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 

• Unknown User (acoburn)
• Bethany Seeger
• Nick Ruest 
• Yinlin Chen 
• Esmé Cowles
• James R. Griffin III
• Jared Whiklo
• Andy Wagner
• A. Soroka
• David Wilcox
• Michael Durbin
• Osman Din
  
  

Agenda

1. Status of "in-flight" tickets

   Click here to expand...

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

2. Memento as versioning HTTP API. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Status of removing JCR from fcrepo-kernel-api. See also: https://github.com/fcrepo4/fcrepo4/pull/968

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   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. Discussed  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  ,   @A. Soroka the internal method check, giving a RDF case, set a default if you ask me a mimetype and I don't know what is it, I just return triples and remove 500.      

2. Memento is a popular and widely-supported specification for versioning, many LDP platforms are choice Memento. Thus, we try to adapt Memento into Fedora's HTTP API for versioning. People in the meeting all agreed to proceed it. @A. Soroka will send out messages to the fedora communities.

3. Cleaning up the fcrepo-kernel-api, including moving JCR and modeshape (been done). After removing JCR, any implementation of the Fedora does not have to know about the JCR. There is on open request https://github.com/fcrepo4/fcrepo4/pull/968 . This PR pushed JCR Session into the HTTP layers. You still need to address JCR Session in the HTTP layers. This is the intermediate implementation before completely removing JCR out of fcrepo-kernel-api.

Still need to discuss and clarify the definition and usages about the "transaction" in Fedora. e.g. @mike Would it make sense to call our new session construct a "transaction", since that's essentially what it is?
or if we use different backend which does not support transaction (e.g. hadoop)? An idea is to provide an optional for users to chose transaction or not., or an API-X module. Need to know how the communities think about it. (e.g. islandora community)