Metadata Call 2023-06-27

Time: 2:00pm-3:00pm Eastern

Call-In Info:

Community Notes:


Moderator(s): Annamarie K.

Notetaker: Nora Z.



  •  @Juliet Hardesty (Indiana University)

  • @Annamarie Klose (Ohio State)

  • @Anna Goslen (UNC Chapel Hill)

  • @Rebekah Kati (UNC Chapel Hill)

  • Emma Beck (University of Louisville)

  • @Rachel Howard (University of Louisville)

  • @Nora Zimmerman (Lafayette College)

  • @Christine Peterson (Amigos)

  • @Heather Greer Klein (Samvera)



  • Still looking for a SMIG co-facilitator

  • Roadmaps Alignment Group Update - Julie

    • Haven’t met recently, but there has been some discussion on Slack

    • Hyrax had 4.0 release and is currently working on Google Analytics support

  • OAI Documentation Working Group Update - Annamarie

    • The June meeting was canceled since it overlapped with the Juneteenth holiday.

    • Group submitted a lightning talk proposal for SVC 2023 in Philly to report on the outcome of the group’s work.

    • Next meeting is July 17. Participants will bring feedback from developers on customizing OAI with Blacklight in Samvera.

  • Presentation on Indiana University’s use of Bulkrax with AllinsonFlex - @Juliet Hardesty

    • Presentation Recording

    • 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

  • Presentation on University of North Carolina’s use of Bulkrax - @Rebekah Kati

    • Carolina Digital Repository (CDR) GitHub repo  

    • Carolina Digital Repository is an institutional repository, so their use case is focused on ingesting scholarly articles 

    • Using Bulkrax 3, with some customization due to their local use of people objects (post MODS migration), which tie faculty, departmental affiliations, and ORCiDs, and also impose author order (important for Google Scholar indexing)

    • Creator field + affiliation field that map to local controlled vocabulary; a creator_other” field, and creators_index 

    • Bulk ingests are often the result of CV review projects for individual faculty (use normalized data from Scopus); also work with subject liaison librarians for social sciences to gather citations (manual data creation)

    • Standard Bulkrax installation

      • Visibility: have to manually update records that require embargoes after importing as Public. Would appreciate an enhancement to import with embargo option.

  • Open Discussion

  • Future meeting

    • Katharine Van Arsdale can demo how Adventist Digital Library uses Bulkrax with Hyku.


Next meeting: July 25, 2023, 2-3 pm Eastern