Date
Participants
Gabe GalsonCynthia Schwarz (Unlicensed) David Lacy Chin U. Kim Chad Nelson (Unlicensed) Annie Johnson (Unlicensed) Holly Tomren
Goals
Let’s decide on, or at least discuss, the following:
--A UI approach. Should we...
A) Customize and build out DSpace (see DukeSpace)
B) Skin DSpace with a Blacklight interface that will function as a standalone repository and be populated with items pulled from DSpace via OAI (see Columbia's IR).
C) Leave the DSpace UI as-is, or minimally customize it using a theme
--A timeline. What will we release and when, given staffing and technical constraints? The target date is June, but given our UI approach and staffing available will that be doable?
--A library search strategy. I'm assuming we want IR items indexed in library search but I'd like to confirm. We should consider this when setting a timeline.
--Staffing. Whether we go with A, B or C, integrating IR materials into library search will require developer support. Most of this work will be blacklight-side however. UI-wise, Chin and I alone can execute option C by June, but we'd have to skip many customizations and features requested by Annie/the IR Services group. UI options A and B would take a good deal of additional developer support, while Option C could also benefit from a bit. For example, integrating ORCID into the UI would require developer support, as would many other features.
Discussion topics
Topic | Options | Notes | Decisions |
---|---|---|---|
UI approach | A) Customize and build out DSpace (see DukeSpace) B) Skin DSpace with a Blacklight interface that will function as a standalone repository and be populated with items pulled from DSpace via OAI (see Columbia's IR). C) Leave the DSpace UI as-is, or minimally customize it using a theme | ||
Timeline |
| ||
Library search strategy |
| ||
Staffing |
|