ACMAD changes

[isedwards]

• The changes in this pull request were made to an early fork of Climsoft 4.0 from May 2017 (e61f860)
• The Climsoft project was very different in mid-2017 with the majority of contributions being made by only two lead developers
• Most of the changes are fairly independent of the main Climsoft code and therefore could be rebased onto a later version
• Instead of using the global connection to the database (that is opened during login) each of the new modules connected as required when they are opened using settings in My.Settings.defaultDatabase
• Modifications have also been made to the Climsoft database, these will be analysed and added to a pull request in the climsoft-database repository (this issues will be upadated with a link when the pull request is available)

Overall, the main difficulty with progressing this work is understanding how everything is intended to work. It requires us to take ownership and to make a commitment to adopting the capabilities and maintaining them going forward.

[isedwards]

Login is unchanged except or customisation of the logo:

Main menu has new modules:

---

Each of the new modules is shown below

---

Carnet d'observation:

---

Tableau Climatologique mensuel:

---

Inventiare de microfiche:

---

Donnees hydrologiques:

---

Consultation:

---

Sondage:

[Steve-Palmer]

The problem here is understanding what the requirements are. One set is for the fiche archive held by ACMAD - where the problem is converting to digital images from a huge number of photographic images on the old fiche. The image contrast was poor to start with, and they are deteriorating slowly with age. They contain data up to the mid-1990s, with nothing since.
The other problem is imaging from paper archives containing data from the 1990s (after the fiche) to present. Here one of the principles is to set up systems which can be operated by the NMHSs. Hence there may be ideas about the balance between local and cloud-based processing and storage, as well as making systems robust for use by non-technical staff or contractors. There would also be a training package.
First step is to get some documents describing the potential processes, perhaps as User Stories.