Attendees
General
- Indicates who took minutes -
![(star)](/s/h9vz60/9012/1phy4ty/_/images/icons/emoticons/star_yellow.svg)
- Call-in: Google-hangout at:
Agenda
- Sprint b3 planning
- AuthN/Z
- Triplestore
- 3-4 Upgrade
- Large files
- Clustering
- Search and/or Sequencers
Minutes
- Project and process introduction
- Pivotal tracker
- Tickets, points, phases, etc
- Git flow
- Working branches, submit pull requests
- Unit and integration testing
- Ensure minimum of 75% unit test coverage
- Sonar
- Ticket walk-through and assignments
- Esme
- Working on triplestore tickets, starting with use cases and sample data/queries.
- Documenting triplestore deployment, then how a user can create objects and inspect results in a triplestore.
- Michael
- Scalability issue with nodes that have many children (e.g., fcrepo3 repository with a million objects). All children are loaded and included in the REST API response. Need broader discussion of how to address this (using paging, simulated hierarchy, etc.).
- Eric
- Working on large files, esp. whether performance of SHA1 checksumming can be improved by using native OpenSSL call instead of Java.
- Wiki documentation of large file ingestion.
- Testing whether content added to a projection using the REST API is stored in the projection, or in the repository.
- Matthias/Ye/Markus
- Need to review existing indexing work and develop design document for searching/indexing.
- Design - Customizable Search Index
- Goal is customizable, configuration process, need to identify what can be configured.
- MODS sequencer: should be a more generic XML sequencer, wait for indexing design document.
- Greg
- Access control models to attach roles to fedora nodes. Goal is to add simple policy enforcement in Java (not delegating to external system).
- After that: Adding XACML to a separate workspace and link them to parts of the repository to define policy.
Actions
- All to flush out details of respective tickets
- Setup meeting to discuss scalability of nodes with many children (Greg Jansen)