How to Check SIP Status

Overview

Version 2.0 of the Rosetta Deposit Processor will not include the SIP Status module. The main use of the SIP Status module -- as a way to generate links for EADs -- is no longer relevant with ArchivesSpace implementation. Furthermore, searching within the Rosetta software has shown itself to be the most efficient way to check on SIP statuses.

Searching the Operational Repository

• To start, click "Go" on the Operational Repository search bar.

• Rosetta gives a few different ways to find SIPs. You can search by date submitted

• By "Before DATE" and/or "After DATE"

• And combine those search fields with Partner

• Results can be exported as a CSV by clicking the export icon below the search button

• Once the CSV has been generated, you can download it by clicking Download

• The Location column shows where the deposit currently is. If the Location is "Permanent," that means the deposit has successfully been ingested into Rosetta. Clicking "Search Permanent" will take you to the Permanent Repository, where you can view the ingested IEs and/or export IE information as a CSV

• If the Location is "TA Workbench," the deposit is in the TA workbench and requires further attention.

Working in the Technical Analyst Workbench

• You can get to the "Technical Analyst" Workbench by going to Data Management --> Technical Issues

There are four areas of TA Workbench that are most likely to have errant deposits

Deposit

Submissions end up in the Deposit tab if there is something wrong with the SIP package. This is likely an error in the CSV/METS/DC file.

• In the case of CSV deposits, make sure

1. The correct deposit folder is listed in the "File Original Path" column

2. Every IE level row as exactly 1 PRESERVATION_MASTER REP row below it

3. Every FILE listed in the CSV is present in the deposit's "streams" folder

- You can test this easily by searching the Object Type column (Column A) for every instance of "FILE" and comparing that number to the amount of files in "streams"

Loading

Submissions end up in the Loading tab if there was an issue loading the files from the deposit into Rosetta. Try selecting the deposit and choosing "Rerun" from More Actions in the bottom-left. If this does not work, contact the Rosetta System Administrator.

Validation

Submissions end up in the Validation tab if one or more of the deposit's files fail Rosetta's Validation Stack. This could mean a file needs replaced or the deposit needs to be re-run. Click the "Results" dropdown for each row to see how many files have failed which part of the Validation Stack.

System Error

Submissions end up in System Error for various reasons. If working on a CSV deposit, run through the troubleshoot list from the Deposit tab above and re-ingest the deposit. If the second attempt also ends up in the System Error tab, contact the Rosetta System Administrator.