...
- Andrew Woods
- Ed Fugikawa
- Jonathan Green
- Nigel Banks
- Osman Din
- Benjamin Armintor
- Scott Prater
- Michael Durbin
- Greg Jansen
...
- Fedora 3.7 Test Plan
- Fedora 4 Current Work (Sprint B3 wrap-up)
- Backup/Restore
- Triplestore packaging
Previous Actions
Minutes
Actions
Minutes
F3 -> F4 Upgrade
- Allows federation over F3
- Not all properties from F3 are mapped into F4
- Issues
- Only a small percentage of repository is exposed in F4
- Will be working on integration tests
- Future: mechanism to copy content over from F3 into F4 BinaryStore
- Mapping F3 relationships into F4 objects
- Interest in mapping RELS-EXT into F4
- Security policies need to be migrated as well
- Need support for content model validation
- Ability to define schemas to which conform datastreams conform
- Is it ready for Verification/Acceptance testing?
- Pending two issues mentioned above
Hierachies
- JCR allows structural hierarchy
- RDF relationships allow hierarchy and graph
- We should be clear about convoluting the two representations of hierarchy
Follow-on activities
- Creating new tickets to make UI intelligible
- Developers often do not look at the UI
- Create a wiki page to describe/navigate the UI
- Mike: create tickets for UI
AuthN/Z
- FedoraAdmins are able to bypass some AuthZ
- REST endpoint always uses servlet-based credentials
- No anonymous users
- Greg to add documentation about how to wire in policy enforcement points
- Is another extension point needed for a PEP?
- This sprint
- Defining node-types to store roles
- Example PDP/PEP
- Documentation for wiring
Actions
- Michael Durbin to create Pivotal tickets for UI polish
...