From 233fb806f67a1f6699e56efbbf4c6a1e5af7c083 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Thu, 2 Jul 2026 21:34:11 +0000 Subject: [PATCH] Add warnings for inapproprate use of the sdb_follow WATCHES.Type value It is possible to first insert, e.g., a pantgrunt and create the follow, and then insert other follow related information. But it seems more likely that a follow that has, e.g., only pantgrunts related to it should instead be a pantgrunt WATCHES.Type. --- doc/src/tables/watches.m4 | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/src/tables/watches.m4 b/doc/src/tables/watches.m4 index 842bccd..403c5b9 100644 --- a/doc/src/tables/watches.m4 +++ b/doc/src/tables/watches.m4 @@ -323,6 +323,17 @@ are followed there cannot be a row on WATCHES for that individual for that day with a |WATCHES.Type| of ``sdb_pantgrunt``, and vice-versa. +The intention is that follows, WATCHES rows where the |WATCHES.Type| = +``sdb_follow``, be used where data on a focal is recorded. +The system will generate a warning when there is a follow for which +there are only B-Record related events. +The system will generate a warning when there is a follow for which +there are only location related events. +The system will generate a warning when there is a follow for which +there are only mating related events. +The system will generate a warning when there is a follow for which +there are only pantgrunt related events. + The |WATCHES.Date| must be during a period when the watched individual was under study. This means that |WATCHES.Date| must be on or after the watched -- 2.34.1