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
• Kevin Ford
• Longshou Situ
• Jim Coble
• Yinlin Chen
• Doron Shalvi  
• Michael Durbin 
• Andrew Woods
• David Wilcox
• Joe Harrington
• Bethany Seeger
• Esmé Cowles
• A. Soroka
• Unknown User (acoburn)

Agenda

1. Updates from MW-FUG
2. Who is attending Code4Lib L.A. next week?
3. How are Islandora and Hydra clients using LDP-RS ETags?
4. Outstanding issues on Fedora API Specification
5. Updates/Next steps for Fedora API Adopters Guide (previous meeting notes)
   1. Coding opportunities for aligning Fedora implementation with specification
6. Michael Durbin : Interested in testing migration of Fedora 3 PIDs?
7. Opportunity to attend Southern Miss IR conference and represent Fedora
8. CfP for SEMANTiCS conference in September
9. Opportunities for contribution: low-hanging bugs to be fixed
10. For your pleasure: Drastic/CNI presentation video
    
    1. FCREPO-1976 - ldp:contains can be asserted via hasMemberRelation OPEN
    2. FCREPO-2398 - Audit machinery causes the emission of events with info: URIs. OPEN
    3. FCREPO-2379 - ldp:constrainedBy Links point to incorrect locations OPEN
    4. FCREPO-2378 - Missing ldp:constrainedBy header on ldp:Resource creation OPEN
    5. FCREPO-2399 - LDP-RS that describe LDP-NR incorrectly advertise allowable methods OPEN
11. ...

12. Status of "in-flight" tickets

     Click here to expand...

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

1. Updates from MW-FUG
   
   1. Kevin, Andrew, Michigan, Northwestern, Notre Dame, Art Institute of Chicago were in attendance.
   2. Logistics were challenging to allow a full suite of attendees.  The result was a tighter, more advanced group that enabled good discussion.
   3. Michigan in advanced state.  For example, they have advanced the Java client. It would be nice to funnel their work back to community.
2. Who is attending Code4Lib L.A. next week?
   1. Esme, Longshou, Danny, Andrew, Mike, Bethany, Joe, Ben P., and others attending.  Perhaps meet up later in the week.
   2. Two related workshops - Import/Export, Performance.
3. How are Islandora and Hydra clients using LDP-RS ETags?
   1. Ben P. updating Java client to be in line with Fedora 4.7.1.  Weak ETags have returned to RDF sources.  Build these into Java client?  Not sure.
   2. Hydra - there is an existing ticket to implement using If-Modifier-Since (Esme).  Would cover vast majority of use cases, but may fail in some cases involving multiple synchronous updates.
   3. Hydra is using If-Unmodified-Since, since 11/21/2016: https://github.com/projecthydra/ldp/commit/36520b2a78744f0610d75702384330c43bbf8e21
   4. CLAW - not sure what is going on in this area.  They wanted to use ETags, but are not due to ETag issues.  In current version of CLAW, using an identifier instead.  Not sure what they will do long term.
4. Outstanding issues on Fedora API Specification
   1. Three of these issues just need relatively simple pull requests.
   2. Some of these issues need better clarity, specifically in numbering and referencing.  The document is difficult to follow, especially for those new to the discussion.
   3. Recent change in document - there is now a permalink next to every header, which should be used for referencing.
   4. Andrew - Getting resolution in this spec is currently the highest priority item in the community.  Need more community input and review to move things forward.
   5. Esme - For many items, all of the options seemed reasonable.  Difficult to pick one approach over another.
5. Updates/Next steps for Fedora API Adopters Guide (previous meeting notes)
   1. Discussed last month, more meetings coming up.
   2. Aaron Birkland working on fixity section.
   3. Need sections created in the Adopters Guide that match up with the Spec - looking for volunteers.
   4. Volunteers received for sections on Atomic (Jared), Fixity (Esme), Versioning (Danny).
   5. Need volunteers to support sections on Resource management, AuthZ (WebAC).
   6. Coding opportunities for aligning Fedora implementation with specification.
6. Michael Durbin : Interested in testing migration of Fedora 3 PIDs?
   1. If using an apple tree design, move and copy operations do not work; but these operations are not in the spec anyway.  There is also a bug in Fedora 4 in emitting messages when using this design.
   2. How should URIs be migrated from F3 to F4?  Do we need to support F3 style URIs such as /objects and /datastreams?
   3. In general, a translation layer is recommended to handle this scenario.  Possibly, API-X could be used to implement such a layer.
   4. It may be better to migrate data, rather than having a complex translation layer.
   5. The migration tool will be updated to support the latest version of Fedora, but is first waiting on completion of the third phase of import/export.  Nick Ruest was leading this effort but cannot continue due to time constraints.  Andrew is putting out feelers for who may be able to pick this up.
   6. A multi-disciplinary team, including developers, testers and documenters, was effective for the second phase of import/export.  will try this approach again for the third phase.
   7. What are some import/export use cases?  Some use cases are to move between implementations of Fedora.  Such a tool should be agnostic and not depend on internal artifacts such as Modeshape.
7. Opportunity to attend Southern Miss IR conference and represent Fedora - contact David Wilcox if interested.
8. CfP for SEMANTiCS conference in September - if you are interested in attending this conference, and presenting or collaborating on a presentation regarding semantics with Fedora, contact David Wilcox.
9. For your pleasure: Drastic/CNI presentation video