Content Comparison

...

1. Requests received and routed to appropriate digitization team

   • RLAS Receives requests and determines whether items should be scanned in the DPC or RL, and routes items to conservation as need be.

   • RLAS creates digitization starter guides for the materials and routes items to DPC

   • RLAS determines whether patron request items can be made publicly accessible, require restrictions or if more investigation is needed (status unclear).

   • Who creates entries in the google tracking sheet???

2. Digitization

   • DPC performs intake

   • DPC evaluates the condition of material and confers with Conservation as needed.

   • Conservation evaluates and repairs items when needed.

   • DPC digitizes collections and performs quality control.

     • See DPC document in L:\Share\DPC-Public\DPC Manual\Workflows or contact Giao Luong Baker

   • RLAS scans items and performs quality control.

3. Digital Materials Sent to Patrons

   • DPC returns quality controlled scans to RLAS via Box.

   • RLAS returns scans to patrons via Box.

   • DPC returns physical items to RLRS.

4. Finalization and Ingest

   • DPC finalizes items they have scanned, and creates ingest tickets for Repository Services Analysts.

   • RLAS does something to prepare items they have scanned for ingest (???)

   • Head, DCCS creates ingest tickets for items scanned by RL.

   • Repository Services Analysts create new collections in DDR as needed, ingest content to DDR, and route tickets to RLTS or Metadata Architect depending on the collection/item in question.

     • /wiki/spaces/DDRKB/pages/2086600705

5. Description and Metadata

   • RLTS will review and, when necessary remediate existing description for items that were digitized either by DPC or RL.

   • Metadata Architect crosswalks and applies metadata - Patron Digitization Requests - Metadata

   • Metadata Architect determines the appropriate rights statement for the item(s)/collection and applies it. - Rights Management Metadata

6. Launch

   • Head, DCCS applies access roles accordingly (public access, metadata access only or a mix of levels in a collection).

   • Archivist for Metadata in RLTS adds persistent DDR links to catalog records (if necessary) and finding aids for enhanced patron access. For most published items (books, serials, etc.), links are only added to local Aleph records (not OCLC records).

7. Delete data from DPC servers

   • Repository Services Analyst deletes files from DPC Work following collection launch.

...