Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://duraspace.zoom.us/my/fedora 
  

  • Dial-in: 
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

• Join fedora-project.slack.com on the "tech" channel

Attendees

1. Danny Bernstein
2. Andrew Woods
3. Aaron Birkland 
4. Bethany Seeger 
5. David Wilcox 
6. Ben Pennell
7. James Silas Creel
8. Jared Whiklo
9. Jon Roby
10. Peter Eichman

Agenda

1. Announcements

   1. 5.0.1 Release
   2. Publishing CTS Test  Results
      1. https://fedora.info/spec-tests/
      2. https://github.com/fcrepo/fedora.info
2. James Silas Creel 's demo of TAMU's CAP frontend for Fedora (15 minutes)
3. Status of ecosystem tools:
   
   1. Java Client Release
   2. fcrepo-camel
   3. camel toolbox
4. 5.1.0
   1. Ready for review
      
      1. 
      2. 
      3. 
      4. 
      5. "Check if metadata is available in commons.js" : https://github.com/fcrepo4/fcrepo4/pull/1499
   2. Issues that are ready to be worked:
      1. 
      2. 
      3. 
5. 4→ 5 migration and 5 → 5 support.
   1. Next steps 
6. Your issue here 

7. Please squash a bug!

   
   

8. Tickets resolved this week:

   
   

9. Tickets created this week:

   
   

Minutes

Announcements

5.0.1 Release

• Seems like this is ready to go
• Ran into a security issue with a dependency but this has been patched
  • RC2 released, has already been tested by a few people
  • Still needs Linux and Windows sanity builds, Linux test suite run
  • Andrew and Bethany will build on Linux

Publishing CTS Test Results

• We now have a home for test results: https://fedora.info/spec-tests/
• Ideally, those with alternate implementations would run the test suite and issue a pull request to post the results: https://github.com/fcrepo/fedora.info
  • Alternatively, would the Fedora committers run the test suite instead? 
  • Agreement that we should trust implementers to run the suite and report the results

James Silas Creel 's demo of TAMU's CAP frontend for Fedora (15 minutes)

• Needed to edit metadata in Fedora, HTML interface is not fully featured
• Built a Curator's Admin Platform
• Can create new IR views, import metadata schemas
• Visually edit metadata, add fields, batch edit
  • Can restrict which metadata properties are available to add/edit
• Available on GitHub: https://github.com/TAMULib/Cap
• Something like a middle ground between the default Fedora HTML UI and a more fully featured front-end like Islandora or Samvera

Status of Ecosystem Tools

• Java client
  • No further movement, is there a documented release process?
  • Release process is on the wiki
• fcrepo-camel
  • Aaron put in a pull request which is ready for review

5.1.0

• Development driven by need
  • Some interest in state tokens
  • Bring CTS failures to zero
    • 3 issues to resolve in addition to state tokens
• Fixing bugs
• Fedora 4 to 5 migration path
• Scope of Fedora 6.0 is an OCFL-compliant ModeShape replacement
  • Probably makes sense to focus more on this release than on incremental improvements

Migration tooling

• Fedora 4 to 5 tooling
  • Should this be part of the import/export tool or a separate utility?
    • A separate tool would be less of a maintenance headache
    • Maybe bundle a separate utility into the same import/export pipeline?
    • Have we standardized the on-disk format for exports? Is this aligned with a particular version of Fedora? Could be tied to a version of the Fedora API.

Actions

• Checking with Peter Eichmanregarding: UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
• Danny Bernstein will reach out to Yinlin Chen to see about a fcrepo4-docker release with the 5.0 architecture.