Call-in Details

• 4pm BST / 11am EDT / 8am PDT
• https://emory.zoom.us/my/rmetz

Attendees

1. Rosalyn Metz
2. Neil Jefferies
3. Ben Cail
4. David Wilcox
5. Peter Winckles
6. Steve Liu
7. Andrew Hankinson (note taker)

Agenda

1. Community updates (introductions, updates, implementations, plans, etc)
2. Releasing 1.0
   1. Requirements to release 1.0
   2. Status of validators
   3. Open 1.0 Spec Issues
3. Next community meeting: Feb 12, 2020 (second Wednesday of the month)

Notes

• Community updates

  • Fedora work -- appreciated! Neat to see things coming together
  • A few pull requests yet to be approved
  • What happens to AUDIT logs? Are they first-class content, or should they be written to the logs directory?
  • OCFL Java Client updates from Peter:
    • Does not do anything with the logs directory yet
    • Working quite well with S3
    • Suggestion for doing a demo of the S3 at the next OCFL community meeting. Peter thinks that's a good idea.
  • Neil has discovered another OCFL repository in Germany; he's trying to get more information about this.

• Review of 1.0 roadmap

  • Status of clients: Julian, Peter are the most advanced
  • List of Error Codes for validators provided
  • List of fixtures: Julian has some Stanford-specific fixtures; need to be cleaned up
  • Tests: Will require fixtures & software

• Peter: Thing holding us up is the lack of specification for extensions, specifically layouts and parameterization. Neil will take this on, and create an issue to track progress on this.

• Next meeting: February 12th.

Audio recording

• 2020-01-08.mp3

Action Items

Previous Action Items

• We need to add language addressing incomplete fixity blocks - resolved with pr-409
• Add language to spec to warn users about problematic characters/sequences - issue-407
• Neil to contact NDSA group regarding openness of preservation storage in the "Levels of Preservation" - Likely OBE