Getting Started

Accessing Preassembly

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

  • If you are not sure if you have access, please make sure you are on the Stanford VPN and then click this link to go to the application home page.
  • If your browser loads the Preassembly application, then you have already been authorized and are ready to use Preassembly
  • If the page does not load, please contact the Repository Manager, to request access.
  • Note: you will need to be on the Stanford Network (or VPN) to use Preassembly.

• In order to stage files, you will need to have permission to copy files to a staging location.

  • Which staging server to use depends in part on whether you are a member of a department with its own staging space.
  • For example, Special Collections, Music, and members of the digitization labs have departmental shared storage that has been configured to work with Preassembly
  • There is also a "general use" staging location available on the Preassembly server itself.
  • If you need access to a staging location or are unsure of which location to use, please contact the Repository Manager.
  • Detailed instructions on how to access the Preassembly server in order to upload files with SFTP or through the command-line are available on Consul

• 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

• A Slack channel is also available at #dlss-aaas for more synchronous communications

Overview of Basic Workflow

• Contact the repository 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 [instructions]
• 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
• Use Argo to check that accessioning has been completed
• Complete post-accessioning tasks such as cleaning up the content staging location