Child pages
  • MODS and RDF Call: 2017-11-27
Skip to end of metadata
Go to start of metadata

Time: 9am PDT / Noon EDT

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

Homework:  White paper comments and Collaboration document spreadsheet clean-up

Moderator: Eben English

Primary notetaker: Julie Hardesty (Etherpad Link: https://etherpad.wikimedia.org/p/MODS_and_RDF_Call__2017-11-27)

Attendees:

Agenda:

  1. Review formatting options for final documentation
    1. White paper: https://docs.google.com/document/d/1ffCyIirUkESLefBehafbacsLb_Rq7KJbTxxeoQCyLpw/edit#
      1. tables and examples at end show options for displaying mapping

      2. single list of namespaces and prefixes

      3. Emily's use of tables with MODS elements as headings makes sense and is clearest

      4. Eben's use of examples directly in documentation is helpful as well - people can scan for the thing they are trying to do and see example right there

      5. provide explanation for each element mapping (might be what usage scenario cells are for)

      6. add additional column to express MODS elements and attributes that would indicate mapping to properties?

        1. might get messy in table structure but not sure how best to provide this information

        2. could also use Usage Scenario column to describe how to evaluate MODS for mapping

      7. How much of examples should be provided?

        1. one option - single prime example with link to spreadsheet

        2. another option - provide all examples in single document (like DPLA MAP, Europeana)

          1. Pros:
            1. not needing to jump to different places to see documentation

            2. easier to manage over time if it's all in one place

          2. Cons:
            1. gets long and hard to read
            2. presence of minted object examples may be confusing and off-putting
            3. maybe consider having a web site where minted examples hidden/expandable (like a Github wiki or something similar)?

          3. supporting rich bib description is more complex when trying to map "correctly" or strictly to reproduce what MODS is representing

          4. nature of graph model is to have this complexity

          5. Minted local objects might be more useful in time with Samvera software or elsewhere as tech matures

        3. THIRD OPTION - Separating into different sections to show direct mapping with each MODS element and then a local minted object section with MODS elements that have minted objects

          1. Can try with what we have now and would have to repeat XML examples

          2. Worth trying and need to provide explanation

      8. need to have design and formatting set with these examples before we get too far into creating this documentation

      9. discuss over email - Eben will take first attempt at reworking examples using THIRD OPTION

      10. Review prefix for dc and dc11

        1. known in larger community as dcterms and dc but Ruby gem uses dc and dc11

        2. need to consider audience and talk about this again

        3. maybe wait to see what feedback is when documentation is sent out for review

  2. Next meeting: Monday 12/11, 12 PM EST
  • No labels