2019-04-30 Meeting notes- Technical

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/Version control

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.

• Decision: Chin will schedule database dumps that get pushed to the Isilon, or another storage location. These should be scheduled as appropriate. Weekly? Monthly?

• Decision: Do a local postgres dump. This will be backed up by the automatic backups. Schedule this to run monthly.

• Daily snapshots

• Version control: start with original configs, merge in ours, keep that version history

  • Decision: Back up all configs on the S Drive.

Themeing/front end design

Who should be involved? Gabe and Chin? Chris? Rachel Cox? When can this work begin, given their workloads?

• Chin, Gabe and Annie will work on this. Chris can advise.

URLs

Requires SSL Cert… Chin is working on this now.

• Security check for SSL cert necessary to enable the use of repository.temple.edu, and to remove the 8080 from the URLs

• Payment: Cynthia’s working on it. It must be paid by check, meaning that this will take longer.

• Remove the 8080 from the URLs…

  • Ideas from Chad:

    • Apache could be run in front of tomcat

    • Apache could be run in front of the Handle service

Old URL:

http://repository.temple.edu:8080/xmlui/handle/123456789/280

Is this an acceptable new URL:

http://repository.temple.edu/xmlui/

Decisions:

• Get http [apache] service in front of the TomCat. This will route trafic to the site.

• Enable SSL Cert

• Handle: Once we get the server set up, Chin will start the security procedure.

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

• Procedure. Here’s what you need…

  • TUHelp ticket

  • FOAPL

  • Gabe will make sure that the ETD chunk to be migrated from CDM will fit

Timeline

• How long will the procurement process take?

Contingency planning

• Who will be responsible for keeping the system up and running?

  • Ongoing conversation

• If it goes down, who will bring it back up and on what timetable?

  • Chin will be point person

  • Bottom tier of support… only during business hours.

  • Document procedures for bringing it back online.

  • Chin U. Kim will document the procedure for bringing the system back up

Related dev requests?

• Holly and Margery- they want redirects from CDM to DSpace (hosted) before the ETDs are deleted from CDM

  • We can’t do this because it’s on OCLC’s server

  • Gabe Galson will make sure that OCLC doesn’t offer anything like this

• SWORD crosswalk from ProQuest

  • This will probably not be necessary. Decision… not needed for soft launch

  • 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.