...
- Initial steps with Java Client Library
- Additional acceptance tests
- System/Admin test examples?
- Load test examples?
- Other?
- New name for project: fcrepo-jms-indexer-pluggable?
- Handling externally managed content
- ...
Minutes
- Java client library
- Use cases seem to be covered by REST actions on resources
- #Objects
- #Binary Content
- #Fixity
- #Identifiers
- #Namespaces
- #Node types
- #Transform
- Development work will likely take place within the community rather than within a sprint
- Those interested: Esmé, Konrad, Martin, Greg
- Evaluating LDP clients
- LDP4J
- Not very much test coverage
- Marmotta
- Some Marmotta assumptions are built in
- Need to create a table comparing clients to requirements
- LDP4J
- Should the new client implement the existing fcrepo-kernel interfaces?
- Easier to build on a single API and make adjustments as needed
- There may be incompatibilities between the internal API and LDP
- Roadmap
- Should be able to put together an initial implementation within 4-6 weeks
- This will be a volunteer effort from community members outside the Fedora 4 sprints
- Use cases seem to be covered by REST actions on resources
- Acceptance tests
- Hopefully tests will be conducted by people within the community
- Test templates have been added
- Need to brainstorm additional tests
- Load X number of objects/datastreams
- Setup server monitoring
- Testing for high availability
- Rename fcrepo-jms-indexer-pluggable
- fcrepo-jms-consumer?
- fcrepo-message-consumer?
- fcrepo-consumer?
- Handling externally managed content
- Currently you can create a well-known property (fedorarelsext:hasExternalContent) on an object that points to the external file
- From a user perspective, it would be nice to not have to care if the file is actually in the repository file system or in an external file system
- Could add some logic to automatically look for this well-known property when requesting the file
Actions