ADO Types in Archipelago

Archipelago Digital Objects (ADOs) require a type value upon ingest. This tells Archipelago what kind of template to create for that specific object.

Note that this list is subject to change as we work with more collections.

Below is a list of TAMU Archipelago worktypes:

Collection

  • Metadata:
    • Technical/Structural:

      • Has child ADOs

      • May be part of another collection

    • Descriptive

      • No unique fields

  • Structure:

    • Should have its associated files set up for “collections as data”

    • May have a thumbnail

  • Display/viewer

    • None

  • File types: jpg (thumbnail)

  • Example item: Brazos Maps

All child ADOs are displayed at the bottom of the page.

Screenshot of a Digital Object Collection ADO.

CreativeWorkSeries

  • Metadata:
    • Technical/Structural:

      • Has child ADOs in a prescribed order

      • May be part of a collection

    • Descriptive

      • No unique fields

  • Structure:

    • Should have its associated files set up for “collections as data”

  • Display/viewer

    • Mirador - user can scroll through child ADOs

  • File types: None

  • Example collections:

    • Building History Collection

  • Example item: Bachelor Hall and Buggy House

  • Collection vs. CreativeWorkSeries

    • Like a collection, a CreativeWorkSeries displays all ADOs at the bottom of the ADO page.

    • Unlike a Collection, a CreativeWorkSeries includes a Mirador viewer with all ADOs in order. The user can scroll through enlarged ADOs without clicking off the page.

    • Unlike a Collection, a CreativeWorkSeries has no thumbnail.

Screenshot of the Mirador viewer of a CreativeWorkSeries ADO.

Image

  • Metadata:
    • Technical/Structural:

      • Checksums for files

    • Descriptive

      • No unique fields

  • Structure:

    • Multiple High Resolution Images as Canvases

    • 1 to n canvases

    • Individual canvases can be downloaded

    • Not paged

  • Display/viewer

    • Mirador

  • File types: jpg, jp2

  • Example collections:

    • WWI Postcards

    • Wheelan Collection

    • Berger Cloonan

  • Example item: Military Parade 1

Map

  • Metadata:
    • Technical/Structural:

      • Checksums for files

    • Descriptive

      • Projection

      • Edition of the map / state of the map

  • Structure:

    • Multiple High Resolution Images as Canvases

    • 1 to n canvases

    • Not paged

    • May have a watermark

  • Display/viewer

    • Mirador

    • x, y, w, h of the watermark to the original canvas

  • File types: jpg, jp2

  • Example collections:

    • Brazos Maps

    • WWII Service Maps

  • Example item: Bryan-College Station Bicycle Plan

  • Image vs. Map

    • A Map will be annotated with a watermark, but an Image will not

    • A Map contains unique metadata not included in any other worktype

Screenshot of a Map ADO.

Book

  • Metadata:
    • Technical/Structural:

      • Structures and Ranges

      • Checksums for files

    • Descriptive

      • No unique fields

  • Structure:

    • Multiple High Resolution Images as Canvases

    • 1 to n canvases

    • OCR and HOCR or AltoXML for each canvases

    • Entire work can be downloaded as a PDF with OCR embedded

    • Should have its text and associated files set up for “collections as data”

    • Not paged

    • Searchable

  • Display/viewer

    • Mirador

  • File types: pdf, jpg, jp2

  • Image vs. Book

    • A Book has OCR, an Image does not

    • A Book is searchable, an Image is not

    • Users can download an entire Book as a pdf, but Images must be downloaded individually as their original filetype (jpg or jp2).

  • Example collections:

    • Yearbooks

    • Committee on South Asian Women

    • Cherokee Freedmen

  • Example item: The Olio

Screenshot of the search function on a Book ADO.

Here is the extracted text tab on the book:

Screenshot of the extracted text tab of a Book ADO.

Manuscript

  • Metadata:
    • Technical/Structural:

      • Structures and ranges

      • Checksums for files

    • Descriptive

      • HTR

  • Structure:

    • Multiple High Resolution Images as Canvases

    • 1 to n canvases

    • HTR for each canvas

    • Entire work can be downloaded as a PDF with HTR embedded

    • Should have its text and associated files set up for “collections as data”

    • Not paged

    • Searchable

  • Display/viewer

    • Mirador

  • File types: pdf, jpg, jp2

  • Book vs. Manuscript

    • A Manuscript does not have OCR or Extracted Text

    • A Manuscript has HTR instead

  • Example collections

    • AMC Early Presidents

    • Houston Oil Company Minutes

  • Example item: Letter to Louis L. McInnis from H. H. Dinwiddie, August 6, 1887

Screenshot of a Manuscript ADO.

AudioObject

  • Metadata:
    • Technical/Structural:

      • Checksums for files

    • Descriptive

      • Link to Avalon

  • Structure:

    • 1 - n audio files

    • File and transcript can be downloaded

    • Searchable, synced vtt transcript

  • Display/viewer

    • Audio player

  • File types: mp3, vtt

  • Example collections:

    • Science Fiction Radio Show Collection

    • Owens Folk Music

    • Edge Grant Oral Histories

  • Example item: Bill Scott, Forest Ranger: “Forest Aflame”

In the example, the audio and transcript are synced and there is a button where the user can download the vtt.

Screenshot of an AudioObject ADO.

The vtt shows up as extracted text.

Screenshot of the extracted text of an AudioObject ADO.

VideoObject

  • Metadata:
    • Technical/Structural:

      • Checksums for files

    • Descriptive

      • Link to Avalon

  • Structure:

    • 1 - n video files

    • File and transcript can be downloaded

    • Searchable captions

  • Display/viewer

    • Video player

  • Example collection:

    • Veterans of the Valley

    • NASA A/V Recordings

  • Example item: Jeff Bailey - part 1 interview

Screenshot of a VideoObject ADO.

The vtt shows up as extracted text.

Screenshot of the extracted text of a Videobject ADO.

MetadataOnly

  • Metadata:

    • Technical/Structural:

    • Descriptive

      • url to item

  • Structure:

    • Searchable transcript/captions (or nothing)

  • Display/viewer

    • None

  • File types: vtt if this is audio/video hosted on Avalon

  • Example collection:

    • Dallas Women’s Gallery

  • Example item: Interview with Ann Stautberg

The user can download supplemental files but not the file the metadata is about.

Screenshot of a MetadataOnly ADO menu allowing the user to download two vtts.

In this exemplar, the vtts are used to create extracted text, similar to that of a VideoObject or AudioObject.

Screenshot of the extracted text of a MetadataOnly ADO.

WebPage

  • Metadata:

    • Technical/Structural:

    • Descriptive

      • url from orginal site

  • Structure:

    • Searchable

  • Display/viewer

    • WARC Replay.web Widget

  • File types: wacz, warc

  • Example collection:

    • OJS Journals

    • Archived exhibits

  • Example item: AAVPT Biennial Symposia

  • MetadataOnly vs. WebPage

    • While both MetadataOnly and WebPage require a link to another site, WebPage is intended for archived sites and MetadataOnly is more of a tool for discoverability

    • WebPage opens a viewer so the user can navigate the site inside Archipelago

    • WebPage asks the user to upload a warc, not just entering a link.

The user can navigate the site in the viewer as if it were the original website

Screenshot of a WebPage ADO.

In the metadata, the URL of the original site must be included:

Screenshot of the metadata of a WebPage ADO.