Digital Object Structures

Depositing images to Digital Repository Service (DRS)

For tiled images, both the component-images and a resulting tiled image of a subject will be deposited in the DRS.

For stitched images, typically, component images will not be deposited.

In some cases, both the component-images and the stitched will be deposited. One reason for keeping the component images of stitched image: The stitched image is so large that it’s resolution needs to be reduced to accommodate the limitations of Harvard’s image delivery systems, and keeping the components at their original resolution provides users with additional image information.

For the STILL IMAGE objects (as defined by DRS), each deposited image will be its own object, each with its own deliverable URN, and the relationships between components and tiled images will be coded with the file-to-file relationship, HAS_SUBSET.

For page-turned (aka, PDS) objects, typically, only the stitched image will appear in the page-sequence presented to users. In cases where a tiled image is included in the page-sequence, both the tiled and component images will appear in the page-sequence (tiled images will be tagged, “composite” in the structural metadata; component images, “component image”), The component-images will be coded with the same level of access as the PDS object, and will be assigned URNs that can be provided to users by library staff upon request.

Filenaming

FOR STILL IMAGE OBJECT IMAGE:

If the tiled original is named: LA-GD-UA-2-02, the four component image files would be named:

• LA-GD-UA-2-02_comp_01
• LA-GD-UA-2-02_comp_02
• LA-GD-UA-2-02_comp_03
• LA-GD-UA-2-02_comp_04

FOR PDS OBJECT IMAGE:

The component images will be named using standard sequential naming.

CODING FILE/OBJECT RELATIONSHIPS IN DRS

• Still Image object: file-to-file, HAS_SUBSET.

• PDS object: No relationship coding available as of Fall 2021.