Participants- Jared Whiklo
- Danny Bernstein
- Ben Pennell
- Peter Winckles
Objectives- Containment Index
- The containment index is designed to be used for:
- Keeping track of which Fedora resources are contained by which Fedora containers (resources)
- Facilitating the generation of 'ldp:contains' triples for responses to Fedora requests
- Success will be defined by:
Storing containment relationships in index Storing Storing containment relationships in OCFL- Adding
Adding containment relationships when Fedora resources are added to a Fedora container - Deleting
Deleting containment relationships when Fedora resources are removed from a Fedora container - Rebuilding
Rebuilding containment relationships on application startup (if the index is empty) - Providing
Providing ldp:contains triples in HTTP responses - Ensuring
Ensuring the HTML UI renders contained resources - Ensuring
Ensuring the HTML UI navigates containment relationships
- Initial
Initial JMS Messaging infrastructure- The JMS messaging feature is designed to:
- Implement the Notifications section of the Fedora API Specification
- Per the Fedora messaging documentation
- Success will be defined by:
- Deciding on which message bus to use (was Guava)
- https://github.com/greenrobot/EventBus
- Guava
- (Jared suggested this, but more reading indicates this is primarily for Android and maybe not a good choice)
- Guava
- https://github.com/bennidi/mbassador → benchmarks compare to Guava (https://github.com/bennidi/eventbus-performance)?
- Wiring the bus into the code such that events are put on the bus
- Marshaling messages into the message format
- Publishing of messaging via JMS
Long running transactions ACLs- Implement start and commit operations on transaction endpoint
- Implement cancel transaction on transaction endpoint
- Success will be defined by
- All ACL integration tests will be re-enabled
ACL-aware deletions will function as expected
TicketsSprint board Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-3164 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-3247 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-3248 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-3249 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-3250 |
---|
|
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-3251 |
---|
|
|