Page Comparison

...

Participants

Gabe Galson

Goals

Review roadmapthe plan. Potential issues?
How to support the interim system
- What are backups likeBackups
- Recovery plan
- Upgrades

Discussion topics

Item	Notes
Overview of plan	Fall 19- soft launch with locally installed instance, clean up the URLs Theme Spring '20- Migrate to vendor product
Best practices for setting up the temporary repo	What are the best practices? How can we use GitHub to back up our configs without redeploying? Should we do this?
Backups	Backups right now are whatever ITS provides. They don’t back up the database, they take a snapshot of the VM. I’m unsure if they back up the binary assets and their storage location.
Themeing/front end design	Who should be involved? Gabe and Chin? Chris? Rachel Cox? When can this work begin, given their workloads?
URLs	Requires SSL Cert… Chin is working on this now. Old URL: http://repository.temple.edu:8080/xmlui/handle/123456789/280 Is this an acceptable new URL: http://repository.temple.edu/xmlui/
Storage Space	A subset of ETDs from CDM will be placed on the local DSpace instance. How much are we willing to spend on this? Space/cost calculations forthcoming
Timeline	How long will the procurement process take?
Contingency planning	Who will be responsible for keeping the system up and running? If it goes down, who will bring it back up and on what timetable?
Related dev requests?	Holly and Margery- they want redirects from CDM to DSpace (hosted) before the ETDs are deleted from CDM SWORD crosswalk from ProQuest This will probably not be necessary. If we must do this, I will need to at least consult with a Dev. If Annie and Alicia don’t need this for the test version than we can forgo it.