Descriptive Metadata Call 2015-11-18


Time: approx. 1:30pm EDT / 10:30am PDT (after Hydra Metadata IG Call)

Call-In Info: +1 (641) 715 3660, access code 651025 

Moderator: carolyn.hansen (U of Cincinnati)

Notetaker: mcmillwh (U of Cincinnati)



  1. Priorities and timelines
    1. metadata application profile
      1. Julie and Carolyn will look into getting this added as an agenda item on the Hydra Tech call
  2. Base metadata application profile (see:
    1. discussion about the purpose, need to define it more clearly
    2. right now it's basically Dublin Core - what are we adding?
    3. Hydra in a Box ships with the DPLA map as the default schema. This is basically title, rights statement, URL, and holding institution.
    4. What we're developing isn't really an application profile
    5. The DPLA map has a class for place names, collections, agents, etc. 
      1. we could start with the 3 core classes of the DPLA map:
        1. source resource
        2. web resource
        3. aggregation object
      2. because the 3 classes are meant to be expressed as RDF and linked data, we could specify application profiles for extracting that in a flatter record
    6. UCSD developed their profile in layers
      1. Dublin Core 
      2. DPLA - a more specific rendering of layer 1 
      3. looking at putting their own layer on top of layer 2
    7. This is more of a best practice for building your own application profile in Hydra
    8. It will be difficult to get everyone to agree on what a core application profile will look like, but if we can explain to build one, this will help many members of the community
  3. Best practices on handling controlled vocabularies (skipped)
  4. Best practices on handling blank nodes and nested attributes (skipped)
    (see: 2015-05-07 - Fedora Tech Meeting2015-04-23 - Fedora Tech Meeting
  5. Next steps
    1. Discuss ways to explain building an application profile in the Dive into Hydra Works tutorial