Skip to content

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

4 results found

  1. Additional rule input parameter: Preservation Type

    We have a few workflows where we are adding derivative copies either manually or automatically.
    We hold our derivative / access copies to a different standard than the preservation master files - as such, we are willing to ignore most techMD extraction errors, etc. at this stage.

    However, looking at the MD extraction error handling rules, ignore reasons can only be filtered on the producer / format / extension / mime type etc. level.

    We therefore propose to add Preservation Type as an input criterion for submission rules such as metadata extraction error.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deposit  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Retaining datetime stamps for digital content uploaded to Rosetta

    This includes two strands:

    1) Retaining original datetime stamps on files stored/transferred to Rosetta (e.g. using commands like "rsync")

    2) Extracting datetime stamps from files to store with the digital object in its technical metadata.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deposit  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Completed  ·  Adi Alter responded

    There are actually 2 ideas here. We’re happy to let you know that we’ve implemented the first idea as part of Rosetta version 5.2. Please open another idea for the second one and we’ll evaluate it separately.

  3. BagIt-Support

    The BagIt format (https://en.wikipedia.org/wiki/BagIt) is “designed to support disk-based storage and network transfer of arbitrary digital content”. Rosetta should support ingests via BagIt to standardize various ingest workflows and make use of the existing BagIt software ecosystem.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deposit  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Completed  ·  Adi Alter responded

    Deposit of BagIt content was implemented as part of Rosetta version 5.2.

  4. Provide XSDs for Email Notifications

    Provide XSD and/or examples of the raw XML for places in which Rosetta provides the option of editing the XSLT.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  2 comments  ·  Deposit  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base