Skip to content

Rosetta

Your feedback matters to us. Help us improve Rosetta by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

6 results found

  1. Allow institutional parameters for (custom) plugins

    In a consortial landscape a plugin may be used by several institutions. However, each institution may need to use different parameters for a shared plugin.

    To give examples, consider these two business cases:
    (1) A plugin utililzes proprietary 3rd party software that is licenced per institution. In such case we must ensure that only the institutions that actually pay the licence fee have access to the functionality. The license key would have to be configured per institution.
    (2) A PDF migration plugin can take different input parameters which determine the output format to be created (e.g. to PDF/A-1b vs. PDF/A-2b).…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Solr Startup Checker Plugin

    After having had some issues with the new default Solr port in Rosetta 5.4.0.0, I suggest creating a startup checker plugin for Rosetta to test for Solr availability. Possible error scenarios involve:
    1.) network down
    2.) Name resolution down/misconfigured
    3.) Solr default port closed in the local firewall / Solr not listening

    1. & 2. could be checked by pinging the other servers' DNS names (NOT the IPs), which would test network availability and DNS resolution in one step. As Rosetta servers usually are located in the same subnet, we don't have to worry about ICMP firewall restrictions.
    2. could be tested…
    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Additional Rosetta Collections REST API

    The current Rosetta REST APIs return infromation about a collection structure.

    We would like a REST API which will return all of the IEs attached to a Rosetta Collection

    The information is currently stored in the Oracle VIEW COLLECTIONMEMBERSVIEW

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Web Services: 1. new argument for SOAP/REST: institution code / 2. general limitation of answers to content of a certain institution

    Hello,

    we would like to limit the content delivered by a SOAP/REST request to data belonging to a certain institution.

    We assume there are several ways to reach this goal.

    1. A first approach could be to introduce a new argument ("institutionCode") similar to producer ID:
      <arg2 xmlns=""></arg2> //producerID
      as used in e.g. getDepositActivityBySubmitDate

    2. Regarding a more fundamental solution:
      As a constortial leader we are especially interested in functionalities that support Rosetta's multi-tenancy approach.
      Therefore we would welcome a general limitation of web service request answers to content of the institution of the requesting user.

    Thanks for your considerations

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  APIs & Plug-ins  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Rosetta REST API to Retreive IE

    Would like a REST API which will retrieve a Rosetta IE METS record

    You can retrieve the METS by adding 'dps_func=mets' to the delivery URL -

    https://digital.slq.qld.gov.au/delivery/DeliveryManagerServlet?change_lng=en&dps_pid=IE305955&dps_func=mets

    however, the delivery manager will not deliver the METS information if there is are access rights preventing the delivery of the digital asset

    so would like a way to retrieve the METS data regardless of the access rights on the asset

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  APIs & Plug-ins  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. DCReplacePlugin

    Enhance DCReplacePlugin to be able to replace empty/NULL values from the DC field replace value

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  APIs & Plug-ins  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base