Time/Place

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

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access:  https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees 

• Danny Bernstein
• Jared Whiklo 
• Bethany Seeger 
• Ben Pennell
• 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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Other work in-progress
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
5. 4.7.5 release
   1. Deprecations
   2. Non-API-Alignment fixes/improvements
   3. Future of fcrepo-audit? -  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Peter Eichman is on it
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - waiting on feedback from Chris Colvard
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - ready to go? Danny Bernstein?
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - ready to go? Danny Bernstein?
8. ...

9. Tickets In-Review

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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: 
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - 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.  
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - duplicate of 2623?  Sounds like it. Jared Whiklo will update the ticket.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. 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 - November / 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.  

Actions

• Danny Bernstein will try to push forward on FCREPO-1262.
• Doron Shalvi will write up a description of the Fedora URI concerns and post to the Fedora listserv to start discussion.