MODS and RDF Call 2016-11-28

Owned by Bill Branan
Jun 16, 2017

Time: 9am PDT / Noon EDT

Call-In Info: 712-775-7035 (Access Code: 960009)


Homework Reminder: 

  • TBA

Moderator: Steven Anderson (Boston Public Library)

Primary Notetaker: saverkamp (NYPL) (etherpad link: https://etherpad.wikimedia.org/p/RDF-MODS-20161128)

Attendees:

Agenda:

 

   

 

  1. Conversion Code Update

    1. No updates for this week, but BPL will likely have updates to the code by next meeting.

  2. Series, subseries, collection, institution Individual Institution Usage And RDF Voting Document review (https://docs.google.com/spreadsheets/d/19sjUN5oMsGHAVsBaZ-gncePuWPNPi7t5eOtxM5Sqml0/edit?usp=sharing)

    1. 3 options to put forth for voting

    2. Option 1:

      1. Where does bibframelite:Series come from? Not in bibframe 1.0 or 2.0. Seems to be only in bibframelite? Maybe a concern if we want to assert that as a type. Interesting that bibframelite has two different Series classes with two different URIs.

      2. Using pcdm:memberOf may not work for institutions who cannot mint URIs or create objects for parent series/collections. It would have to be part of the migration to create objects for these host objects, which could be cumbersome for some.

      3. Institution was not included in this mapping document because it seemed that maybe this was a use case specific to BPL. What is the consensus? What to do about external owing institutions? Wouldn't physical location work for this? Stephen will add institution as pcdm:Collection to the document, so people can vote on it.

    3. Option 2:

      1. Advantage is that you can get to collection or series more easily, but it seems that you would still need to resolve multiple levels of series to get to other subseries within the hierarchy.

    4. Option 3:

      1. Same as option 2, but uses bibframe:hasSeries instead of a custom predicate, but it is used incorrectly. The advantage is using a familiar predicate.

      2. Option to represent collections/series as strings rather than objects is not present.

      3. dcterms:isPartOf would require a non-literal value, would have to use dc:relation with literal.

      4. Some institutions may not want to create new objects, so this would be an option. dc:relation, however, may not be the best  mapping for this.

    5. What to do about mapping items in a collection that do not include this information in relatedItem? This info should be in the rels-ext and you could use that to generate Collection objects.

      1. Can IU post some of their examples where the 3 options posted wouldn't work? Julie will look into it.

    6. Questions about bibframe series predicates. Why are we not comfortable using bibframe:hasSeries? Guidance isn't clear about semantics and use. Seems to be intended more for published series or serials, rather than archival series, so we really aren't using all of the series-related predicates correctly.

    7. Stephen will put together a voting document once IU decides whether or not they can map their items to collection objects.

  3. Other Collaboration Document discussion

    1. No additional discussion items.

  4. Next meeting: Monday December 12th at 9:00 AM PST / Noon EST