Collect up tasks for Dave

[agstephens]

1. Review the trigger code (currently commented out):

See: #29

• Fix the trigger code and maybe rename files so they are easy to follow.
• Check it is all working
• Re-work it back into the Ansible playbook
• Replay on to the live server

2. Add cluster (sort) ability to playbook:

See: #34

• Add cluster scripts to the repo
• Test with Ansible
• Run on production
• Document how to run routinely

[david-i-berry]

Hi Ag, I'm struggling with the best way to document the triggers (and the database build scripts in general). Any pointers would be welcomed.

[david-i-berry]

I've updated the readme and re-organised the code / scripts (including renaming to be more obvious). See https://github.com/glamod/glamod_database.

[agstephens]

Hi @DavidBerryNOC, I didn't know you would look at that. Sorry, I am working off here, which is significantly different already:

https://github.com/glamod/glamod_database/tree/refactor/use-default-schema

We are using that branch for our production build.

I suspect we can bring the changes together.

[agstephens]

@DavidBerryNOC coming back to your question about documenting the triggers. I think we just need a description of the required components:

• code X does ...
• code Y does ...
• code Z does ...

It can just be in a README file, so that I can follow it.

[david-i-berry]

I've edited the readme under the original. I think this is what you are after.

I've only had a brief look at the refactored code, I think you should be able to copy the functions and triggers directories from the old to the new without issues (I've changed cdm_v1 to __INSERT_SCHEMA__ throughout. I've also edited the make_database.sql to call the correct files.