Descriptive Metadata Call 2016-01-06
Time: approx. 1:00pm EDT / 10:00am PDT
Call-In Info: Google Hangout: https://plus.google.com/hangouts/_/g2jey2y5cjcnggkmymxziudmw4a
Moderator: carolyn.hansen (U of Cincinnati)
Notetaker: mcmillwh (U of Cincinnati)
Attendees:
- Maggie Dickson (old account) (Duke)
- Corey Harper (NYU)
- Arwen Hutt (UCSD)
- Schneider, Juliane [X] (UCSD)
Agenda:
- Metadata application profile tutorial for Hydra (https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra)
- Discussion of timeline - we'll begin work in mid-February
- Scope
- rather than best practices or guidelines, this will be a "bonus lesson" to be added onto the Dive into Hydra tutorial
- "Lesson - Define metadata complexity levels"
- Focus:
- using properties from multiple vocabularies
- building hierarchical vocabularies
- something about controller
- looking at the book model (https://github.com/projecthydra/hydra/wiki/Lesson---Build-a-book-model-with-RDF), should we demonstrate how additional vocabularies would be layered on top of this?
- we could start with the first layer and add the DPLA layer on top of it
- the DC layer doesn't address the complexity we would want to address in the tutorial
- this is about using other models or namespaces outside of DC
- we'll consider what NYU is working on with Ichabod: drawing on additional RDF vocabularies
- Ruby RDF-vocab gem: https://github.com/ruby-rdf/rdf-vocab/tree/develop/lib/rdf/vocab
- this will allow the use of other vocabularies
- if you have an ontology of your RDF vocabulary, there are generators in RDF-vocab that will output an OWL or RDF vocabulary online and generate the vocabulary
- using properties from multiple vocabularies
- rather than best practices or guidelines, this will be a "bonus lesson" to be added onto the Dive into Hydra tutorial
- Additional items
- previous discussion in November re: Carolyn & Julie on developer call
- no longer a relevant issue, so the meeting was unnecessary
- no need for us to work on blank nodes and (namespaces for?) controlled vocabularies until a use case arises
- Need to run this addition to the tutorial by the rest of the community
- we're developing an elevator speech
- Corey will come back to the group with more details after the NYU hack day and reach out to people in community for feedback
- previous discussion in November re: Carolyn & Julie on developer call
- Action items
- Corey will report to the group about his findings at NYU hack day and community feedback on our ideas for the lesson
- next meeting is February 17th
- we'll plan to be available for questions in the first two weeks of February