2021.04.20 Editors Meeting

Call-in

See invite

Attendees

• Julian Morley (Stanford)
• Rosy Metz (Emory) *
• Simeon Warner (Cornell)
• Andrew Woods (Harvard)
• Neil Jefferies (Oxford)

(* indicates the notetaker)

Agenda

1. Review previous action items
2. Follow up on engaging the community
3. Spec
   1. Open PRs
   2. Open Issues
   3. Most recent issues
4. Extensions
   1. Open PRs
   2. Open Issues
5. Fixtures
   1. Open PRs

Notes

1. Review previous action items
   • Andrew upgraded slack github integration
   • Zenodo has a community function, 50gb per file size limit, Neil is going to set that up.
   • Andrew talked with Justin, Archivematica is trying to serve out their output and wants to be able to support new formats including OCFL.
   • Neil was in a meeting with Wellcome, Cambridge, National Library of Scotland are working on a cloud repository together and they are most likely going to use OCFL for their storage. So we may be getting feedback on cloud storage and OCFL. Wellcome is pushing Archivematica to produce AIPs in OCFL format.
   • E-ARK is creating a spec in which there would be a bag in an OCFL object. There are a few changes that we would need to make BUT we could end up being the standard for preservation for Europe. Neil is checking in to see if they can input use cases into our Use Case repo so they can contribute. Sounds like we are getting more use cases that could move us forward with v2 of OCFL.
2. Follow up on engaging the community
   • We discussed creating a survey to gauge community interest. Should we move that forward?
   • We could send out a survey to see who is using or considering using the specification. Send to a broad scope of listservs.
   • Contextualizing what we are thinking for version 2 of the spec. Perhaps we need to review the Use Case repo and determine what those uses cases are that we are thinking of including in the repository.
   • NEXT STEP: review use case repo during our next meeting.
3. Spec
   • Is there enough stuff going on that we should produce a 1.1 version of the spec? Everyone was in agreement.
   • There is a some clarification needed and adding musts and shoulds would be useful. In the community meeting Peter Winkles suggested section level error codes.
   • Create a milestone, declare season open for 1.1, request the community add tickets, then start to prioritize the backlog.
   • All PRs since the 1.0 release
   • Draft email to the community letting them know that we are ready to start work on a 1.1 version of the spec
   • NEXT STEP: Review email at the next meeting, then we can send it out to the various lists we used to promote 1.0

Action Items

• Neil to draft email to the community letting them know that we are ready to start work on a 1.1 version of the spec.

Previous Action Items

• Andrew to upgrade Slack GitHub integration.
• Andrew will follow up with Justin Simpson from Archivematica about possible connection.
• Neil to look into Zenodo for hosting our community meeting videos.