March 2012 Agenda and Notes

Logistics

Dates: March 28 - 30, 2012

Attendees

Timeframe

Note: LibDevConX^3 is March 26 - 28. We will adjust Hydra Partners schedule to accommodate--likely formally starting Weds PM, and also exploring opportunities for overlapping agenda items.

Wednesday: 9 AM arrival - overlap with LDCX
Thursday: 9:00 AM - 5 PM
Friday: 9:00 AM - 5 PM

Agenda, Schedule & Notes

Thursday

• MOU and CLA update

• Hydra Partner Meeting Functions

• Review Matt's doc on Hierarchy of Promises

  • MAKE WILLY COMFORTABLE CALLING A HYDRA STACK-BASED APP A HYDRA HEAD, EVEN IF IT DOESN'T USE ALL OF THE LATEST CODE AND ALL THE COMPONENTS. (WILLY = FOIL FOR NEW DEVELOPERS)

  • Walk through improving Hydra docs for new users

• What Should Be in the Hydra-Head Gem?

• Rights & Authz

  • APO's/rightsMetadata/adminSets/XACML/FeSL

• DuraSpace / DuraCloud / DfR

  • batch hydra ingest (dfr?)

  • Argo / dfr comparison

  • Hydra and DuraCloud (Bill B.)

  • StorageManager review

  • Hylandora & how it fits into Hydra Framework

• T-shirt

Friday

• Status of the Hydra Design Group (see http://projecthydra.org/community/structure/)

• Pin down June meeting dates to 6-8th June at UVa

• Three-tier mailing lists: making sure you see everything you should!

  • Hydra-users to be used as "hydra-announce"

  • Hydra-partners to be used for sensitive content

  • Hydra-tech for all technical queries

• Hydra Webinars via DuraSpace

• Rotate release managers schedule

• Project Hydra Accounts

• APT

• Atrium & Exhibits & Collections sites

• DRY out wiki and web site

Open Action Items

• MOU & CLA – code licensing & copyright statements

• create Hydra Accounts page

• "What's on the can?" review

• Updating Hydra wiki with latest and more details on object models, cModels, data streams and samples see Hydra Object Models docs for Islandora, e.g.

  • move to wiki...

  • review relative to diagram(s)

• OR12 planning

Open Discussion Items

• RDF instead of MODS as primary metadata schema

• Hydra official content models / AF models

• other pieces of infrastructure development, and how they fit into the Hydra Framework. How have specific institutions arrayed Hydra relative to their local infrastructure?

  • authentication

  • authorization

  • workflow

  • ESB

  • Mike Stroming will bring a set of user stories and wireframes on authn/z

• OR12 planning

• Reuse of heads by others

• Reuse of components w/in heads

  • make sure that local code is accessible in GitHub

• Media Planning: VoV, WGBH, RockHall

• LDCX^3 retrospective