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.
191 results found
-
Make Standard Upload procedure for 3A configurable (Applet vs. manual upload)
When adding representations via the 3A workbench, the default procedure is the applet upload. Due to security settings, the applet may not be available in some environments. In this case, the user has to click the "Load the files manually" link located on the left to then switch to the manual upload procedure, which works fine.
To avoid these extra steps it would be nice to set the default upload procedure (applet or manual) for 3A workflows via a general parameter.2 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 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.
18 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.…
35 votes -
make
As the set of supported operating systems is known and limited, it would be great to have a Rosetta installation path that uses the distributions' packet manager (e. g. yum) for the initial installation and all upgrade processes. This could facilitate disaster recovery, improve availability and reduce the time needed for upgrades (you could just run "yum upgrade"). DB connectivity etc. could be checked during the package installation.
7 votes -
Support Indexing of Date Range
Enable indexing of a range between start and end values.
4 votesAdi Alter respondedSubmitted by Ex Libris PM on behalf of our customers
-
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.
24 votesAdi Alter respondedSubmitted by Ex Libris PM on behalf of our customers
-
Support Publishing Scheduling on an Institutional Level
Possibility to run publishing jobs on the Insitutional level rather than on the consortia level.
10 votesAdi Alter respondedSubmitted by Ex Libris PM on behalf of our customers
-
Deactivate Institution
Enable deleting an institution that had content already deposited into it. This should be enabled only if all the IEs were already deleted.
3 votesAdi Alter respondedSubmitted by Ex Libris PM on behalf of our customers
- Don't see your idea?