Skip to content
Benjamin Albritton edited this page Jun 3, 2019 · 13 revisions

Preamble

  • In order to have access to the Preassembly Application, you'll need to be a member of the appropriate Stanford workgroup.

    • Note: you will need to be on the Stanford Network (or VPN) to work with the application.
  • To become a member of the accessioning workgroup, please email dlss-accessioning-team@lists.stanford.edu with your name and SUNet ID, department within the library, and reason for needing access to the application.

  • You will also need workgroup access to Argo, so if you do not already have that please specify when you request membership in the accessioning workgroup.

  • Communications are managed through the sdr-accessioneers mailing list. If you are going to be adding materials to the Stanford Digital Repository through this application, please subscribe to the list here

Overview of Basic Workflow

  • Contact the accessioning manager to make sure that you have the appropriate permissions to use this application and have received training
  • Register your content in Argo before beginning work in this application [see Argo registration instructions]
  • Prep the content on one of the storage servers available for accessioning work [see section on Content Staging]
  • Create a manifest for your content [see more]
  • Make sure that the content you want to accession has a LEGACY ticket in JIRA specifying, at a minimum, number of files and preservation size of the content (these are necessary for monthly infrastructure planning), and that the ticket has been proposed in the monthly accessioning call
    • Please note: This is very important so that we don't accidentally fill up a preservation disk. If that happens, all accessioning across the library will come to a screeching halt for a week or more.
  • Go to https://sul-preassembly-prod.stanford.edu
  • Run the Discovery Report
  • If errors are uncovered in the report, correct those and run the Discovery Report again (repeat until there are no errors being reported)
  • Run the preassembly job
  • Monitor to completion in Argo and complete post-accessioning tasks