Road test the new single-instance Hyrax.
Develop training materials.
Complete as thorough a set of tests as we can.
Correct any problems that can be fixed.
Report results back to Implementation Team.
| Driver | Approver | Contributors | Stakeholder |
|---|---|---|---|
Kevin Cloud (Unlicensed) | Sacramento Dominguez Hills Fullerton |
| Objective | Road test the new single-instance Hyrax. |
| Due date | |
| Key outcomes | Develop training materials. |
| Status |
We need to run a pilot to ensure that the new single-instance Hyrax is working as expected. We think the following three campuses are good participants for a pilot:
Sacramento has a typical, medium-sized repository in ScholarWorks, and has a number of new collections they’d like to upload. We think they will be a good representative of current CSU DSpace users. Dominguez Hills and Fullerton do not currently use DSpace, and so can start using the new system without consideration for historical data or current workflows. This will allow them to get up and running faster than most campuses. Having three campuses will let us test the multi-campus configuration of the new system.
Must have:
Nice to have:
Not in scope:
The pilot should not include new feature requests or UI changes. Rather, such requests should be taken up more formally within the Implementation Team.
Plot out milestones and deadlines using the table below. Put each milestone on its own row, @mention milestone owners, and type /date to quickly add deadlines.
| Milestone | Owner | Deadline | Status |
|---|---|---|---|
| Establish new issue tracking system | David Walker | ||
| Kick off meeting | David Walker | ||
| Initial orientation for campuses | Kevin Cloud (Unlicensed) | ||
| Develop second-pass testing plan | David Walker | ||
| Follow-up training meeting to go over questions and documentation | Kevin Cloud (Unlicensed) | ||
| Complete initial documentation | David Walker | ||
| Final report back to Implementation Team | David Walker |