Hyrax Digital Collections application
Bulkrax with AllinsonFlex, configured to import using both CSV and METS XML metadata files
METS XML: one work per row, typically for multipage works
CSV: one work per row, typically single page/image works
Import parsing and options vary between the two types (METS vs. CSV), lightly customized
Create distinct AdminSets per collection or grouping of related collections/materials in order to apply metadata set to that context as a template
M3 Houndstooth (GitHub repo)
Allinson Flex (GitHub repo)
For archival materials that share a same finding aid, METS XML is used to render multiple related/connected objects within the same IIIF viewer
Filename property in the CSV is used to link metadata with the work in Bulkrax
AllinsonFlex metadata profiles for each AdminSet are stored as “context definitions”; “class definitions” refer to the work/object type e.g. Image, ArchivalMaterial, Scientific etc.
Visual interface for configuring aspects of each metadata property, e.g. cardinality, namespace mapping, index behaviors, etc.
Metadata profiles are exportable are massive YAML files, by collection, worktype, or by importer (unfortunately not by AdminSet).
AllinsonFlex is not managing Hyrax “basic metadata fields” the same way as other properties