How can we improve Rosetta?

Recalculate fixity SHA2 and insert into Rosetta

We have around 22,000,000 files that we would like to recalculate a new fixity hash, but this time it would be SHA256. We need a good way of getting this fixity back into Rosetta. We would like to store it along with the SHA1 value we previously generated. We are aware that the SHA1 fixity is located in xml clob data in the hdemetadata table. We are wondering if there is another location for this SHA1 value in another table.

2 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Aly ContehAly Conteh shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Aly ContehAly Conteh commented  · 

        We are aware that there is a task chain that can be run from within Rosetta to recalculate the fixity but we are running a process outside of Rosetta that will necessitate us touching all 22 million files and therefore it makes sense to do the recalculation at that point and use an API call to update the metadata in Rosetta.

      Feedback and Knowledge Base