May 27, 2022

- Objective of the meeting is to get team members up to speed on ICE-D - how it works, how data is added to the database, etc.

- Greg began by laying out the structure of the database

- separating and recording the observations that are permanent (i.e., the lat lon elevation, 10Be conentration, etc.) in an easily accessible archive and then as new methods for calculating ages are updated, users don't need to keep publishing and handling spreadsheets of pre-existing data.

- further, the database needed a sort of back end infrastructure that stores the data live and can be updated and populated by multiple users. Data should also be readily available to be delivered dynamically when asked.

- the database is run through MySQL and is stored on a google virtual server that the grant pays for for a monthly fee.

- Briefly, the cost to connect multiple computers to the virtual server in google scales, and so along with security reasons it is easier to have users connect to a separate virtual server (stoneage) that has access to the server storing ICE-D.

- The connection to stoneage is set up through SSH tunnels. Specifically, we connect user's personal machines using key pairs, one that is public and one that users generate and store and privately on their own machines (see tutorials for more details on how to make those).

- Greg showed the tables plus MySQL connection page to demonstrate how users connect through stoneage to ICE-D using the SSH tunnel and how each user will be set up as a 'reader' (i.e., users will have read only privileges and won't be able to edit the database directly from their SQL clients).

- Now that everyone is connected to ICE-D as a reader, Greg is showing people what the data actually looks like in ICE-D.