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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. issues with indexing in Rosetta

    Here at SLUB, we're seeing a few issues with the way indexing is implemented in Rosetta.
    Currently, all Rosetta servers that are in the "Indexer" role hold a single part of the whole index with no redundancy between the indexing nodes. If there's an outage in one of the servers, there are two effects.
    N°1: One third of the index entries will not be available and the missing server will not take part in indexing any new IEs, obviously. The IE that was just being processed by this server will not be in the index and information about it will…

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ingest  ·  Admin →
  2. Export of full-lifecycle IE including all versions

    Something Rosetta is currently lacking is the possibility to export full IEs including all versions. Current export functionality only exports the latest version of an IE.

    Two use cases for this functionality of full lifecycle IE export: exit scenario;
    batch export of IEs post migration action to perform external analysis / comparison of different versions of the same digital object across different versions.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Data Management  ·  Admin →
  3. Bulk delete of Processes

    We can have 100s of processes located under the Data Management tab and we would like the ability to mark some or all of the processes and then delete them in bulk

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base