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. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ingest  ·  Admin →
  2. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  3. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Ingest  ·  Admin →
  4. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ingest  ·  Admin →
  5. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  6. Support Indexing of Date Range

    Enable indexing of a range between start and end values.

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

Feedback and Knowledge Base