After Accessioning

What Happens After My Job Completes?

• Once the Preassembly job and accessioning completes you see "Job completed".

• If there are errors either during the initial preassembly job or the accessioning process (or both), this will be indicated in the status reported in Preassembly when the job is complete:

• Job complete (with Preassembly errors)
• Job complete (with accessioning errors)
• Job complete (with Preassembly and accessioning errors)
• Discovery report complete (with errors)

• After the accessioning process finishes, you have a few final responsibilities: to report to the content owners or stakeholders, to close the accessioning ticket, and to remove your accessioned content from the storage server.

• Reporting to content owners and stakeholders can be formal (an email copying relevant project and departmental lists) or informal, depending on the context of the job.

• Closing the accessioning ticket is an important step - don't forget!

• In order to do remove your content from the storage server, it is recommended that you verify the files that have been accessioned before you remove the content from the server. While an object might look "done" we prefer to compare the checksums of the files to make sure that what was preserved matches what you meant to accession.

  • For a few objects, you can get the checksums from the individual objects in Argo (from the contentMetadata datastream)
  • For a large number of objects, please file a ticket in the Accessioning JIRA project requesting an md5 checksum report for your content
    • Make sure to include the list of druids that you need information about (in a single csv file, one druid per line)