/
DRS Deposit Service for Content not Produced by Imaging Services

DRS Deposit Service for Content not Produced by Imaging Services

Jan 23, 2025

What We Do with the Data

Note: we don't accept data directly from patrons.

Workflows We Offer

The Procedure to Use this Service

  1. Submit an Imaging Services project proposal by following the link in this page.

  2. Determine the workflow with Imaging Services (see the "Workflows We Offer" section above and their detailed descriptions)

  3. Copyright clearance

  4. Set up the file delivery method/procedure with Imaging Services (see "File Delivery Method" section below)

  5. Provide DRS related information to Imaging Services (see the "DRS information" block in the "Check List ..." section below)

  6. Arrange to ran a pilot batch with Imaging Services if necessary

  7. Confirm a fee if applied

  8. Schedule file deliveries (one time or regular)

Check List before File Delivery to Imaging Services

  • Any copyright or license document to be associated with the digital content?

  • DRS object type (see the section below)

  • Delivery, and Discovery systems to be used, and who will insert or update the links after depositing

  • Any cataloging work needed before depositing?

  • Any metadata files needed to go with file deliveries?

  • File type/format to be delivered

  • File type/format to be deposited

  • File and Object name

  • DRS information:

    • DRS OwnerCode (for example, GSE.GUTMN)

    • DRSBillingCode (for example, RAD.SCHL.SKC_0001)

    • NRS authorization path and mask (for example, FHCL and {n}, HBS.Baker.GEN and {n}-{yyyy})

    • DRS access code (P, R, or N)

  • Any other information the repository would like to be associated with deposited objects.  For example,

    • Initial project note

    • Producer of the files

    • Future processing note

DRS Object Type We Support

Currently, Imaging Services assembles these types of object for the DRS.

  1. Still Image Object

  2. Page Turned Object (List Object if needed)

  3. Document Object (PDF, Doc, Docx)

  4. Opaque Object

  5. Text Object

File Delivery Method and Communication

Delivery methods

Delivery communication

  • It is recommended that the repository sends an email to inform Imaging Services that a batch is ready to be processed.

  • Repository should always keep a copy of data.

Batching

We expect files are delivered in batches.  We refer a batch as a deposit unit in a reasonable "size".   The "size" could be considered from the combination of several factors:

  • Data size: generally speaking, we don't want a batch is too big (i.e. over 50GB)

  • Average file size: the larger the file size, the less number of files in a batch.

  • Total file count: we don't want a batch contains too many files (let's see, over 5,000)

  • Object type: an object type may require all the files for an object are in the same batch (for example, a PDS object)

  • Object size:  an object may include several types of files, which increases the size of the object.

  • DRS guidelines, policies, software practical limits: LTS has a general guideline about how many GB data a depositing unit can deposit each day.

  • The convenience for repositories and Imaging Services to prepare and track the "unit":


Usually, we deposit the batch as delivered by its repository.  Here are some examples:

  • Still image batches with average 1000 color TIFF images.

  • Still image batches with average 500 color TIFF images.

  • Still image batches with average 20 color TIFF images which matches to a building design.

  • Still image batches with average 200 color JPEG2000 images which were produced from a box of slides.

  • A PDS batch which contains 1000 color images of a 1000-page book.

  • A PDS batch which contains 500 color images of 50 small pamphlet.

  • A PDF document batch which contains about 10 GB of PDF files.

  • A PDF document batch which contains about 12 PDF files.