diff --git a/handbook/logbooks.html b/handbook/logbooks.html index 16ee6560f..1ee7d691e 100644 --- a/handbook/logbooks.html +++ b/handbook/logbooks.html @@ -41,7 +41,7 @@ where "Lemon Snout" is. If this is all new to you, please now read Why we make surveys and -Cave data management, +Cave data management, and then the Survey Handbook diff --git a/handbook/datamgt.html b/handbook/survey/datamgt.html similarity index 57% rename from handbook/datamgt.html rename to handbook/survey/datamgt.html index 2f4133f90..ea5330e35 100644 --- a/handbook/datamgt.html +++ b/handbook/survey/datamgt.html @@ -22,33 +22,28 @@ data. Aside from the data collection requirements of the game itself, setting up expedition) of cave exploration often involves collection of personal information ranging from dates available to medical information to the desire to purchase an expedition t-shirt.

- + If an expedition will only happen once, low-tech methods are usually adequate to record information. Any events that need to be recorded can go in a logbook. Survey notes must be turned into finished cave sketches, without undue concern for the future expansion of those sketches. +

Recurring expeditions

However, many caving expeditions are recurring, and managing their data is a more challenging -task. For example, let us discuss annual expeditions. Every year, for each cave explored, a list -of unfinished leads (which will be called "Question Marks" or "QMs" here) must be maintained to -record what has and has not been investigated. Each QM must have a unique id, and information -stored about it must be easily accessible to future explorers of the same area. Similarly, on -the surface, a "prospecting map" showing which entrances have been investigated needs to be -produced and updated at least after every expedition, if not more frequently. +task. For example, let us discuss annual expeditions. + +

+

When we have hundreds of explored shafts, and thousands of potential holes on the plateau, it is absolutely essential that we record holes we have already looked at. -

-These are only the minimum requirements for systematic cave exploration on an annual expedition. -There is no limit to the set of data that would be "nice" to have collected and organized -centrally. An expedition might collect descriptions of every cave and every passage within every -cave. Digital photos of cave entrances could be useful for re-finding those entrances. Scans of -notes and sketches provide good backup references in case a question arises about a finished -survey product, and recording who did which survey work when can greatly assist the workflow, -for example enabling the production of a list of unfinished work for each expedition member. The -expedition might keep an inventory of their equipment or a catalog of their library. Entering -the realm of the frivolous, an expedition might store mugshots and biographies of its members, -or even useful recipes for locally available food. The more of this information the expedition -wishes to keep, the more valuable an effective and user-friendly system of data management.

From "Troggle: diff --git a/handbook/survey/index.htm b/handbook/survey/index.htm index c1441a9b8..595cd78fa 100644 --- a/handbook/survey/index.htm +++ b/handbook/survey/index.htm @@ -33,9 +33,9 @@ detailed topics.