Time/Place

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

Attendees

Agenda

  1. Art Institute of Chicago OR2014 demo?
  2. XACML design review 
    1. XACML attributes
    2. XACML authorization delegate
  3. LDCX report
    1. Hydra connector progress (Sufia, Active Fedora 8, Fedora Lens, LDP)
    2. New developer interest
    3. IIIF
    4. ResourceSync

Minutes

Open Repository coming up in June

AIC has started implementing Fedora4. There is a chance that they will present their plans and reports remotely.

XACML attributes

  • Greg & Eric are working on XACML
  • Interface is ready to implement
  • Policies are retrieved from repo: auth request -> modeshape delegate -> XACML request
  • Policy objects can be anywhere
  • Policies can be grouped in policy sets, retrieved by UID
  • Hydra IDs/metadata can be translated into roles via sequencers
  • SPARQL/RDF is best way to store and retrieve
    • Attributes are find by querying by predicate - likely no extra configuration is needed
    • Attributes are collected to make pieces of auth logic, e.g. embargo date attribute can be used to validate access before/after a certain time/date
  • Andrew: Auth rules are not honored in triplestore or Solr index. We need to support that. 
    • Greg: There is some design
    • Esme: As far as you index in Solr correctly you can configure Solr to do that by mapping roles to Solr entities
  • Andrew: is the XACML engine external and is it deployed as separate process?
    • Greg: it will be internal at first, externalizing it needs lot of plumbing
    • Andrew: another concern is performance, but if it's not bad it's better to keep the XACML engine external in order to keep the Fedora core codebase clean
    • Greg: maybe as a second pass
    • Initial draft implementation will be in next sprint


LDCX report

  • un-conference and forum for technologies for library archives focused on Hydra, Blacklight, Fedora, IIIF
  • Andrew and Esme were present
  • Hydra
    • Strong Hydra community
    • Was pointed out that the F4/Hydra connector needs more resources and more focus
    • 25 developers participated to hackfest
    • Good engagement, some new faces
    • Sufia, ActiveFedora 8, Fedora Lens are the main Hydra stack elements
    • Focus on mapping RDF to addressable properties
    • Focused on having a demo which can be a model for other developers to build upon
  • IIIF
    • Might possibly integrate with Fedora
    • K. Clarke has done some work in that direction
    • Integration point would be hat IIIF server accesses Fedora server to get images
    • Kevin: Sequencers can be involved
    • NWU heavily relies on disseminators for images, could be a good use case
    • AIC also uses pyramidal images with IIP, want to automate PTIFF generation and retrieval through Fedora
  • ResourceSync
    • 21st CEntury's OAI/PMH for sharing metadata across repositories
    • Based on Google Sitemaps
    • We already have sitemap feature in F4 but Fedora might not use the same machinery
    • There could be an implementation of rsync for F4

Actions