...
- Interest in sakai auth integrating with fedora
- Action: Osman Din to investigate auth and sakai/fedora
- Interface between consumer and policy driven storage must be defined/designed
- How do we serialize rules
- How are changes detected by kernel
- When are updated storage policy rules recognized by kernel?
- What information is only available once an object is created
- What do real users want to make policy storage based on?
- Should we add headers to specify hints for storage policy decisions?
- Can fedora expose hardware usage info?
- i.e. Space is running low
- We need new tickets, Osman to create/update
Monday 2013-08-05
Greg
- Working on mock with shib header
- Goal: authN, acls in repo, produce roles, role -> pdp, ...
- How to make serializable principals in mode?
Yuqing
- Adding transaction into tuque
- http connection issue in tuque, resolved
- Stomp
- Need object path instead of pid (ticket)
- Will not be ready for community review by end of week
- Yuqing will be on sprint2
Osman
- Added unit tests
- Cleaned up tickets
- Currently storing storage policies as node properties
Jay
- Two current areas of interest
- BagIt
- Async store
- Working on registration of content
- Two connectors
- General cloud connector
- Sequencer to retrieve content