2012-07-02 DfR Technical Meeting

Regular Attendees

• Andrew
• Bill
• Chris
• Dan
• Jonathan
• Danny

General

• Call In To: Free Conference Call HD - DuraCloud Line
• - Indicates who will be taking minutes

Discussion Topic

DfR 0.2 Jira

Actions from last meeting

Status

• Jonathan
• Andrew
  • In Progress: Shib over DuraCloud MC (jira)
• Bill
  • Completed DFR-90, UpSync deployment investigation. Notes available here.
• Chris
• Dan
  • Worked with DGI to creating a functional SIDora
  • Created an AMI from it (one bug remains - some Tabbed forms don't render properly)
  • Work on objects examples for ingest
  • Bring up OCS code (note: it does not have an execution environment outside of test)
• Danny

Minutes

Sidora

• Good response from TJ; junior person did initial setup
• Sidora:
  • There's a set of object models; leaf node and collection node concepts map one-to-one to Fedora
  • Object models loaded through Fedora; solution pak is set of object models, set of Drupal modules (e.g., collection and item-like things), can have multiple solution paks loaded
  • Drupal provides the view plus other functionality, includes internal database providing info for presenting views;
  • Solution paks are specializations loaded on top of Drupal and on top of Fedora
  • Dan: Some additional things should be stored in Fedora.
  • Use Drupal product called Skinner that manages skins
  • Driven by a set of XML forms; there is a form builder or you can load pre-built form from XML file; series of XSL transforms--used in many cases to put data into Dublin Core; set of associations map form, transform, and object model.
  • DC, MODS records; metadata is mostly mapped to inline XML datastreams; you can upload a data datastream to Islandora; When you upload a file to Islandora it becomes managed data in Fedora; 
  • You can add new content models on top of data already there
  • We don't yet have good documentation off Sidora content models; need to view the XML to make sense of them
  • Manual process to configure Sidora; part is SSHed into a server, part through the administrative interface
  • Currently:  The AMI is created, the instance automatically starts Fedora; has  Sidora modules in it, has some data in it. Not sure we have a file/directory object model
  • There's a bug affecting the rendering of some tabs
  • We should be able to load item and view it, add metadata and view it, at the end of this iteration
  • We are done for this iteration

Sync Tool

• What browse and select capability should we deploy?  Danny will investigate

Shib Implementation

• Work happening on Management Console side
• Spring config setup for basic auth; at Apache level it bumps you over to Ship IDP, does auth against LDAP, bounces you back to MC

Action Items

See above for now.