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
• Esmé Cowles
• Ben Pennell 
• Michael Durbin
• Peter Eichman
• Joshua Westgard
• Bethany Seeger
• (Please add your name)
  
  

Agenda

1. Announcements
   1. 4.7.5 Release Process begins
2. 4.7.5 release - Planning for week of January,15th 2018
   
   1. Release manager - Osman Din
   2. Volunteers
      1. Testers
         1. Danny Bernstein
         2. Joshua Westgard
         3. Peter Eichman
         4. ?
      2. Someone to review 4.7.5 commit message for signs of missing documentation?

      3. Preparers of Module Release Candidates

         Module	Who?
         fcrepo-module-auth-rbacl	Osman Din
         fcrepo-module-auth-xacml	Osman Din
         fcrepo-module-auth-webac	Osman Din
         fcrepo-mint	Osman Din
         fcrepo-audit	Osman Din
         fcrepo-webapp-plus	Osman Din
         fcrepo4-vagrant	Osman Din

   3. Resources:
      1. component release process tracker: https://docs.google.com/spreadsheets/d/1I_zTMxh2l2rf2wpafoTwhSTR5GZuEoaTcZmTKCI3xT4/edit#gid=1769378986
      2. Release Testing - 4.7.5
3. Fedora API Test Suite... needing:
   
   1. Try the tool against an API implementation
   2. Code reviewing the tool... lots of low-hanging fruit
4. Simple, synchronous query in Fedora
   1. What will it take to make this happen?
   2. Prior art
   3. Queries to support
      1. select ?s where {?s ?p ?o}
      2. select ?s where {?s <some-pred> ?o}
      3. select ?s where {?s <some-pred> <some-object>}
5. Tickets requiring attention
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Bethany Seeger to review?
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Ralf Claussnitzer to explore?
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Ben Pennell to explore?
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - on hold or close?
6. 5.0.0 release
   1. API Alignment
   2. Pairtrees?
7. Beyond 5.0.0 - Areas of improvement
   
   1. Persistence?
   2. Journaling?
   3. Simple, synchronous query?
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

2. Release

• Esme can help with Samvera testing
• Osman will perform builds of module release candidates, unless he wishes to delegate
• May be a challenging release given holidays

3. API test suite been running for a while. Has anyone had a chance to look at it?

• Danny hasn't looked at it yet, but seems easy to use. Going to try it out this week
• Interested in people trying it against other implementations, like Trellis and Cavendish.
• Bethany: Is this considered done as far as the contractors are concerned?
  • Danny: Good question, the repo doesn't say how complete it is. Will check in with Andrew
  • Since the API alignment isn't complete, it shouldn't pass against modeshape impl yet
  • Code reviewing the tool?

4. Simple querying in Fedora?

• Previously, cbeer had added this functionality, but it had been later removed
• Is data structured for this in modeshape to be reasonably performant?
• Mike: Was one of the agitators for this, opposed it being cut
  • Some stuff is inferred, some not directly searchable
  • What types of queries do we want to support?
  • What exceptions are we willing to tolerate?
  • Extension spec?
  • Is it okay if it doesn't work consistently on server managed triples, like date fields?
  • Just wants to be able to search dc:identifier. This would work, modeshape has an index that can be searched.
• Esme: Valkyie, making a list of queries that the repository needed.
  • Needed queries
    • all objects of given type
    • Doing a search for dc:identifiers
    • They will come up with a list of queries they need
• Danny: Would it be helpful at this point to fill out the list
  • Discuss some of the known limitations of modeshape's internal indices
    • Mike: Last modified date is across two fields. Might need to normalize way stored in fedora. Need to work out if this is needed
    • Esme: Types and containment triples are harder to make searchable
    • Search for non-server managed triples that are directly assigned are easy.
    • RDF type are not stored in the index modeshape maintains. That is inserted into responses.
    • Use case: find all objects of a type in order to do bulk object on it
    • Can't search on fcr namespace and ldp namespace. Might be okay to not support those, but it would be weird to have an LDP server that didn't support it
    • Could add support for this in after if there is demand for it
• Mike will start document to gather first pass at known limitations of implementation and requirements

Action Items

Action: Check in with Andrew about completeness of the test suite

Action: Mike will put together a document with first pass at the feature set.