...

1. Announcements
   1. 2020 Q1 Sprint Doodle: https://doodle.com/poll/es7nwdppt94rv2pz
2. State of the code review: open tickets
3. Fedora 6 Demo
   1. What
   2. When
4. Open Questions
5. <your topic>

...

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

4. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Notes

...

1. OCFL call - discussed a couple issues, planning to add some language to OCFL spec or implementation notes. Stanford has a new validator (Ruby gem).
2. Desire to make sure Fedora 6 runs properly in the cloud. Can test S3 on OpenStack. Need details on what exactly people want to do in the cloud.
   1. ocfl-java client - starting to add support  for S3 (incomplete). More complicated, may have more requirements (eg. DB).

...

...

...

1. realigned with proposed interface, writing code to retrieve data from DB - WIP PR. Discuss later today.

...

1. shared doc about handling server-managed triples, and OCFL objects from outside Fedora.
   1. 4 approaches: ignore SMT, how much to interpret RDF/directories on OCFL objects. How Fedora would behave in different cases.
   2. leaning toward ignoring SMTs, but still discussing.
   3. working on follow-up document.
   4. discuss more in Part 2.
   5. is it possible to push json-ld in, and get it exactly back out? Agreement to trim SMTs.
   6. info:fedora URI from Fedora 3 - could make it configurable to support multiple use-cases. Optionally translate URI prefix.
   7. roll out simplest things first, then add more features.
   8. should RDF files be containers? what should migration-utils do? Discuss in doc.

...

1. object deletions - root of Archive Group - add a tombstone, then delete ocfl object when tombstone is deleted?
   1. F4/5 - when object is deleted, you get a tombstone, and all the info is all lost
   2. what would other backends support? It's not part of the API. Could be specific to OCFL backend to allow bringing back an object that was deleted.
   3. could provide access to version history of tombstones, or not.
   4. Are people OK with the memory of a deleted object still being there?
   5. Could fit somewhat with Fedora 3 'D' state.

Actions

•  Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file David Wilcox will review the NDSA matrix and pull out the concrete technical requirements that could be considered during the Fedora 6 development.
  
•  Call for comments on https://docs.google.com/document/d/18rSFqqoxixmozZrgPKON59Ojpg5iOu4lsHDNMm23soY/edit# till tuesday
•  Clarify in in documentation that multiple simultaneous writes to OCFL are not supported

...