Metadata Call 2016-02-10
Call-In Info: +1 (641) 715 3660, access code 651025
Moderator:
Juliet Hardesty (Indiana University)
Notetaker:
mcmillwh (Univ. of Cincinnati)
Attendees:
- Esmé Cowles (Princeton)
- carolyn.hansen (Univ. of Cincinnati)
- James Griffin (Lafayette College)
- villereal (Univ. of Virginia)
- Arwen Hutt (UCSD)
- Ryan Wick (Oregon State)
- Chrissy Rissmeyer (she/her) (UC Santa Barbara)
- sanderson (Boston Public)
- Subgroup reports
- Descriptive Working Group
- on hiatus until next meeting on 2/17
- next meeting will include updates on recent work at NYU that may impact tutorial lesson contents
- MODS and RDF Descriptive Metadata Subgroup
-
MODS and RDF Call 2016-02-08 - notes from last meeting
- discussed MODS:abstract element
- dcterms:extent vs. bibframe:extent
-
MODS and RDF Call 2016-02-08 - notes from last meeting
- Applied Linked Data Working Group
- Segment of a File Working Group
- no feedback on draft received from outside of the group
- Julie will check with group members to determine if recommendations are final
- Descriptive Working Group
- Issues/Questions
- none
- Review Metadata IG Requests and Priorities
- New item for ontology question from
Samvera GIS Data Modeling Working Group
- James: While modeling geospatial assets, began to model ActiveFedora objects and their respective attributes
- began to integrate GeoRSS, but found that extensions for RDF were abandoned, so solution was not feasible
- discussed possibility of structuring an extension of GeoRSS in RDF
- could this be published on opaquenamespace.org?
- GeoRSS is something that could be used if it had an RDF expression, but it currently doesn't.
- was it discussed at GeoBlacklight Summit?
- briefly. For the purposes of expediting a prototype, they're using a placeholder URI in the Data Modeling Group
- The Data Modeling Working Group is part of the Geospatial Interest Group that may get together to create an ontology based on GeoRSS. This will need a namespace.
- was it discussed at GeoBlacklight Summit?
- Opaquenamespace.org seems reasonable to start with, but it will be necessary to continue with data modeling and vocabulary
- It would be ideal if projecthydra.org could have rdf vocabularies there and this would emphasize the community aspect
- the DPLA profile makes use of W3C's Basic Geo for altitude, latitude, longitude
- for things that DPLA maps to, does it make sense to consider using alt, lat, long and then using GeoRSS for things W3C isn't covering?
- if the purpose is to share it outside GeoBlacklight
- for things that DPLA maps to, does it make sense to consider using alt, lat, long and then using GeoRSS for things W3C isn't covering?
- James has enough info to move forward and can discuss with the Data Modeling Group
- if an ontology is likely to be developed, opaquenamespace is likely to be used
- New item for ontology question from
Samvera GIS Data Modeling Working Group
- Additional Items
- at Hydra Developer Congress in SD, there was lots of talk about how PCDM maps to IIIF
- recognition that there are flaw in implementation
- there will be a development effort to have PCDM objects that generate IIIF manifests automatically
- work to pull the notion of a book out of plum and move it into curation concerns or a separate gem
- Further discussion re: dcterms:extent vs. bib frame:extent
- is it better to use dc:extent with text strings like everyone else or is it better to use it as specified?
- Esmé and Julie suggest following community practice and not going with dcterms:extent as defined
- any examples of someone using it as defined?
- none suggested
- none suggested
- is it better to use dc:extent with text strings like everyone else or is it better to use it as specified?
- at Hydra Developer Congress in SD, there was lots of talk about how PCDM maps to IIIF
- Action Items
- next meeting will be in 2 weeks on 2/24