-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Welcome to the Preassembly Application!
For users of the application, please consult the user documentation listed in the sidebar.
Preassembly refers to the process of submitting content (files) to the Stanford Digital Repository (SDR) so that the files then get shaped into a structured digital object (such as a "book" or "image") via a process known locally as "Assembly" - hence the name, Preassembly.
Preassembly users should be familiar with the process of accessioning files into the SDR. This process requires copying the files to be accessioned to one of a set of specific "staging" locations internal to the library's systems. The Preassembly application does not currently support direct file uploads via the web. Instead, it takes files from the location where they have been staged and copies them into the SDR. This makes it possible for Preassembly to support both smaller accessioning jobs and larger batches of over 1000 objects and/or over 1 TB of data.
The application allows users to enqueue two related but distinct pieces of functionality:
- Discovery Report Job
- Discovery reports analyze the batch to be accessioned and check for possible errors
- Run Preassembly Job
- Preassembly jobs run the actual Preassembly process. Generally, a Preassembly job should only be run following a successful discovery report for that same batch.
Once submitted from the web, both types of job run in the background to allow long-running and parallel jobs. You can submit a job and leave it running and the system will send you an email when the job is complete.
If a Preassembly job partially executes and fails, it can usually be "restarted": the successfully processed objects will not be reprocessed and the job will pick up where it left off.
NOTE: A project's Discovery Report job is affected by the running of Preassembly. If you run a Preassembly job before running a Discovery Report on the same batch, the report will ignore any objects that have already been processed through Preassembly. If you need to re-run Discovery and Preassembly on a previously processed batch of content, please give your batch a new "Project name" so that completely new reports and logs get generated.
- Getting started
- Deposit workflow overview
- Content staging
- Using Globus to stage files
- Filling out the Preassembly web form
- Running the Discovery Report and Preassembly Jobs
- Updating existing items
- Accessioning complex content
- Accessioning images with captions
- Explanation of possible errors found by a discovery report
- What Happens After My Job Completes?
- My Job Seems to Be Taking A Really Long Time (like... days!)
- My files did not show up on the PURL as expected
- Using preassembly for self-deposited content