/
MODS and RDF Call 2016-11-14

Samvera Community Wiki

MODS and RDF Call 2016-11-14

Jun 16, 2017

Time: 9am PDT / Noon EDT

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


Homework Reminder: 

Moderator:  @sanderson (Boston Public Library)

Primary Notetaker: @Eben English (etherpad link: https://etherpad.wikimedia.org/p/RDF-MODS-20161114)

Attendees:

  • @sanderson (BPL)

  • @Eben English (BPL)

  • Jennifer Liss (Indiana) 

  • @soriordan (Emory)  

  • @Melanie Wacker (Columbia)  

  • @Eric O'Hanlon (Columbia)   

  • @ksgerrity (Amherst College) 

  • @saverkamp (NYPL)   

  • @Sara Rubinow (NYPL) 

  • @Johanna Radding (Amherst College) 

Agenda:

  1. Conversion Code Update

    1.  No updates yet; waiting on final mappings of several elements

  2. series, subseries, collection, institution Individual Institution Usage And RDF Conversion discussion

    1. Review of institutional mappings

      1. BPL

        1. Still looking for alternatives to bf:seriesStatement, which it seems like is being used incorrectly (more for commercial series than archival series)

        2. Would be open to using opaquenamespace predicate for archival series

        3. using bf:partOf for collection, but would be open to using dcterms:isPartOf instead

      2. Columbia

        1. No updates from last meeting.

        2. Using dcterms:isPartOf for collection

        3. Archives Hub may have some info on handling series?

        4. RDA has "is subseries of" predicate (http://www.rdaregistry.info/Elements/u/#P60192), could be used for commercial series?

        5. For commercial series numbering, both RDA and Bibframe have predicates to handle this.

      3. Indiana

        1. dcterms:relation for archival series

          1. does not accept literal as range, would need to use dc:relation for literal values

        2. dcterms:isPartOf for collection

        3. not using subseries (or haven't found example yet)

      4. Amherst

        1. No use of series or subseries

        2. using dcterms:isPartOf for collection (will mint URIs for collections)

        3. Bibframe for commercial series: bf:seriesStatement, bf:seriesEnumeration, bf:hasSeries

        4. Bibframe documentation is confusing regarding series – MARC mapping doesn't work well with item-level records for concept of archival series

      5. NYPL: https://docs.google.com/document/d/1CcYUi0o3MErlltiUjbPF6HqRQcL0i80G9Xn7hjgYIv0/edit?usp=sharing

    2. PCDM

      1. could we use this (pcdm:isMemberOf) for both series and collection?

        1. would use the type of the object being associated (collection, series) to determine nature of relationship

        2. this would be less helpful in a metadata-sharing environment

    3. Further investigation needed

      1. bf:seriesOf, bf:subseriesOf – these may be usable, but further research needed

    4. Existing examples of Bibframe in the wild?

      1. Linked Data at the University of Washington

      2. ALCTS BIBFRAME Webinar series

    5. Next steps

      1. Steven will come up with a collaboration document describing 2 different options for further discussion:

        1. generic-predicate-with-typed-objects

        2. series-specific-predicates

  3. part, extension, and recordInfo collaboration document review

    1. https://docs.google.com/spreadsheets/d/103__DdqlTPMXFsANLtEhQpRUbphnL3oeQoOcPygF2GU/edit?usp=sharing

    2. No comments or corrections

    3. We can remove mapping for <mods:part> (Indiana had only example of this, they are OK removing it since it is very institution-specific).

  4. Next meeting: Monday November 28th at 9:00 AM PST / Noon EST

    1. Homework: go back through collaboration documents, find unresolved issues