Page tree
Skip to end of metadata
Go to start of metadata

Time/Place

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

Attendees 

Agenda

  1. Status of "in-flight" tickets

    Key Summary T Created Updated Assignee Reporter P Status Resolution
    Loading...
    Refresh

  2. Memento as versioning HTTP API. FCREPO-1275 - Getting issue details... STATUS

  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!

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

  2. Tickets resolved this week:

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  3. Tickets created this week:

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Minutes

1. Discussed  FCREPO-1840 - Getting issue details... STATUS  ,   @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)