Table of Contents
|
Time/PlaceThis meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info: AttendeesAgenda- 20 - Review current fcrepo4 work.
- Triple store integration
- Customizable search indexes
- Large file performance
- Fcrepo3 migration
- roles-based AuthZ
- 10 - Scalability of the API for children
- Moving away from using Jena Model as container for triples in the kernel
- Moving to a streaming API all the way through the kernel
- 10 - Stakeholder needs in a customizable search indexer (Solr)
- 15 - Wiring and configuration (see also Comparison - Wiring)
Previous Actions
Minutes- reports on current work
- triple store integration - Esme
- will be looking at Mulgara and JMS indexer to incorporate non standard SPARQL queries
- looking at multiple levels based on reviewing use cases
- kitchen sink now has triple store ( Question for Andrew: Is vm built from master automagically )
- Answer from Andrew: "Yes, Jenkins deploys kitchen-sink on each commit to: http://futures6.fcrepo.org:8080/fcrepo/rest/"
- large file performance - Eric
- 3 avenues explored
- researching different configuration settings ( e.g. caching hashes showed dramatic improvement )
- Scott commented on how fixity done in Fedora3
- fyi, looks like we actually read the data and do a new checksum when we do the fcr:fixity check, the low-level code that does the reading/checksumming is here:https://github.com/futures/fcrepo4/blob/master/fcrepo-kernel/src/main/java/org/fcrepo/kernel/utils/LowLevelCacheEntry.java#L92 (Esme)
- migration - Mike
- 90% completed and the remaining 10% is slow
- working on display, especially focused on performance when many children as displayed
- roles based - Greg
- will be working on integration test needed for effective roles for tree object
- roles can have expanded permission set ( Scott )
- XACML will be used for each role
- policy enforcement point
- API for children
- effective hierarchy needed to maintain good performance
- a couple of tests suggested (Greg has the action items)
- search indexer - Markus
- external indexer (esp. Solr)
- Design - Customizable Search Index
- Scott described how they use Solr in F3. change METS to Solr XSLT to customize
- what should be indexed? data streams, text extraction from spreadsheet, PDF, etc.
- Possibly use METS which can point to binary files
- maybe use a default Solr schema; consider exposing to public and document how to use
- alternatives to XSLT should be considered
- need to keep the idea of distributed hardware ( e.g. separate Solr and Fedora)
- wiring - Adam
- changes will be hard and are hard now
- future proofing may not be as important as buy in from the group
- examples used currently or in the past: struts, Spring, JAX, CDI
- feedback from the community needed for https://wiki.duraspace.org/display/FF/Comparison+-+Wiring
Actions
|
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
1 Comment
Andrew Woods
What was the context/meaning of the following comment in the minutes: "General agreement to leave Fedora 3 documentation sources behind for Fedora 4"?