Date
Attendees:
Meeting Goals:
- Define scope of DSpace project
- Sketch out Timeline
- Address Annie's notes covering stakeholder expectations
Project deliverables:
Short term
- Ingest Faculty Publications
- Ingest ETDs
Longer term
- Migrate ETDs from CONTENTdm
- Public access to IR's contents
Questions:
ETDs... if they're to be migrated to DSpace, how will they be accessed?
Long term storage/preservation
Core functionality-
Annie: Public interface/access is important and should be implemented earlier rather than later
David: we should wait for now. The longterm plan is to feed items from the dark dspace instance into Blacklight. Persistence of URLs and URIs is a major concern. Global discoverability (via google) is another.
Another display option: create a blacklight powered discovery interface hosted on a separate website. This would allow us to use blacklight without forcing users to go through the general library search interface. See Columbia's
Annie: Why would users be accessing the data through Blacklight?
on the UI-
David: DSpace has a public UI, but it would take time we don't have.
Who will handle the curation internally? Who will populate the dspace via elements? Who will handle the long-term work.
Info: the current installation is the dev environment, and will be replaced.
Double ETD workflow: They'll be added to CDM and DSpace simultaneously, until CDM can be turned off.
Adjusted timeline: Bridging Elements-DSpace could extend into the fall. DSpace with UI summer '19? (Unclear; david says that with that much time we should ). Cynthia: conservatively, this can be done by next March the secondary and tertiary blacklight based pages w/ unified look will be ready.
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|