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

26 results found

  1. Enable re-enrichment with CMS records

    Rosetta knows two CMS integration options: unidirectional and bi-directional. The bidirectional integration requires a Rosetta flag to be set in the CMS system. Via the flag, all Rosetta-relevant records from the CMS can be gathered and the metadata pool within Rosetta updated in bulk on a regular basis. However, institutions may be using a CMS for enrichment which belongs to a different / external institution, making the addition of a Rosetta-flag within the CMS system impossible.
    This is where the unidirectional enrichment comes to play. The CMS is queried via SRU integration and records are pulled into Rosetta. The pre-requisite…

    12 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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. "Download all" function with 5.4 should preserve original folder structure

    I tested the new "Download all" function in the General IE Viewer and found that the original folder structure of the files within the representation is not preserved in the IE.zip, even if there is a logical structmap and the folder structure is displayed in the viewer. This is contrary to the IE Export where the original folder structure is kept in the REP.tar. It would be good to have the "download all" functionality modified. When a complex IEs with a hierarchical structure is downloaded through the viewer, the directory structury according to the structmap should be kept.

    13 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)

    Supported as part of 6.1. Download configuration in the representation profile configuration provides 3 options – download all (regardless of original structure – current behaviour), download displayed representation (according to structmap structure) and download (single) file

  3. Make General IE Viewer more configurable

    We at the BSB have different types of material to be displayed with the General IE Viewer (Version 5.4). We suggest to make the configuration of the General IE Viewer more flexible.

    1. Configurable display of panes In general it would be very useful to be able to configure the standard display of panes. For each the content structure pane and the descriptive metadata pane there should be three different modes of display: Display as standard (the panes are displayed when the viewer is opened and can be closed if the viewer clicks on the grey area of the frame on…
    1 vote
    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)

    v6.1 provides configuration options for:
    1. MD pane (md_pane = show/hide/none)
    2. TOC pane (toc_pane = show/hide/none)
    3. search box (search = show/hide/none)
    and other configurations regarding download and share button.
    Thanks,
    Daniel

  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

    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)

    A major aspect of this request has been delivered as part of v6.2 – support for control over version increments through APIs – and as agreed, the area of AIP updates will continue being discussed through the working groups. Due to this, I will close the issue as completed.
    Thank you,
    Daniel

  5. 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.

    40 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)
  6. Flagging SIPs as Deleted when all IEs are deleted/purged

    One of our institutions keeps track of the ingested SIPs in an external application. Here, it is currently not easily possible to trace SIPs for which all IEs have been deleted.

    When deleting all IEs of a SIP in Permanent, the SIP itself cannot be found in a search in Permanent - however, the SIP itself is not flagged as deleted in the SIP Report and its status remains as "Permanent/Finsished" when querying for SIP Status via the API. External applications therefore can't easily see that the SIP actually doesn't exist anymore.

    For external integrations it would be helpful to…

    18 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)
  7. BagIt-Support

    The BagIt format (https://en.wikipedia.org/wiki/BagIt) is “designed to support disk-based storage and network transfer of arbitrary digital content”. Rosetta should support ingests via BagIt to standardize various ingest workflows and make use of the existing BagIt software ecosystem.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deposit  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Completed  ·  Adi Alter responded

    Deposit of BagIt content was implemented as part of Rosetta version 5.2.

  8. Rosetta UX

    This is another Rosetta UX issue

    When you are viewing the DC Descriptive information it would be great to copy information from the 'Data' field

    Currently when you do a 'left' click to start highligthing the field the whole row moves.

    To do a copy from the field you have to edit the record.

    It oul dbe better if you can highlight and copy data without editing the records.

    To move / reorder d=fields it woul dbe better to grab a 'anchor' on the row instead

    13 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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. SAML Authenication mapping with unique indentifier (ID) instead user name

    Currently SAML authentication in Rosetta uses the user name for mapping to the IdP.

    There is no guarantee that the user name is unique within one instituiton or does not get reused after a user has left the instition. This makes the field user name ambiguous.

    It gets more problematic if users from more than one IdP want to authenticate for Rosetta. This happens in a consortia setup or when guest users are stored in a separate IdP. If authentication has to be set up with more than one IdP the user name will no longer be unique and it…

    14 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)
  10. "Unassign" functionality in Permanent TA

    In SIP TA (Submissions – Technical Issues) it is possible to unassign a SIP that is assigned to somebody else by clicking on “Unassign”.
    However, this is not possible in Permanent TA (Data Management – Technical Issues) – there is no way to unassign an IE that is assigned to another person. This can be an issue if that person is absent for a longer period and the IE remains blocked. The only possible workaround I can think of is to change the other person’s password and use his/her user account to unassign the IE – but that’s certainly not…

    15 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)
  11. SRU request to get the file PID

    For a specific use case, we need to get the deep link of a file in Rosetta. Our idea is to use the SRU request for this purpose. But currently SRU requests only return IE-level responses, and not file-level information. We would like to see this changed and are asking for the option of a SRU response at file level to be added.

    20 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)
  12. Additional rule input parameter: Preservation Type

    We have a few workflows where we are adding derivative copies either manually or automatically.
    We hold our derivative / access copies to a different standard than the preservation master files - as such, we are willing to ignore most techMD extraction errors, etc. at this stage.

    However, looking at the MD extraction error handling rules, ignore reasons can only be filtered on the producer / format / extension / mime type etc. level.

    We therefore propose to add Preservation Type as an input criterion for submission rules such as metadata extraction error.

    4 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  ·  Deposit  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Search for "unknown" extensions

    It is currently not possible to search for files with extensions that are not recorded in the Format Library, such as .md or .cxml, because they are not included in the autocomplete list. So there is no way to build sets of files with such “unknown” extensions. According to Ex Libris, there is an open issue on this subject: DPS-16975. I would like to suggest that increased attention be given to this issue and that a solution be planned for one of the upcoming releases.

    20 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)
  14. IE Viewer enhancements

    Fist of all I like the looks of the new repository viewer and looking forward to the new IE viewer that Adi showed in the Rosetta 5.3 highlights webinar. There are a couple of things I would like to see in the new IE viewer, though:

    The new metadata panel looks great, but should be collapsible to make more room for the viewer panel. The same is true for the content panel.

    For some collections in Rosetta, no or hardly any descriptive metadata was available during ingest. The DC record for those IEs is typically empty except for a dc:title…

    1 vote
    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)
  15. Report or other method to show locked IEs

    IEs can be locked due to different reasons. A user may have manually locked an object in Permanent and forgotten to unlock it, or there may be an issue with a hanging or incorrectly aborted processes, causing an IE to be locked by a system process.
    Locked objects cause problems in the system, especially when trying to run another process over a locked IE. Currently, there is no available method through which the user can check which IEs are locked. We currently have to open a ticket with support who identifies locked IEs for us.
    It would be helpful to…

    11 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)
    Completed  ·  Adi Alter responded

    I’m happy to let you know that this report was implemented and will be available as part of Rosetta version 5.3.

  16. customizable staff_work_area per institution

    As people who ingest data into and export data from Rosetta we would like to export IEs per institution.

    Currently the export directory for the whole consortium is (in our installation) /exlibris1/operationalshared/staffwork_area/

    Subdirectories are created when a user exports something for the first time. The subdirectories are named after the user, e.g. for user admin1 /exlibris1/operationalshared/staffwork_area/admin1/.

    We would like to have the export directory per institution, e.g. /exlibris1/operationalshared/staffworkarea/institution1/ or /exlibris1/operationalshared/staffworkarea/institution2/. The creation of subdirectories for users is fine as it is and we would like to keep that…

    33 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)
  17. Create Itemized Sets for Representations (REPs) and Files

    We're trying to create an itemized set of File PIDs in Rosetta to run a fixity check, but we're receiving an error message that Rosetta can't find the PIDs. It looks like Rosetta is expecting a list of IEs in order to create an itemized set. Is there another way to create an itemized set of File PIDs?

    Ultimately, we’d want to be able to make itemized sets with IEs, REPs, and Files.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Administration  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Enhance UpdateMD web service to support DNX update

    Currently, the updateMD web service is designed only for updating DC metadata. Updating DNX metadata is not supported. But tests have shown that DNX metadata can perfectly be updated using the updateMD web service – with the drawback, however, of losing some other DNX metadata such as Producer, Producer Agent, and Access Rights Policy. See attached file with a comparison of the IE METS before and after the updateMD process.

    The getIE web service works fine in this regard, allowing you to choose between DC, DNX and source MD and giving you the complete metadata output.

    We strongly argue that…

    28 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)
    Completed  ·  Adi Alter responded

    I’m happy to let you know updateMD was enhanced to support editing of any MD that can be edited via the UI. This will be available in the upcoming version of Rosetta (version 5.3).

  19. Full index support for metadata validation error

    Currently, metadata validation error messages are only indexed if the field does not exceed a certain max length. If the file contains a longer error message, the IE fails indexing and lands in the exception queue, leading to no meaningful way to find them other than by their SIP / IE ID.

    This becomes problematic, when validation error messages are exceptionally long - either per design or per error in embedded third party tools. A current example for this exists through a jhove misbehavior, which is documented as an issue here: https://github.com/openpreserve/jhove/issues/165

    Removing the validation error message from the Index…

    10 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)
    Completed  ·  Adi Alter responded

    The indexing limitation was removed and will be available as part of Rosetta’s next version (5.2).

  20. Enforce file download in Rosetta Delivery

    As a researcher, I want to be able to always download a data file delivered to me in the web browser, regardless of its format. But to date, there is no such option in Rosetta.

    The choice of specialized viewers is limited. A vast majority of formats will be handled by the “File Viewer” that leaves it up to the browser how to deal with a file – open it directly in the browser window or offer it for download. For some formats, it is possible to define a download or “save file” option in the browser settings. For the…

    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)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base