What was the goal of Sprint 16?
For Sprint 16, the following goals were set:
- Finalize short-term workflow for ingesting data into UCSB and UCSD Geodata
- Determine the look and feel of UCSB Geodata
- Add rights metadata field to Geodata interface
- Determine stakeholder priorities for next development cycle
- Add QA/QC processes into the ingest workflow
- Determine short-term object storage options
- Determine which Shoreline tickets could potentially be part of Comet
What is the milestone that this sprint is supporting?
To determine how potential feature development should be prioritized during the next work cycle based on input from stakeholders; to gather information about potential ingest methods as we refine our ingest process; to provide a high-level description of Shoreline; and to prepare for a first round of data ingest into each campus’ instance of Geodata.
Accomplishments of Sprint 16:
During the sprint we accomplished the following:
- Short-term workflow for ingesting data into UCSB and UCSD Geodata have been finalized
- Set up appropriate meetings to discuss the look and feel of both UCSB and UCSD Geodata sites in the broader context of each campus’ digital library guidelines
- Participating in GeoBlacklight community sprint, which has made updating rights metadata fields in GeoBlacklight a priority
- Reviewed stakeholder input and determined (but not ranked) priorities for next development cycle
- Added QA/QC processes into the ingest workflow
- Determined that a short-term storage solution for distributing the original objects is not necessary through GeoBlacklight
Did we do everything we set out to accomplish?
Yes, except for the following:
- We were unable to determine which Shoreline tickets could potentially be part of Comet because the Comet White Paper that defines its scope has not been finished.