Time/Place

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

Attendees

Agenda

  1. Federation config wrap-up
  2. Federation authz namespaced nodes
  3. Artic asynchronous design question
  4. C4L planning
  5. Content model proposal, session prep
  6. other...

Minutes

  • Federation config
    • Esme and Eric set up a sample configuration for filesystem federation
    • Esme: Initial set up of filesystem federation works as expected - changing the config and reloading breaks things.
    • Looking for ways to change and reload config, added debug statements to trace issue
    • Adam: We should talk to Modeshape; should be their issue
    • Esme: will open a ticket on Modeshape
  • Eric's federation issue: applying auth rules on federated nodes
    • When setting ACL in federated content, an error is thrown.
    • ACLs are persisted as children nodes of resources and resource names are namespaced. This is problematic with the current filesystem connector.
    • Andrew: if we are not able to resolve this in current sprint, we should lay out in the wiki what the issue is and possible approaches to tackle the issue in subsequent sprints.
  • AIC async derivative generation
    • Currently CMS generates derivatives.
    • With Fedora 4, derivatives will be created by sequencers, thus asynchronously
    • How do we monitor derivatives being generated?
      • Async API: it's planned further down the road, so it's not an option for now
      • External messaging system: better solution, client should rely on messages sent directly from sequencers.
    • How do we know which derivatives are expected once master file is ingested?
      • We don't want to hard-code list of expected derivatives in client for each resource type
      • We can use SPARQL query to find derivatives
      • Andrew: a suggestion would be pre-populating derivative datastreams with placeholder images
  • C4L
    • Esme is presenting - what would be good for Fedora to get out?
    • Esme: will send presentation to mailing list and ask for feedback
    • Presenting new features; basic timeline; call for contributors to the code
    • There might be a Breakout session
    • Planning for Hydra updates to work with F4
    • Andrew: will discuss list of features planned for 4.0 - consistency in messaging is important
    • Ben: 3.7.2 current stand and roadmap will be presented as well 

Actions

2 Comments

  1. Hi - I see that the 3.7.2 roadmap was to be covered at C4L last week - can this be shared here on the wiki and/or the Fedora-Community list?  Thanks!

    1. Benjamin Armintor, I know you have had your hands full across a variety of projects, but do you have any 3.7.2 comments?