Metadata Call 2016-04-20
Call-In Info: +1 (641) 715 3660, access code 651025
Moderator:
Juliet Hardesty (Indiana University)
Notetaker:
mcmillwh (Univ. of Cincinnati)
Attendees:
- James Griffin (Lafayette College Libraries)
- sanderson (BPL)
- Christine Mayo (Boston College)
- matienzo (DPLA)
- Arwen Hutt (UCSD)
- Ryan Wick (OSU)
- Subgroup reports
- Descriptive Working Group
- Descriptive Metadata Call 2016-04-13
- The group discussed the spreadsheet for metadata pain points
- All institutions are encouraged to add to the spreadsheet with their own experiences with these elements or add additional elements that are challenging
- The next meeting will focus on the widening gap between BIBFRAME and Hydra, particularly their handling of descriptive metadata
- MODS and RDF Descriptive Metadata Subgroup
- MODS and RDF Call 2016-04-18
- last 2 meetings talking about complex subjects and how to model them
- how to handle multiple subjects - topical, temporal, geographic
- if a subject has multiple pre-coordinated elements, how can it be represented in the subject field?
- interaction with Descriptive Metadata WG
- keeping an eye on opportunities for overlap/collaboration
- Applied Linked Data Working Group
- Last meeting had limited attendance due to DPLA Fest
- Working on making a gem that could be mounted on any rails app
- could talk to different backends like blaze graph
- just a few remaining issues to wrap up and metadata enrichment will follow
- Is the gem one of the group's deliverables?
- It was part of WG aims - a way to share code that deals with linked data
- Like an intermediate layer that allows Blazegraph to act as a caching layer
- We need a standardized interface to make calls against so we can share linked data
- Descriptive Working Group
- Issues/Questions
- None
- Review Metadata IG Requests and Priorities
- During the URI Management WG Charter Development, multiple issues on this page were brought up
- Julie contacted WGBH to determine where issues with FITS and ExifPro stand
- code in Hydraworks takes care of FITS info they want to express in RDF
- PBCore XML might have some rdf properties that will need to be expressed that can't be expressed in EBUCore
- pointing to code in hydra works that covers technical metadata properties
- PBCore might require new URIs
- Additional Items
-
URI Management Working Group
- The charter is a work in progress and feedback is welcome
- Julie, James, Ryan discussed scope and objective of group, deliverables & timeframe
- Karen Estlund provided feedback
- see notes on Karen's LCDX session, Management for Community URIs
- Julie will send this out to the list Thursday 4/21 around 4-5 EST
- please provide any feedback before this time
- the group will need a facilitator
-
URI Management Working Group
- Action Items
- Provide any feedback on charter by Thurs, 4/21 at 4:00
- Next meeting: Wed, May 4, 1pm EST