Skip to end of metadata
Go to start of metadata
Table of Contents

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

  • 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:

Attendees

Agenda

Minutes

F3 -> F4 Upgrade

  1. Allows federation over F3
  2. Not all properties from F3 are mapped into F4
  3. 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
  4. Mapping F3 relationships into F4 objects
    • Interest in mapping RELS-EXT into F4
    • Security policies need to be migrated as well
  5. Need support for content model validation
    • Ability to define schemas to which conform datastreams conform
  6. 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
  1. Creating new tickets to make UI intelligible
    • Developers often do not look at the UI
  2. Create a wiki page to describe/navigate the UI
  3. Mike: create tickets for UI

AuthN/Z

  1. FedoraAdmins are able to bypass some AuthZ
  2. REST endpoint always uses servlet-based credentials
    • No anonymous users
  3. Greg to add documentation about how to wire in policy enforcement points
  4. Is another extension point needed for a PEP?
  5. This sprint
    • Defining node-types to store roles
    • Example PDP/PEP
    • Documentation for wiring

Actions

  • No labels