Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Announcements
  2. Check-in regarding the double meeting format
  3. Status of  https://github.com/pwinckles/ocfl-java-parent  move into ocfl Github repo
  4. Opportunities to chip in:
    1. API Test Suite PRs
      1. https://github.com/fcrepo/Fedora-API-Test-Suite/pulls
    2.  Minimal 4 →5 migration needs testing  and code review:
      1. https://github.com/fcrepo4-exts/fcrepo-upgrade-utils/pull/17
  5. Status on organizing a Fedora documentation review
  6. Update on Fedora 6 Pilots 
  7. Sprint Planning
    1. 6.0 Architecture Review
      1. Versioning review from last week:
        1. Clarification of the proposal: 
          1. OCFL transactions always result in new versions;  we will not support unversioned content in Fedora
          2. From Fedora's point of view, the current state of a resource is the most recent version (ie HEAD)
          3. By default Fedora will display only "significant" versions in the list of mementos.
          4. "Significant versions"  are OCFL objects that contain a marker file in the content directory (possibly something like content/.fcrepo/memento)
          5. Implication:  versions cannot be removed ( because removing content from OCFL is likely to be controversial).
        2. Questions: 
          1. Is it important to be able to have Memento timestamps synchronized across a multi-object transaction?  In other words, are users going to want to be able to version changes across a single time-slice? 
            Ie: 
                http://localhost:8080/rest/object1/fcr:versions/20190822122001
                http://localhost:8080/rest/object2/fcr:versions/20190822122001
                http://localhost:8080/rest/object3/fcr:versions/20190822122001
      2.  Multi-object transaction implementation ideas
    2. Transaction Sidecar Spec Update
  8. Status on organizing a Fedora documentation review
  9. Your topic here...

Tickets

...

OCFL Java Client  - let's get Peter Winckles and Aaron Birklandtogether for a discussion about a common java ocfl client interface / interaction model

Bethany Seeger :  will take a look at Greg Jansen 's PR.


Add a discussion point around API Test Suite modifications and overall spec compliance disucssion.

Joshua Westgard  to look into PR on migrations the next week.

Danny Bernstein  to run upgrade routine on  sample (e.g. plant patents )datasets



Actions

  •  Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
  •  Peter Eichman   and maybe Ben Pennell to make recommendations re transaction side car specification.
  •  Andrew Woods will look into java 11 transition

...