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.
134 results found
-
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 -
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 -
IIIF Universal Viewer - Print
Require the option to allow ‘Print’ from the viewer.
Would like to configure the at least the following information as part of the ‘Print’ option
- Descriptive metadata
- Handle / PI identifier
For images would like to print the single image to fit across the page – this is relevant if printing in portrait or landscape mode
Allow image to scale according to paper size selected4 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…
4 votes -
IIIF Universal Viewer - Share Options
Would like to configure the ‘Share’ option.
At this stage the only share options are
1. Embed
2. URL link
Would like to configure the ‘Share’ option to allow adding the following additional social media options
1. Facebook
2. Twitter
3. LinkedIn
4. Various citation options such as RefWorksAs part of the share option we would like to configure what information is passed across. For example, for Twitter, SLQ would like to pass
1. Handle/PI information
2. Title
3. Image
4. Any appropriate hashtags4 votes -
Expand the search scope of the search box on web collection page
Is it possible to expand the search scope of the search box on web collection page from the current collection to all its sub-collections and itself?
For example, I tried to search IE2119194 by its partial title "South Korea's economic puzzle" on the following page;
but no matching IEs were found, because the IE belongs to the collection(id=109127824)'s sub-sub-sub collection(138846884).
- 109127824 > 138830885 > 138834664 > 138846884
4 votes -
IIIF Universal Viewer - Download Options - filename
When selecting the download option would like to be able to configure the download file name.
Currently the file name is ‘default.jpg’
Would like to configure the download so that the download file name can use one of the following options
1. <dc:title> (maybe the first 30 characters); or
2. <internalIdentifierValue>
SLQ would prefer the <dc:title> option4 votes -
IIIF Universal Viewer - Download Options
Would like the ability to configure the download options to allow the download the Master Preservation Master
4 votes -
Upgrade internal XSLT processor
Currently Rosetta seems to accept only XSLT 1.0 syntax for XSLT configuration files. This means we are deprived of the many goodies of XSLT 2.0 and 3.0:
- strong typing and XSD types
- XPATH 2.0 sequences
- XSL functions
- range variables
- regular expression matching and grouping
- URL encoding and decoding
- better value comparison
EXSLT 1.0 is not supported either, so whenever I try to do something more intelligent that some simple markup and string replacing, I hit the limits of XSLT 1.0. Trying to make decisions in your XSLT based on element values without regular expressions is a big PITA - if…
4 votes5.5 already includes XSLT 2.0 support in the XSLs files used for delivery – IE and file metadata, XSLT viewer and customized SRU response. 6.1 will include XSLT 2.0 in OAI transformation xsl
-
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 votes
Adi Alter
responded
Submitted by Ex Libris PM on behalf of our customers
-
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 -
Publishing Sync Job - View Log
hen running a Publishing Sync Job and looking at the assciated 'View' we get the following information
Mon Jan 07 09:06:40 AEST 2019 INFO sync all configurations for IE publishing
Mon Jan 07 09:06:40 AEST 2019 INFO sync the configurationId: 18981614
Mon Jan 07 09:06:41 AEST 2019 INFO sync the profileId: 18981613
Mon Jan 07 09:06:41 AEST 2019 INFO Handling new IEs
Mon Jan 07 09:06:41 AEST 2019 INFO Handling Removed IEs
Mon Jan 07 09:06:41 AEST 2019 INFO Handling updated IEs
Mon Jan 07 09:06:41 AEST 2019 INFO Finished sync for the profileId: 18981613
Mon Jan 07 09:06:41 AEST…4 votes -
IIIF Universal Viewer - Searchable PDF
For searchable PDFs would like the viewer to have similar features as the viewer deployed by the British Library- http://access.bl.uk/item/viewer/ark:/81055/vdc_00000004216E#?c=0&m=0&s=0&cv=0&xywh=-2194%2C-163%2C6568%2C3244
Would like the search bar for be available and indication where the search word if located in the PDF
Download options would be driven by Entity Type
4 votes -
change to Rosetta METS XSD re: duplicate file IDs
During a recent batch of deposits (see case 00477041 from the Getty for more info) we figured out that, due to an error in our one of our input files that creates the METS, our original METS file did not have unique file IDs in the structMaps for the preservation master and modified master representations. It was simply repeating the same file ID from the access file representation.
For some reason, this did not cause a METS validation error when we validated against the Rosetta XSD before deposit, nor when it was deposited. However, it resulted in the METS in…
3 votes -
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…
3 votes -
Take account of the METS mimetype attribute during file ingest
The METS standard has a mimetype attribute on files "<file MIMETYPE="application/pdf" ... /> but this information is currently ignored by Rosetta during the file-type identification process on ingest.
Mimetye should be at least as reliable as file extensions (because mimetype is a standard, is actively maintained and widely use by a good portion of software for identifying file types).
In particular, recognising mimetypes is likely to greatly increase the ease of ingest of content from internet-facing content management systems where it is very widely used
See also https://tools.ietf.org/html/rfc6838
3 votes -
encrypt all update channels
After experiencing some problems with Rosetta's Format Library update mechanism (see SC 00423700 "error while updating Format Library [Rosetta 5.1.0.2]", handled by Paul), we got thinking about Rosetta updates in general. Currently, all updates are downloaded through an unencrypted connection. This includes:
- Rosetta updates (major, minor, service packs, hotfixes) and their checksum files (!)
- Oracle updates and their checksum files
- PDS updates (presumably)
- Format Library updates
Due to this, there's no way to verify authenticity of ExLibris' servers and the integrity of the update packages/the checksums. All information that are downloaded from ExLibris' servers must be…3 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 -
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 -
IIIF Universal Viewer
SLQ would like the ability to configure the following in the ExL supplied IIIF Universal Viewer
Print option – currently hidden in the default view - currebtly would like to configur how th pint out appears
Bookmark - currently hidden in the default view
Feedback - currently hidden in the default view – we see this as an option to allow ustomers to provide feedback on teh displayed image such as correctins and.or additional information
Share Option – we would like the ability to configure additinal 'share' features such as FaceBook, Twitter, HistoryPin, etc3 votes
- Don't see your idea?