See Anatomy of DAMS digital assets#Pagedcontent/complexassets for an introduction to paged content in the DAMS.

GUI Ingest Options:

• Books/Issues - 
  1. Create by uploading a PDF, system generates page images (TIF files) from PDF. 
  2. Create empty book/collection, add pages (in TIF or JPEG2000 format) afterwards. 
• Publications can be thought of as a specialized collection for organizing issues. Like collections, when created via the GUI they are empty, and issues may be added to them afterwards. Publications provide two features that may be advantageous:
  1. Publication-level descriptive metadata that can provide valuable context for issues organized within it.
  2. A unique viewer that makes it easy to browse issues in chronological order (e.g., newspaper or magazine issues). 

• Note: Page-level description is not the default, so unless provided by users, individual page objects do NOT contain a MODS datastream.
• Note: As mentioned by help text on the form, there is a 2GB limit when ingesting zipped pages (around 70 .tiffs, depending on size). Anything over that limit should be ingested via the batch ingest tool. 
  
  
• Additional GUI configurations to help manage assets include:
  • At publication level:
    • Add issue dates to issues if the original issue date is not in a format recognized by the system.
  • At issue/book level:
    1. Regenerate PDF (based on all pages)
    2. Regenerate TN (thumbnail image)
    3. Regenerate OCR (searchable full-text datastreams for all pages)
    4. Reorder pages
    5. Delete pages (same as purge utility but with convenience of checkboxes)
  • At page level:
    1. Regenerate PDF (for that page)
    2. Regenerate OCR (for that page)

Note: Because of additional derivative generation, updating/replacing/reverting the OBJ at the page level will result in longer processing time than other content models. Otherwise, updating/replacing/reverting datastreams associated with Paged Content works the same as with other Content Models.

Note: If a PDF is added as an additional datastream after a book/issue has been created, then no pages will be created from it.

PDF derivatives

At the book/issue level, there is an option to create a PDF under Manage > Book > Create PDF. To avoid over-writing a user-provided PDF, the PDF created from this feature will have the DSID (datastream ID) as "UTLDAMS-PDF" and the filename will be "UTLDAMS-PDF__timestamp" (example: UTLDAMS-PDF__1541687815, see below). Users can use https://www.epochconverter.com/ to find a human readable version of the timestamp. If a user provides a PDF, then the PDF filename will get written to MODS. However, if there is no user-provided PDF and only a system generated PDF, then the system generated PDF filename will get written to MODS. If there is neither a PDF nor a UTLDAMS-PDF, then there will be no identifier with type filename written to MODS.

At the page level for either a book or issue, the same option is present. However, since PDF is a derivative and pages have OBJ datastreams, there is no indication of whether the page PDF derivative is system generated if the "Create PDF" feature is used.

Thumbnail Creation for GUI Ingested Paged Content