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

23 results found

  1. Save Set information for repeated Processes

    Save Set information for repeated Processes

    When setting up a recurring Process that uses a Set with different values each time, Rosetta does not keep a record of the Set values each time it is generated, so that you cannot Rerun the previous Process instances in History. We propose a change to the recording of Set metadata so that each time a Set is used, its values are stored, thus allowing a Historical Process to be rerun at a later date. An example is rolling fixity checks, wherein a different range of SIPs are checked each day using the same…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Management  ·  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. File level access restrictions to be inherited from PM/MM REP to AD REP

    we are using access restriction on file level for some of our items. For PM REP we can assign this automatically via task chain, but this approach does not work for AD REP (tasks cannot be used). Unfortunately when there are files in PM REP with access restriction, this access restriction is not inherited/copied to AD REP during the enrichment process. So we need to go to AD REP and manually add/change the AR for the files which need to have it.
    It would be great if we have either have a task chain which would copy the file restrictions…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Exclude file level dmdSec from publishing

    We use the out of the box Update Metadata Job fairly regularly. The first part of that job is to run a publishing configuration that outputs the XML to the server. We'd like the option to exclude the file level dmdSecs from publishing, as we have some IEs with thousands and it results in a very large XML file that is difficult to work with. We generally only need to edit the IE level dmdSec so the additional XML is unnecessary.

    0 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  ·  Data Management  ·  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 Next →
  • Don't see your idea?

Feedback and Knowledge Base