...

• Danny Bernstein
• Jared Whiklo 
• Doron Shalvi 
• Bethany Seeger Seth Shaw
• Ben PennellJames L Woods
• Esmé Cowles
• Aaron Birkland
• David Wilcox
• Simeon Warner
• Peter Eichman
• Yinlin Chen
• Andrew Woods

Agenda

1. New Fedora Clustering configuration

2. Fedora representative at Data Help Desk at AGU Fall Meeting
3. Samvera Connect next week
4. Sprint follow-on tickets

   1. Memento work in-progress:

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2617

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2625

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2623

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2622

   2. Other work in-progress

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2632

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2585

5. 4.7.5 release
   1. Deprecations
   2. Non-API-Alignment fixes/improvements
   3. Future of fcrepo-audit? - 

      Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2648

   4. This month?
6. 5.0.0 release
   1. API Alignment
   2. Abandoning the single subject restriction: any feedback/illuminating discussion on the list?
   3. Pairtrees?
7. Tickets requiring attention

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2650

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2649

       - Peter Eichman is on it

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2544

       - waiting on feedback from Chris Colvard

   4. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2486

       - ready to go? Danny Bernstein?

   5. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2492

       - ready to go? Danny Bernstein?
8. ...

9. Tickets In-Review

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

   
   
   

...

Minutes

• Discussion regarding new clustering configuration PR:  https://github.com/fcrepo4/fcrepo4/pull/1265

  • It would be interesting to understand the context for this PR

  • Is clustering being used with this new configuration?
• David Wilcox spoke about the AGU Fall meeting that will be in New Orleans in December. If you're interested in attending and representing fedora (essentially taking shifts at a table), contact David Wilcox
• Issues: 

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2623

     - is ready to be merged. Andrew Woods will check in with Aaron Birkland before merging it, though it seems like it's ready to go. 
    • there needs to be some work done with converters to have the subject returned correctly for getting the timemap - so that the public facing side is `fcr:versions`, but the internal node name is `fedora:timemap`.  Sounds like `fedora:timemap` is being returned right now and shouldn't be.
    • a test case needs to be written to test the subject returned when doing a GET on a LDPCv.  

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2622

     - duplicate of 2623?  Sounds like it. Jared Whiklo will update the ticket.

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2585

    Danny Bernstein working on - sounds like it's almost ready to go. 
• The work on fcrepo versioning is going into a versioning branch right now. Once the basic versioning/memento functionality is there, it will be merged into master. 
• 4.7.5
  
  • Incremental Release - Novemeber / December time frame? 
  • fcrepo-audit - Question is should we continue to support this module or deprecate it? 
    • Seems like there is general agreement about deprecating it, however, maybe not quite yet until we have a durable solution to replace it with. 
    • Peter Eichman - talked about the issues they've been seeing. Having the audit messages added in the triple store (via fcrepo-camel-toolbox indexer) is useful and much easier to access audit info that way.
      
      • switched over to indexing triplestore camel route to track audit - will be using that in their production repo starting next week.  It is a separate dataset in fuseki. 
      • thinking about creating audit service that listens to JMS messages and writes to log file(s) - anyone else interested in that?
        • One could use the various mature filesystem tools available to manage logs this way (for rotating, viewing, graphing, etc.)
        • Their first thoughts on the first pass at this:  considering just dumping the JSON messages to disk. 
        • Might be able to look at fcrepo-camel-serialization tool for inspiration/code
    • There are currently two audit capabilities - fcrepo-audit & fcrepo-camel-toolbox triplestore indexing tool.  
      
      

...