/
Hydra Tech Call 2015-10-28

Hydra Tech Call 2015-10-28

Owned by Bill Branan
Jun 16, 2017

Time: 9:00am PDT / Noon EDT

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

Moderator: Justin Coyne (DCE)

Notetaker: Nabeela Jaffer (Michigan)

Attendees:

  • Carolyn Cole (Penn State)
  • Lakisha Robinson (Yale)
  • Adam Wead (PSU)
  • Aaron Coburn (Amherst)
  • Steven Ng (Temple)
  • Esme Cowles (Princeton)
  • Collin Brittle (Virginia Tech)
  • Julie Hardesty (Indiana University)
  • Trey Pendragon (Princeton)
  • Ryan Wick (Oregon State)
  • Anna Headley (Chemical Heritage Foundation)
  • Nabeela Jaffer (Michigan)
  • Justin Coyne (DCE)

Agenda:

  1. Call for agenda items: No additional items

  2. Next call
    1. Date: November 4, 2015
    2. Moderator: Steven Ng 
    3. Notetaker: Esme Cowles
  3. Check in on process for community registration Hydra RDF predicates (using opaquenamespace.org)
    1. Carried over from last week, relating to the following predicates: https://github.com/projecthydra/sufia/issues/1327
      1. Talked about the five terms listed in the github issue. General consensus is that it is better to use existing RDF vocabularies which helps with linked data. The arkivoChecksum is produced via connection of Arkivo. RelativePath is not really used by ScholarSphere, but is used in ArchiveSphere for viewing files in a tree structure. It is mainly used for storing the original path of the file in the uploaded directory tree. The last two terms, proxyDepositor and  onBehalfOf can be used with Marc relator terms. In ScholarSphere they are used as the proxyDepositor is the person who is depositing the file while the onBehalfOf is the person who owns it.
      2. opaquenamespace.org was created at Oregon to manage their RDF predicate. Question is are there other people using it? Should the future work be under this name space? 
      3. Should PCDM namespace be used? Most of the attendees were not in the favor of using PCDM namespace for creating additional RDF terms
      4. There should be a way to connect Metadata Interest group to Github group, so that when issues related to metadata are listed on Github, the metadata Interest group can participate and get involved in the development. Julie Hardesty volunteered to  talk to Metadata Interest Group. Should we have a team on projecthydra or projecthydra-labs or a cross-project team can work with metadata group. Esme and Justin volunteered to look into this.
    2. Referred to the Hydra Metadata Interest Group by Esme – how did this go? 
      1. Metadata Interest Group is interested in helping develop vocabularies.