Hydramata Project Director 1-31-14 Meeting

  Attendees:

   Notes

• Institutional Priorities
• There was a lot of discussion surrounding if we should reflect high priority institutional requirements into our lists and the general consensus was yes as that helps PO's hone in on features that are especially critical
• The dates Rick had picked for ND may need more time built in (maybe at least one month in between each, currently they are 2 month blocks and could be better as 3 month blocks)
• OR 14: We agreed that having something impactful to show at OR is priority and we tentatively settled on the following as a good story to tell:
• Speak to a few different research datasets, or collections that show a mixed variety of formats.  For example, having tabular data alongside images that are displayed via a IIIF image viewer in the context of research data
• We identify some collections that could demonstrate well in a flashy way.
• To accomplish the above we focus less on fully implementing a single Hydramata module (e.g. Data, images, ETD), and focus more on implementing line item requirements within each.  For example, I explained that even though I tentatively attached a June date for a DIL focused plugin, what is really necessary by then is a IIIF viewer that integrates with our image serve.  This would mean we do not focus on having DIL fully functioning within the context of Hydramata, but just have some of the features available to allow us to tell the story above.
• For OR 14 we should make sure we have a good web presence with clear documentation, (official hydramata.org website?), maybe a sample install?
• Some of the core requirements like administrative set, administrative unit, group support, and some bulk ingest capability seem high priority for all
• OR Proposals: 
• Robin and Rick divvied up an outline for the Hydramata project overview proposal
• Rick will create first draft of an outline that Rick and Linda will revise together and divide up