Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To the degree possible, it is helpful to know who is able to commit to the sprint for any of the months in this period. Please list your name if you are available to participate in any of the sprints!

April 6 - 10

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
      2. Adding containment relationships when Fedora resources are added to a Fedora container
      3. Deleting containment relationships when Fedora resources are removed from a Fedora container
      4. Rebuilding containment relationships on application startup (if the index is empty)
      5. Providing ldp:contains triples in HTTP responses
      6. Ensuring the HTML UI renders contained resources
      7. 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
        2. Guava
        3. ?
      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

Tickets

Sprint board

  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3164
  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3247
  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3248
    Initial JMS Messaging infrastructure
  • need to decide what to use for message bus (was guava)
  • wiring into the code so events can get put on the bus
  • publishing of messaging
  • marshaling (which should already exist, so probably done)
  • Tickets:
  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3249
  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3250
  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3251
     

Participations

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

...