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.
105 results found
-
Add report in migration plugin
The migration plugin is part of preservation and is the way in Rosetta to migrate bitstreams from an obsolete format to an uptodate format. It is a script plugin receiving a file and delivering the newly migrated file.
For purpose of transparency it would be necessary to add a report about what has changed. For example when migrating pdf to pdf/a it might happen, that a font was included or even replaced. Having a report would implement a well documented preservation workflow. Depending on the migration tool the report might be quite complex.So it would be nice to add…
43 votes -
Assigning a valid SSO user to a default account if one does not exist
We do not wish to have all of our institutional users in Rosetta, leaving that for administrators and publishers.
When a user has signed in successfully through SSO (in our case ADFS) we know that they are from our institution, so we should be able to do access rights rules based on this.
We are also able to pass through extra parameters through SAML to identify the type of user, and where they have come from, it would be great to be able to assign such users to basic user accounts so we can have granular access rights to IE's…
4 votes -
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 -
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 -
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- & 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.
- could be tested…
5 votes -
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…5 votes -
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 -
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.
11 votes -
Scheduled Reports with Institution in Email-Header
When Scheduling Reports for different Institutions, the Email received does not contain any information about where the Data comes from. If you want to know IEs in permanent, you would not know wheter it is about Institution A or B. It would be great if the Institution or a custom information-text-content would be sent either with the email or be included in the report itself. The Report in my special case is "Repository Stats" in "Data Management".
2 votes -
untangle format identification/validation/MDextraction
In the course of the discussion on the "File Extension Mismatch - Change Notice" posted on BaseCamp by Opher Kutner (ExL), I noticed that some aspects of file identification/validation/MDextraction in Rosetta need improvement. What got me thinking was the statement that format identification was done by the extractor, which isn't the case. Instead, the actual behaviour is that the MdExtractionPlugin also does the format validation, while the format identification is run separately in DROID. However, the job of extractors is neither format identification nor format validation. Instead, it's metadata extraction only. Usually, a preservation repository can't even know which extractor…
7 votes -
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.
4 votes -
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 -
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.…22 votes -
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.…
13 votes -
In Material Flows: remove option to "automatically extract compressed files" when the Content Structure is changed to METS
The material flow configuration includes the default option to "automatically extract compressed files". This option works in all workflows except METS content structure work flows, as extracting compressed files leads to mismatches in the METS struct map.
Material flow configuration screens should blend out the extraction option for METS content structure or make the user aware of a faulty configuration upon saving such a combination.2 votes -
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…
12 votes -
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 treeBut should not be able to:
*see/modify processes.
*delete IEs or purge the recycle binWe 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.
10 votes -
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.…
33 votes -
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.
15 votes -
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 votesAdi Alter respondedSubmitted by Ex Libris PM on behalf of our customers
- Don't see your idea?