Skip to content

2018.08.01 Editors Meeting

Jump to bottom Edit New page
Rosalyn Metz edited this page Aug 1, 2018 · 8 revisions

Call-in

https://duraspace.zoom.us/my/fedora

Attendees

  • Andrew Hankinson (Bodleian Libraries)
  • Simeon Warner (Cornell)
  • Julian Morley (Stanford)
  • Rosalyn Metz (Emory)*
  • Andrew Woods (DuraSpace)
  • Neil Jefferies (Bodleian Libraries)

Regrets

(* indicates the notetaker)

Agenda

  1. Rescheduling community (and editors) meetings
  2. Outstanding PRs:
  3. Use of RFC2119 language, issue 35
  4. Relationship with BagIt bags? - https://github.com/OCFL/spec/issues/50
  5. Adding content to the specification

Notes

  1. Rescheduling community (and editors) meetings
  • OCFL Editors meetings: 1st and 3rd Wednesday of the month @11am ET
  • OCFL Community meetings: 2nd Wednesday of the month @11am ET
  • Skip the August OCFL meeting
  1. Outstanding PRs:
    • https://github.com/OCFL/spec/pull/44 - WIP: Object definition expansion
    • directories conversation
      • keep Rosy's suggestion for directories
      • if you want to store an empty directory then you should put a .keep file in the directory. see BagIt spec description: "Payload manifests only include the pathnames of files. Because of this, a payload manifest cannot reference empty directories. To account for an empty directory, a bag creator may wish to include at least one file in that directory; it suffices, for example, to include a zero-length file named ".keep"."
    • object definition
      • how to make an object is best practice, not a spec
      • an ocfl object is defined by what you are looking to preserve
    • uk v. us v. canadian spelling
      • we should do uk spelling because OXFORD :/
    • https://github.com/OCFL/spec/pull/45 - New: Begin the section on the logs directory
    • If you want to store the information about fixity checks and what not, you can do that in the log directory (or you can do it in your repository if you prefer)
    • Does the log directory have to exist? No it doesn't, it we should use the word MAY rather than SHOULD.
    • changing the requested paragraph to non-normative
    • https://github.com/OCFL/spec/pull/48 - Add .travis.yml
    • MERGED
  2. Use of RFC2119 language, issue 35
  • approved and closed
  1. Relationship with BagIt bags? - https://github.com/OCFL/spec/issues/50
  • We should talk about this in person because it is a more nuanced conversation
  • Rosy would like to have more solidified with inventory.jsonld
  • Philosophical question: why isn't a version just a bag (paraphrasing); applying linked data sensibilities to BagIt; where would BagIt overlay on this?
  • when you send to a Distributed Digital Preservation (DDP) service you may use BagIt to send a whole bunch of versions to that DDP and then successive versions to them in a single bag.
  1. Reviewed these real quick to closed
  1. Adding content to the specification

Action Items

  • Julian needs to approve the new community meeting schedule in the Slack Channel
  • Andrew H. to reword #45 based on our conversation
  • Andrew H. to create a ticket so we can be explicit about empty directories
  • Neil to propose language about what's in an Object (we are agnostic) in #44
  • Andrew H. to then make updates in #44 around directories
  • Simeon to create a ticket about language preference US v. UK v. Canadian
  • Simeon to create a ticket to capture JSON-LD things he's laid out in a comment in #1

Previous Action Items

Add a custom footer

Home

Meetings

  1. Community Meetings
  2. Editorial Meetings

Reference

  1. Roadmap
  2. Change Process
  3. Style Guide
  4. Validator Codes
  5. Implementations
  6. Abstract Client API
  7. Papers and Presentations on OCFL
  8. Related Reading
Clone this wiki locally