-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Preassembly requires familiarity with SUL-DLSS accessioning practices, including preparation of content on one of the mounted drives available the system. The app allows users to enqueue two related but distinct pieces of functionality:
- Discovery Report Job
- Run Preassembly Job
Both types of job are run asynchronously to allow long-running and parallel jobs. The user is emailed upon completion with a link to the results.
If a Preassembly job partially executes and fails, it can be "restarted" (e.g. after correcting the data to be processed): the successfully processed objects will not be reprocessed.
NOTE: A project's Discovery Report job is affected by the running of Preassembly. I.E. the same objects that would be skipped to avoid reprocessing are also not "discovered". This side-effect is intentional.
- 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