Samvera Community Wiki
Committers Call 2014-07-28
Moderator: Rick Johnson (ND)
Notetaker: Thomas Scherz (UC)
Attendees:
Michael Klein (Northwestern)
Linda Newman (UC)
James Van Mil (UC)
Glen Horton (UC)
Esme Coles (SDSU)
Sue Richeson (UVA)
Rick Johnson (ND)
Adam Wead (PSU)
David Chandek-Stark (Duke)
Jim Coble (Duke)
Lakeshia Robinson (Yale)
Chris Colvard (Indiana)
Justin Coyne (DCE)
Jeremy Friesen (ND)
Dan Brubaker-Horst (ND)
Mike Giarlo (PSU)
Agenda:
Hydramata::Works (http://ndlib.github.io/hydramata-works/)
Design and Development Goals - http://ndlib.github.io/hydramata-works/demos/design-and-development-goals/
Work Type and Predicate Definition - http://ndlib.github.io/hydramata-works/demos/work-type-and-predicate-definition/
View Lookup for Work Type, Predicate Set, and Predicate - http://ndlib.github.io/hydramata-works/demos/view-lookup-for-work-type-predicate-set-and-predicate/
Translation Services for All the Things - http://ndlib.github.io/hydramata-works/demos/translation-services-for-all-the-things/
Interacting with Fedora - http://ndlib.github.io/hydramata-works/demos/interacting-with-fedora/
Explaining the Suggested Structure http://ndlib.github.io/hydramata-works/demos/explaining-the-suggested-structure/
Dan: Why are we working on Hydramata? What are the goals?
Notre Dame has encountered problems/challenges over the course of the year:
Justin: CModels: Multiple inheritance or single table inheritance in Rails. Good and Bad.
Jeremy: What do we do about the inter-relational nature of the gems? Pain-points and challenges.
Dan: The problem space we are working in and the design proposals for dealing with said problems is important.
Dan: There needs to be a common awareness among developers in the hydra community.
Justin: Metadata templates; How does this get changed?
Rick: It was important to communicate to the committers about these pain points and solutions being developed to deal with these pain points Ideally we want to have something more concrete to work with at HydraConnect.
Justin: Another pain point is determining when to call from index or when to call from repository?
Esme: More explicit.
David: Duplication going on.
Jeremy: Is SOLR only our searching index or is there more information in there?
Adam: Spotlight uses SOLR persisted in SOLR but not in Fedora.
Jeremy: Provide a service that will check the index, the class, and then finally the database.
Justin: Breaking down into components makes for a complex class tree.
Jeremy: ActiveFedora cleaves very close to ActiveRecord. Perhaps there is another way to expose useful pieces and here is how you would re-use it as a plain old ruby object.
Justin: Simple inheritance has worked well and questions whether a new approach will work better.
Adam: Is there a concrete implementation of what we are trying to achieve?
Jeremy: Rack Middleware. Is a good example of modeling request / response cycle. Plug-in architecture. I.E. NAUGHT gem. Lotus/Model: Repository patterns.
Next Call:
2014-08-04
Moderator: Adam Wead (PSU)
Notetaker: Jeremy Friesen (ND)