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
  1. UI interface - Repository | General Settings | Events Configuration

    It wouls be greate if we could sort the display by 'Event Type' as this will allow easier matching to the Rosetta Configuration manul Appendix C whch lists events by ID number

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  2. Best fit mode for the JWPlayer in IE viewer

    With the new IE viewer in version 5.4 the JWPlayer (for video and audio) does not have a best fit parameter meaning that the right-hand side of the player is hidden under the metadata pane. The only way to see the whole player is to close the metadata pane manually or zoom out in your browser. We would like to see a “best fit” parameter added to the JWPlayer in Rosetta so that the behavior would match the jpeg viewer (which fits itself to the frame by default).

    Thanks,

    Ryan Edwards
    Digital Access and Systems Librarian
    Information Systems
    Getty Research…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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.
    3. could…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Rework/rewrite AIP update functionality

    Since version 4, Rosetta includes a feature called AIP update. This feature is used mainly by libraries to alter data in the permanent repository, which might be necessary for a number of reasons. Metadata might need updating due to a typo or due to new research results, new files that weren't included in the original ingest might be added, or existing files might be altered with higher resolution versions or to repair defective files. Libraries tend to use this feature, because they regularly ingest SIPs that include a minimal set of metadata. Later, when full metadata have been allotted or…

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Bitstream information in Bitstreams Tab

    Researchers often use zip or tar files in order to upload large amounts of research data in various formats. Bytestream extraction is a useful tool for analyzing the content of these container files. The resulting bitstream information is written in the METS and displayed in the BitStreams Tab in the Web Editor. The information includes BS ID, file name, file original path, extension, mime type and format ID (if successfully identified).

    We would like to suggest the following improvements for the BitStreams Tab and the bitstream information in general:

    1) Include Bitstream size. The relevant values can be found in…

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Producer Mandatory Fields shall be controlled by a code table

    As of now (version 5.3) there is no code table to control which fields are optional or mandatory when adding a producer.

    We provide Rosetta as a service and the details (name, email, telephone etc.) of producers can be seen across the installation. This means that staff user 1 from institution A can see the details of the producers of all the other institutions. The workaround is to enter 123 as telephone.

    Basically we would like Rosetta to be fully compliant with the concept of multi-tenancy.
    Until this can be reached we would like to see code tables in use…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Support the ability for Rosetta to request IEs in batches

    We would like Rosetta to work more efficiently when the storage layer is tape based, particularly for exports. Could Rosetta request IEs in batches from the storage layer. when exporting large collections from tape a file is retrieved from tape one at a time.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Recalculate fixity SHA2 and insert into Rosetta

    We have around 22,000,000 files that we would like to recalculate a new fixity hash, but this time it would be SHA256. We need a good way of getting this fixity back into Rosetta. We would like to store it along with the SHA1 value we previously generated. We are aware that the SHA1 fixity is located in xml clob data in the hdemetadata table. We are wondering if there is another location for this SHA1 value in another table.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Make IE Viewer share button configurable

    The share button in the IE Viewer currently always shows the browser URL. Often the IE has an OID or some persistent URL that is preferred over the transient viewer URL. Rosetta should allow the URL that is displayed to be configurable. Preferably with an XSLT per institution similar to the IE metadata XSLT.

    It is also desirable to allow for more than 1 URL in the share window. That would allow to add URLs for standalone vs embedded viewers, thumbnail view, CMS metadata view, etc.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. view only- user who cannot break anything

    For error-detection and workflow documentation it is sometimes necessary to be able to view all configurations in Rosetta - even all in the Administration area.
    But not all users should be able to edit configuration elements in Rosetta, especially not in the Administration Area.
    In our (ZBW/Germany) opinion, a view-only-user would be very handy. This person would be able to see all the configuration details and the view-option would be available to her/him, but not the edit-button.
    She/he would not be able to break anything, but would be able to see all the details needed for documentation or other purposes. …

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. provide Rosetta developer previews

    ExLibris' current mode of releasing new Rosetta versions is to announce a rough time slot ("April this year") for that new version/minor-release/servicepack/hotfix, release it and deliver a list of changes along with the new release. Up until the actual release, ExLibris will only give a very general roadmap of the planned changes. While this is an easy approach for ExLibris, it's hard for the customers to prepare for the release. Therefore, I propose for ExLibris to provide pre-release versions of Rosetta in order to enable developers to adapt their software (i.e. Submission Applications) to new features, changed API behaviour etc.…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  12. relative paths in IE XML / Storage Migration

    Rosetta 5.2 has brought a new Storage Migration feature that enables institutions to restructure their permanent storage to fit changing requirements. However, the documentation currently warns that "Disconnecting legacy storage is not recommended as it may prevent the possibility of reverting to a previous IE version." (https://knowledge.exlibrisgroup.com/Rosetta/Product_Documentation/Version_5.2, Preservation Guide, page 185). As far as I can see, this limitation is due to the use of absolute paths in the IE XML files. The paths in older versions of these files cannot be updated without forging provenance information, which, of course, isn't an alternative. However, updating these paths would…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. OCR plugin that makes full text available to search

    To create a full text searching capability, we are proposing a plugin that performs OCR on the files in Rosetta, and then makes that text output available via an API or other publishing mechanism, that can be read and indexed by an external CMS.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Read-only user

    As we've begun bringing more users into Rosetta we've seen the need for a different type of user, who could basically do these things:
    *view/download IEs/files
    *view the collection tree

    But should not be able to:
    *see/modify processes.
    *delete IEs or purge the recycle bin

    We checked using dummy accounts with 'Viewer/Editor - View' and 'Approver/Assessor/Arranger - View' but neither of these can see the collection tree, either from the data management menu or from the search screen. So, we'd like something similar Viewer-Editor-View but with access to the collection tree.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Allow full-text searching of all objects in an IE, not just one at a time.

    There is a way to have Primo index the full text of PDFs that are in Rosetta which can help a user find which Rosetta IE has a document containing their term/phrase but then once the user clicks through to the Rosetta viewer there is no way for the user to know where their search term appears. Having the search term come through to the viewer would be great, but that would only work when there are a few PDFs. For IEs that contain dozens of PDFs the user would have to open each one and search for their term.…

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Allow Retention Policy to not delete automatically

    Besides of having the option to delete or delete permanently, a retention policy should also allow not to delete at all. Many institutions want to assign a retention period to their objects, but do not want to delete the IEs when the retention period is over. Instead they expect to receive a report where they can decide themselves which objects should be deleted.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Validation Stack to Flag Problems as Warnings, not Errors, and Move them to Permanent

    Ability to run the validation stack during ingest, but only flagging warnings, not errors. All IEs will be moved to the permanent repositories and if needed, the problems will be dealt with in a future stage.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ingest  ·  Admin →
  18. Support Publishing Scheduling on an Institutional Level

    Possibility to run publishing jobs on the Insitutional level rather than on the consortia level.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Rosetta UX

    when creating a set using the 'IE Entity Type' would like the 'match' to be sorted alphabetically -- appears to be sorted randomly

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Profiles for Rosetta-Aleph-Integration

    we are using the Rosetta-Aleph-Integration in both directions:
    1. creating the CMS-record in Rosetta and
    2. setting the Rosetta-flag in Aleph as well as updating the Aleph record with the URN created in Rosetta.
    In the past there was only one target field for the URN and the assignCMS task with updateURNTask worked without problems.

    Due to changes in the cataloging rules - we are using now the international RDA-rules - we have to deal now with different target fields in Aleph for the URN depending on the type of material: e-only e-books, digital reproductions of printed books, online versions…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base