2020-04 Fedora 6 Sprint

Participants

1. Jared Whiklo
2. Danny Bernstein
3. Ben Pennell
4. Peter Winckles

Objectives

1. Containment Index
   1. The containment index is designed to be used for:
      1. Keeping track of which Fedora resources are contained by which Fedora containers (resources)
      2. Facilitating the generation of 'ldp:contains' triples for responses to Fedora requests
   2. Success will be defined by:
      1.  Storing containment relationships in index
      2.  Storing containment relationships in OCFL
      3.  Adding containment relationships when Fedora resources are added to a Fedora container
      4.  Deleting containment relationships when Fedora resources are removed from a Fedora container
      5.  Rebuilding containment relationships on application startup (if the index is empty)
      6.  Providing ldp:contains triples in HTTP responses
      7.  Ensuring the HTML UI renders contained resources
      8.  Ensuring the HTML UI navigates containment relationships
2.  Initial JMS Messaging infrastructure
   1. The JMS messaging feature is designed to:
      1. Implement the Notifications section of the Fedora API Specification
      2. Per the Fedora messaging documentation
   2. Success will be defined by:
      1. Deciding on which message bus to use (was Guava)
         1. https://github.com/greenrobot/EventBus (Jared suggested this, but more reading indicates this is primarily for Android and maybe not a good choice)
         2. Guava
         3. https://github.com/bennidi/mbassador → benchmarks compare to Guava (https://github.com/bennidi/eventbus-performance)
      2. Wiring the bus into the code such that events are put on the bus
      3. Marshaling messages into the message format
      4. Publishing of messaging via JMS
3. Long running transactions
   1. Implement start and commit operations on transaction endpoint
   2. Implement cancel transaction on transaction endpoint

Tickets

Sprint board

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.