- Why do we collaborate in the University of California (UC) Libraries?
- Why do we build shared services in the UC Libraries?
- What does collaboration look like within the UC Libraries currently?
- What could collaboration look like within the UC Libraries?
- What could shared services development look like within the UC Libraries?
- What are the differences between collaboration, co-development and shared services development? When do we apply each approach?
- What does structures need to be in place (in the UC Library Advisory Structure, in campus Libraries, etc.) to foster collaboration, co-development or shared services development?
- What would Hydra Fedora development look like in the UC Libraries: collaboraiton, co-development or shared services development?
- What principles of community support collaboration, co-development or shared services development?
- How can managers and administrators help developers and metadata specialists succeed? What do developers and metadata specialist need from managers to succeed?
- What do managers need from their developers and metadata specialists?
- How can managers communicate most effectively with our developers and metadata specialists?
Specific Hydra/Fedora questions surfaced by developers / metadata specialists
What resources, expertise, foundational infrastructure is needed to use this (((define "this"))) Hydra "tool" at your library?
- Portland Common Data Model
- Spotlight and other exhibit platforms
- Blacklight/ geoblacklight
- ingesting metadata
- Alternative repositories (alternative to Fedora)
- Complex subject modeling in RDF
- Linked Data Platform
What are the gaps in current Hydra development where contribution is needed, where managers want to direct resources to?
- Manager/PM Lessons Learned from Blacklight/Hydra/Fedora projects?
- What do we want to do with the ideas that we've surfaced during this meeting?