Attendees
General
- Indicates who took minutes -
- Call-in: Google-hangout at:
...
- Crossing off (Unknown User (escowles@ucsd.edu) & Eric James):
- Store/Deliver Large Files
- Managed External Datastreams
- Gaining additional confidence with basic Clustering (Unknown User (escowles@ucsd.edu))
- Defining scope and approach for Content Modeling (A. Soroka)
Minutes
- Filesystem federation - Eric
- First task is to check whether filesystem federation connector keeps in sync with filesystem changes (added files show up in the REST API, deleted files disappear)
- If so, then the next step is to document the behavior and get federation ready for acceptance testing
- If this doesn't work, then create followup tickets to fix
- Large file support
- Interrelated with filesystem federation since large files are a major use case for federation
- Use cases talk about dropbox functionality, could be achieved by using federation and being able to copy a resource from one storage resource to another
- Related to ticket https://www.pivotaltracker.com/story/show/65581498
- Clustering - Esme
- Start by testing new puppet script (https://github.com/futures/puppet-fcrepo) on UCSD VMs
- If it doesn't work, then diagnose networking/VM options
- Indexing - Eric/Esme
- fcrepo-jms-indexer-pluggable needs to be updated to handle new event type format (https://github.com/futures/fcrepo4/pull/264)
- Use case analysis for determining what functionality needs to be provided by the indexer and what is the responsibility of applications
- See Triplestore Use Cases
- Some triplestore use cases reference iTQL-specific query functionality – do we need to revisit Mulgara support, or support for similar functionality in other triplestores?