Scholar@UC UCrate Merge Plan

1. Identify the features and branding in Scholar that are not currently in the UCrate code. The developers will participate in sprints to port those elements over to UCrate. At that point UCrate will essentially be Scholar running on an updated Hyrax version 2.1. Some product owner input may be needed during this process.

2. Release the new code as Scholar 4.0 and deploy it to our existing server environments. A minor data migration may be necessary.

3. More development sprints to implement UCrate-specific features and changes into the Scholar code. This process will be finished when we have a single application that serves the needs for both a self-submission institutional repository and a repository for library-owned content.

4. Finalize a migration strategy for moving DRC content into the new application. Put both the DRC and Scholar into read-only mode.

5. Develop a replacement handle server.

6. Deploy final code to servers and perform the content migration. Direct DRC handles to new destinations. Take the new repository out of read-only mode.

7. Sunset the DRC.

8. Party!

9. Begin plans for moving additional library content into the repository. Additional software development will likely be needed.

Timeline

Steps 1 and 2 will likely take a couple of months. During that time developer focus will be on porting Scholar features , but UCrate product owners can still use that time to make decisions on their needs and migration plans. Step 3 will probably take another 2-3 months.

Hopefully in September/October we will be ready to focus our attention on data migration. We'll be on target if we can finish the migration and shut down the DRC by mid-December.