Page tree
Skip to end of metadata
Go to start of metadata


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


  1. Danny Bernstein
  2. Peter Eichman
  3. Ben Pennell  
  4. James Silas Creel  
  5. Bethany Seeger 
  6. Yinlin Chen 
  7. Aaron Birkland
  8. Jared Whiklo (star)
  9. David Wilcox


  1. Announcements

    1. Release Candidate 3
  2. Release candidate
    1. Release Testing
      1. Samvera
      2. Islandora/CLAW
      3. API-X
    2. Tickets and Pull Requests
    3. CTS

    4. Documentation
    5. Deprecations?
      1. Backup / Restore: deprecated in wiki (as of 5.0) and code (as of 4.7.1)
      2. Copy / Move: deprecated in code (as of 5.0), not in wiki
        1. FCREPO-2940 - Getting issue details... STATUS
      3. Non-Specification features
        1. Transactions
        2. Fixity service
  3. Ecosystem tools:
    1. Camel Toolbox
    2. Java Client
    3. Import Export
    4. Docker
  4. <Your Discussion Point Here>

  5. Please squash a bug!

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  6. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  7. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution


  1. Moved the end of RC-3 testing to December 14. Hoping to get the release out before the holidays begin. Only need to release the fcrepo4/fcrepo4 repository. Should test fcrepo-mint.
  2. Tickets resolved for this RC are Windows build, exploding Shiro and correct responses to interaction model changes.
  3. Java client refactoring - all tickets are complete, there is one PR is left to review. Once that goes in then we could release a 5.0.0 version of that and would be great to get it out close to the fcrepo4 5.0.0 release. Once the fcrepo-camel-toolbox can read the ActivityStreams it should be ready to continue indexing.
  4. Import/Export - what would be the best way forward. We want to be able to import and export from and to 5.0.0 but also export for 4.7 and import into 5.0.0.
    1. Depends on how difficult it would be, but one of the major purposes of the import/export tool was to help with migrations between versions. So it would be nice to allow people to use the one tool to export from their 4.7 Fedora, alter and import into Fedora 5.0. If these stay in the import/export tooling we could end up with a lot of code to convert between versions. But if we keep them small it could be more consistent. Perhaps using the OCFL effort as a guide for on disk representation?
    2. WebACs have changed between 4.7 and 5.0 and this is a data model change. Those changes need to be accounted for and these types of changes will be different for each version of Fedora.
    3. Have to see what the import/export workflow will look like before we can understand what to do.
    4. WebACs used to be linked to the resource they protected, now are implicit so we need to alter the RDF to remove these triples.
  5. What about transactions and fixity, should it remain in the core codebase or move to a plugin or API-X tool.
    1. UMD may have demoed an API-X fixity service which could do the work.
    2. Smaller institutions may find this a benefit because they get it for free. But if we are thinking about deprecating the fixity and transaction service, we should start the discussions with the community at large to see what they are expecting. If we are looking at using an external service then we need to ensure it is easy enough to implement.
    3. If we want to deprecate these for 6.0.0 then do we need to add those messages to the 5.0.0 release? Suggestion to add deprecation notices to the wiki and add the messages to the code in a 5.0.1 or 5.1.0 release.
    4. Aaron is not aware of an API-X persistence fixity service.


  1. RC


  • No labels