28 July 2015 GIS WG

Time:  1pm Eastern / 10am Pacific. 

Call-In Info: Dial 1-609-258-0122, no access code needed

Moderator:  Darren Hardy

Notetaker: John Huck

Attendees: 

• Eliot Jordan (Princeton University)
• James Griffin (Lafayette College Libraries)
• Darren Hardy (Stanford University)
• John Huck (University of Alberta)
  
  

Agenda:

1. Roll Call

2. Call for Agenda Items

3. Next Call

   1. Date: Tue 18 August 2015
   2. Moderator: 
   3. Notetaker: 
4. Schedule time for Google Hangout
   1. Make these more regular as we approach Hydra Connect?
5. Initial draft for geospatial metadata use cases and functional requirements
   1. Please see the W3C Spatial Data on the Web Working Group
      1. ...as well as domain-specific use cases
6. Geo/PCDM Initial Vocab and Model Structure (Thanks Eric James!)
   1. What's next and how do we build on top of this work? Discuss.
7. Questions for the PCDM community
   1. How to store ISO/FGDC metadata
      1. As a blob within the work object's descriptive metadata?
      2. As a separate related file
   2. Are datastreams versioned?
   3. What else?

Minutes

1. Roll Call

   1. Darren Hardy

   2. Eliot Jordan

   3. James Griffin III

   4. John Huck

2. Call for Agenda Items

3. Next Call

   1. Date: Tue 18 August 2015
   2. Moderator: John Huck
   3. Notetaker: James Griffin III
4. Hydra Connect
   1. Looking for an unconference, WG or a poster opportunity at the conference.
5. Schedule time for Google Hangout
   1. August 11, 1 PM EST, 10 AM PST
6. Initial draft for geospatial metadata use cases and functional requirements
   1. Discussion of level of granularity.
   2. The group looked briefly at W3C use cases for comparison.
   3. James will revise his document based on feedback from the group.
7. Geo/PCDM Initial Vocab and Model Structure (Thanks Eric James!)
   1. What's next and how do we build on top of this work? Discuss.
   2. Discussion of the class hierarchy, and a need for a concise model.
   3. Darren will sketch some ideas for implementing more developed class hierarchy, integrating curation concerns, with basic dublin core added, supplementing it with a specific geospatial component.
   4. Questions to keep in mind:
      1. Can we reuse parts of models developed for scanned images?
      2. What about inline documentation?
      3. What can we do to implement the hierarchy with the full HydraWorks data model (i.e., collections, etc.)?
      4. ACTION ITEM: Eliot will find out more about the HydraWorks stack and report back to Darren.
8. Questions for the PCDM community
   1. The group (or Eliot?) will formulate specific questions around the following topics and pose them to the Hydra tech list.
      1. How to store ISO/FGDC metadata
         1. As a blob within the work object's descriptive metadata?
         2. As a separate related file
      2. Are datastreams versioned?
         1. Can metadata properties be versioned?
      3. What's the volatility of the HydraWorks API (? not sure if I heard this correctly – jh)