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.
454 results found
-
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 -
Configure the delivery rules to display only logical structure maps, and not physical ones
We would like the ability to configure the delivery rules to display only logical structure maps, and not physical ones as for one of our institutions, we’d like NOT to deliver the physical structMap, and only the logical one.
Thanks,
Ryan
Ryan Edwards
Digital Access and Systems Librarian
Information Systems
Getty Research Institute
1200 Getty Center Drive, Suite 1100
Los Angeles, CA 90049-1688
reedwards@getty.edu
310.440.73981 vote -
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.…24 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.…
12 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…
11 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.…
34 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.
17 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.
23 votes
Adi Alter
responded
Submitted by Ex Libris PM on behalf of our customers
-
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 Publishing Scheduling on an Institutional Level
Possibility to run publishing jobs on the Insitutional level rather than on the consortia level.
9 votesAdi Alter
responded
Submitted by Ex Libris PM on behalf of our customers
-
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 -
Small change to Create Derivative Copy task
Right now when you use the Create Derivative Copy task you have to select a plug-in type (either Transformation Profile or Stream Handler) even in cases where you are not transforming anything - we create derivative copy representations that are exact copies of the preservation master representation with no transformations. I would like to have a 3rd radio button - something like "None" - added. Since we're not selecting any file formats and we are choosing "Copy other extensions" the system is doing what we need it to do and we think it's odd to have to choose a plugin…
1 vote -
Counter / SUSHI support in Rosetta
Increasingly libraries and consortia are using counter / sushi to measure usage of digital and electronic resources across disparate parts of their holdings.
If holdings being held in Rosetta are to be valued by the broader institutions funding and maintaining those resources, we need to be able to report usage using the counter and sushi protocols (which ExLibris has already demonstrated knowledge of in their support in ALMA and 265 services).
Key features would be basic counter and sushi reporting; use of IP ranges and user groups already defined in Rosetta for reporting; and grouping or content by already defined…
1 vote -
View preservation history of IE
posted on behalf of Amy Joseph, NLNZ
As a researcher, I want to be able to understand the history of an IE including preservation actions.
As an admin, I want to be able to configure the system to display versions of a representation by EventType, so that a user can navigate between different versions of a preservation master or other rep
5 votes -
Update Logical and Physical Structure Maps via Rosetta Back Office
Hello,
For IEs that have both a physical and a logical structure map, we would like to be able to globally change the default logical and physical structure map labels for Preservation Master in the Rosetta Back Office.
Thanks,
Ryan
Ryan Edwards
Digital Access and Systems Librarian
Information Systems
Getty Research Institute
1200 Getty Center Drive, Suite 1100
Los Angeles, CA 90049-1688
reedwards@getty.edu
310.440.73982 votes -
UI interface - Deposits: Delivery XSL Files | Details xsl viewer
i have been working in the XSL viewer / editor -- to make it readable i have to copy and paste the information out of the XSL window -- reformat the information to make it readable -- however when I paste the reformatted XSL file into the Rosetta XSL editor the formatting gets lost -- for example <xsl:for-each> all of the information is wrapped back to a single line -- it would be great if the formatting is maintained in the Rosetta XSL editor
1 vote -
I want to have the collection reversely sorted in Rosetta back office in the collection management. (Z to A)
I want to have the collection reversely sorted in Rosetta back office in the collection management. (Z to A)
1 vote
- Don't see your idea?