...
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- ReadyTalk:
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free:
- http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
- IRC:
- Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #duraspace-ff on irc.freenode.net
Attendees
- Andrew Woods
- A. Soroka
- Ed Fugikawa
- Jonathan GreenUnknown User (escowles@ucsd.edu)
- Nigel Banks
- Osman Din
- Benjamin Armintor
- Scott Prater
- Michael Durbin
- Greg Jansen
Agenda
- Fedora 3.7 Test Plan
- Fedora 4 Current Work
- Triplestore packaging
- Large file federation slowdownsFedora 3 -> 4 Upgrade
Previous Actions
- Scott Prater to add example RI queries to wiki
- Jonathan Green to add example RI queries to wiki
- A. Soroka and Michael Durbin to add example RI queries to wiki
- Greg Jansen to add example RI queries to wiki
- Unknown User (escowles@ucsd.edu) to send email requesting RI query examples, RDF schema examples, etc be added to wiki
- Andrew Woods to investigate F4 RDF responses and if arbitrary properties are included
Minutes
3.7 Release Update
- Scott found a few problems
- Classpath is so long that windows does not have a long enough buffer
- Java6/7 testing
- getDataFromWeb defaults to using 8080
- This issue is still outstanding
- Update again next Thursday
- Note: Scott will be working on f4 opportunistically once 3.7 is out
Fedora 3 -> 4 upgrade
- Considering a few options
- Federating over f3 objects/datastreams
- Federating over f3 HTTP-API - first draft
- Other items to be addressed
- Versioning
- Audit
- Will we need a full list of pids?
- There is a "pagable" interface for paging through the children
- FilesystemConnector does not sanitize paths
AuthN/Z
- Implementing client-facing side of authZ
- Targeting "pre-authenticated" scenario
- Starting with a mock of the pep
- PEP is over the entire set of modeshape operations
- Repo managers can control access with their own PEPs
- Could potentially expose "access control manager" service
- Native to JCR
- Wisc, working on a simple XACML rules engine
- Concerned with speed/performance
- Rules stored outside of f4
- Will likely be choosing an existing XACML engine project
- Example usecase: embargo etd for five years for the history department
- Noting, embargo is a common usecase
- UVa, would like to integrate institutional IdP
- Shibboleth, and PubCookie
- Colorado Alliance, using XACML
- Have user-classes, and different roles across the repo
- Need to ensure that Islandora supports access control design
- There is a need to be able to check the access controls at any point in the repo
- Follow-up meeting
- We will set up a follow-up AuthN/Z meeting
Actions
- Andrew Woods to setup follow-up meeting on topic of AuthN/Z
...