Archival collection (hierarchy, paging); fonds-to-IIIF

[tomcrane]

Archival collection (hierarchy, paging); fonds-to-IIIF

(Provide link to index.md of the issue, if available. To be filled in after issue is created - you need the issue number!)

Use case

Patterns and practices for modelling a fonds (Should this be several issues? Needs an overall narrative).

[saracarl]

Discussion at the October 1 Archives CG Call:

Archives of American Art is currently using the Welcome Player (older UV??); assets are broken down into series and folders, with potentially a 1000 or more items. Welcome player is driven off of METS (and EAD).

Nesting? Manifest linking to other manifests, down to each folder.

At UIC, they are creating fields in metadata for box and folder number for everything that goes in. Sometimes a folder is an object, sometimes the item in it is.

In the finding aid, the data is going to have both box and folder. During digitization, that data is put into a number. They will need to convert from that number into a user friendly box/folder to display (and use for navigation/hierarchy).

[saracarl]

Use this for an example of what we want to do: https://preview.iiif.io/cookbook/newspapers/recipe/0068-newspaper/

[saracarl]

1. We can provide an example of a first pass of a structure of collections -- follow intellectual description, rather than physical.
2. Give recommendations of the minimal amount of associated descriptive metadata for a given level in that hierarchy

[tomcrane]

@saracarl This was purely experimental but you might find it useful to play around with:

https://wellcomelibrary.org/service/collections/archives/lightweight

Hierarchy exposed as collections, e.g., going in deeper: https://wellcomelibrary.org/service/collections/archives/PPCRI/H

There's a gist about it here: https://gist.github.com/tomcrane/44c39a3408e43a2185eef0fff552da0c#iiif-collection-route-through-archives

Should not be taken as a recommendation! But something to kick around, at least.

[saracarl]

Discussion Notes:

May need to discuss physical vs intellectual structure.

Box and folder may belong in descriptive metadata, but may not be how we represent things in a IIIF collection/manifest.

Some finding aids do not have box/folder hierarchy. (i.e. microfilm reel/film level)

[saracarl]

TODO:

1. Bring example IIIF v2 manifests to the working group meeting -- Stanford and USHMM.
2. Look for common structures and approaches in those 2 manifests/collections.
3. Outline a barebones archival manifest based on #2
4. Create a v3 manifest based on that outline.

[glenrobson]

This is an example I worked on when I was at National Library of Wales:

http://dams.llgc.org.uk/iiif/archive/3975658/fonds.json

It was mapped from EAD to IIIF Collections and manifests. Source metadata is available at: https://archives.library.wales/index.php/cardiganshire-great-war-tribunal-appeals-records-2

[saracarl]

https://collections.ushmm.org/iiif/manifest/2016.545.1/170700

[tseneca]

Here's an example from University of Illinois at Urbana-Champaign. https://digital.library.illinois.edu/collections/34d204d0-05d1-0130-c5bb-0019b9e633c5-e/tree

To see the manifest, you have to select a folder, then choose the "View" dropdown menu.

[tobiashreiter]

I see the Archives of American Art is already mentioned above. Right now, we're trying to migrate from Wellcome Player to Universal Viewer, but have not migrated our finding aid based image browsing over to an IIIF viewer.

Just to clarify, right now, each Wellcome Player view only highlights one folder at a time, and doesn't allow for browsing the structure of the finding aid. Our desire is to eventually have the whole finding aid browsable from within the viewer.

The trick is to be able to support a broad variety of hierarchies. Even at AAA, we probably have a dozen different hierarchy schemes, if you consider Box/Folder, Box only, Box/Folder/Item, and Reel/Frame folder listings and numerous ways we've handled series, subseries, and folder groupings!

We're excited to see how this develops.

+1