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.
-
multi-client capability for external migration in Preservation Plan
In a preservation plan it is possible to migrate objects using external alternatives. To do this, the objects are exported, migrated externally and then re-imported.
Unfortunately it is not possible to configure the export path. Therefore it is also not possible to perform migrations separated by institution. At other places in Rosetta this is already implemented. For example, an export path can be entered when exporting an IE. To enable Rosetta's multi-client capability, it would be necessary to separate by institution when exporting in the Preservation Plan.17 votes -
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.
A first approach could be to introduce a new argument ("institutionCode") similar to producer ID:
<arg2 xmlns=""></arg2> //producerID
as used in e.g. getDepositActivityBySubmitDateRegarding 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 -
Allow export of all instances of an element from Search for Objects
When you use the "Search for Objects" from the Data Management menu you can customize the columns and then export those columns easily to a CSV file. One issue we have is that only the first instance of an element is displayed and exported. For example, if we have multiple occurrences of dc:identifier only the first one will show and be exported. We would like all instances of each element to be included - perhaps with a separator like a semi-colon (or something else).
6 votes -
DCReplacePlugin
Enhance DCReplacePlugin to be able to replace empty/NULL values from the DC field replace value
1 vote -
Web Service for Bagit ingest to automate the whole process
Beginend from Rosetta version 5.2 functionality for Bagit must be improved in further versions. Especially a new web service for Bagit ingest must be developed, because no one want to do manual ingest per GUI interface the whole day if there are a lot of Bagits waiting to be deposited. My option is to improve submitDepositActivity so it can recognise Bagit Structure and so on. Or if it is to complicated to rebuild submitDepositActivity, than to develop a new one. Hope to see this web service in a near future. Sincerely yours, Serhiy
14 votes -
UX: improve list view of IE delivery rules
The IE delivery rule list contains the following fields:
- active
- name
- description
- creation date
- modification date
- commands view, edit and deletethe dates and commands take up half of the screen, not leaving much space for the name and description. Both these fields are rarely descriptive enough to fully understand the implication of the rule and we have had several occasions where an operator added a rule, changed the order or modified a rule without understanding its impact. Resulting in wrong viewers being used or even files not viewable at all.
We think the…
3 votes -
Material flow simplification by making things optional
Currently the material flow combines amongst others, a restrictive list of access rights, retention policies and metadata fields. These operate as restrictions on which access rights, retention policies and metadata fields can be supplied by the submitter. We suggest to make it possible to opt-out on any of these restrictions. That would benefit customers that have automated submission workflows outside of Rosetta where the metadata is already checked for validity and fully under control. It would also help solving human errors when new ARs are created, but forgotten to be added to their respective material flows. If it not possible…
3 votes -
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 -
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 -
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
1 vote -
BagIt-Validation based on 1.0 standart
By manuel ingest, the validation of Bag according to 1.0 standard, is not fully supported. It does not check the tag manifest file checksums for their correctness. Maybe there are some other holes which you can add in a comment.
7 votes -
Preservation Sets - Search levels IE/REP/FILE
as a preservation manager I would appreciate to be able to switch between the search levels IE/REP/FILE when working with Preservation Sets.
I agree, that migrations are on file level, but it would be helpful to know how many IEs/which IEs are involved in a Preservation Set. The test set also shows a list of IEs. Furthermore a lot of information for toubleshouting comes on IE-Level: view problematic IEs, view skipped objects, reports on locked IEs,...1 vote -
Verify numbers of files in CSV and Zip match as part of CSV/Zip deposit method
As part of the CSV/Zip deposit method, Rosetta verifies that all files in the CSV are in the Zip. It does not, however, check if all files in the Zip are listed in the CSV.
We recently discovered that for 5 of our IEs, the CSVs were incomplete and missing a few thousand files. Even though the Zips contained more files, the deposits went through successfully and the files not listed in the CSVs were not preserved.
I propose that as part of the deposit process, Rosetta checks the number of files in both the CSV and Zip and verify…
6 votes -
Option to check fixity on export
Currently, when you export a file, REP or IE from Rosetta you will get an error if there is a problem with exporting the file. However, we have had at least one instance where the file seemed to export without issue but the file couldn't be opened (it was corrupt) and we were able to see that the checksum of the file did not match the checksum stored in Rosetta for that file. This helped us diagnose an issue with the way our storage layer was delivering the file. If Rosetta included an optional checksum calculation on export (the type…
24 votes -
Use .LOCKED file or similar while IE export is still in progress
When exporting large IEs with multiple REPs, it is hard to tell whether the export is finished or not. This becomes especially problematic when running an external automatic job which pulls IEs from the export directory before export has actually been completed.
It would be beneficial to flag a partially exported IE, e.g. via a .LOCKED file which is deleted once the export is complete.9 votes -
Add Error Logs to Preservation Plans and Preservation Executions/ Technical Issues
while working with preservation plans, testing alternatives I would appreciate to have more information about problematic IEs. Error Logs like in Submissions/Technical Issues/ would be helpful. Please add "View Errors".
13 votes -
Closed Caption capabilities
We are creating MP4 deliverables with soft embedded 'Closed captioning'. In addition, we have the WebVTT file used to create the 'closed captioning'.
We would like the OOB Videojs to allow customers to switch on/off closed captioning. At the moment this capability is not present in the OOB viewer. This support is available for VideoJS - https://github.com/videojs/video.js/blob/master/docs/guides/text-tracks.md. This functionality needs to be added as an enhancement to the VideoJS player and any new OOB Video players
This is also accessibility issue that we need to address
1 vote -
Events for DNX Validation
with version 6.0 DNX validation was introduced for METS deposits and any AIP update. Furthermore the .xsd will be versioned. As for now I cannot find any event describing the validation process, the name and version of .xsd used for validation, the agent, the event outcome (success). I would appreciate events documenting this validation. In my opinion this is worth a provenance event, like file format identification event 25.
5 votes -
Add "View Migrated Objects" to Preservation Executions History
as a preservation manager I would appreciate to find the history of the execution of signed-off preservation plans in one place. Therefore it would be helpful to have the list of migrated IEs ( the report of event 355 - Representation was added by preservation plan) in Preservation/Preservation Executions/Signed-off Plans/Executions History/Blocks History, for example as "View Migrated Objects" in addition to "View Skipped Objects".
5 votes -
Size stats about IE/REP in results view
I would like an easier was to see the size of an IE/REP both in number of files and storage size. Right now, the only way I can see to get the size of the IE in terms of storage is to search at the file level for all files in that IE and then export the results to CSV and add up the size column (in bytes). Same goes for number of files except you can also see them when you’re in the Meditor in the metadata for the Rep. It doesn't seem like adding at least the number…
15 votes -
Save Set information for repeated Processes
Save Set information for repeated Processes
When setting up a recurring Process that uses a Set with different values each time, Rosetta does not keep a record of the Set values each time it is generated, so that you cannot Rerun the previous Process instances in History. We propose a change to the recording of Set metadata so that each time a Set is used, its values are stored, thus allowing a Historical Process to be rerun at a later date. An example is rolling fixity checks, wherein a different range of SIPs are checked each day using the same…
1 vote
- Don't see your idea?