Time/Place

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

Attendees

Agenda

  1. LibDevConX
    1. Who is attending
    2. Topic proposal
    3. Desired outcomes
  2. Review of approaching beta (feature set and mapping to use cases)
  3. Potential pilot projects
  4. Current dev status
  5. Followup on role assignment

Minutes

  • LibDevConX
    • Attendees
    • Topics
      • Broad focus on open source and libraries, archives and museums
      • Show-and-tell sessions and breakout coding sessions
      • Planning for Hydra/Fedora connector, maybe coding too
      • Brief status update
      • Andrew: How does IIIF protocol interact with Fedora?
      • Martin: Hydra RDF work be expanded to be it own module, could use engagement from other communities for broader impact
      • Eric: Content modeling, and how that changes with Fedora 3 to Fedora 4 migration
  • Beta release
    • Based on the use cases, we are getting close to beta release
    • Biggest gap is authorization work, which will be the focus of the next sprint and Asheville hackfest.
    • Are there any gaps?
      • Esme: Ingest tool to load data from disk, adding files as content nodes and parsing metadata from files
      • Greg: RDF-based ingest tool (with links to content files)
      • Martin: Content-based ingest examples, something more sophisticated than curl, but more achievable than a full-blown ingest tool.
      • Martin/Esme/Andrew: We should revisit disseminators, not for the beta, but going forward.  Some disseminator usage can be replaced by sequencers or other tools sitting on top of the repository.  But there may be some functionality that needs an additional way to plug custom modules into the repository.
  • Access role assignment
    • Stefano: It seems like roles can only be assigned at the individual user level
    • Andrew: There is some existing group authorization (based on group authorization headers passed in), and there is also the framework in place for adding additional functionality.
    • A custom Principal Provider is a simple interface to implement, and provides user/group information that ties in to the existing authorization functionality.
    • Need to do some comprehensive design of authorization pattern to guide development.

 

Actions

  • Esme will propose a Fedora 4 status update/Hydra connector topic for LibDevConX
  • Andrew: Add ingest tool to the 2014-05-12 Asheville agenda