From 082570572d95e759a324cca0615e53cbc8e208df Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Sat, 1 Nov 2025 21:51:02 +0000 Subject: [PATCH] Add warnings regarding strange ARRIVALS rows These could be hard rules, enforced with triggers. But that would require data cleanup before conversion. It would be good to add hard rules for all data that is entered into the system after a certain date. Then, the date could gradually be pushed back as older data is cleaned up. Unfortunately, this is not in the budget. --- doc/src/tables/arrivals.m4 | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/doc/src/tables/arrivals.m4 b/doc/src/tables/arrivals.m4 index 2b2b5ed..bfc915d 100644 --- a/doc/src/tables/arrivals.m4 +++ b/doc/src/tables/arrivals.m4 @@ -35,8 +35,23 @@ The related |EVENTS| row must be an arrival event; it must have an This related |EVENTS| row supplies arrival and departure time values, and the |ROLES| role related to the event supplies information on the individual arriving and departing. -For further information see the documentation of the :ref:`EVENTS -` table. + +The system will generate a warning when there are 2 different arrival +events for the same arriving individual, in the same follow, with the +same |EVENTS|.\ |EVENTS.Start| time. + +The system will generate a warning when there are 2 different arrival +events for the same arriving individual, in the same follow, with the +same |EVENTS|.\ |EVENTS.Stop| time. + +The system will generate a warning when there are 2 different arrival +events for the same arriving individual, in the same follow, with +|EVENTS|.\ |EVENTS.Start| to |EVENTS|.\ |EVENTS.Stop| intervals that +overlap, endpoints included. + +For further information, including additional data integrity rules, +see the documentation of the :ref:`EVENTS ` +table. .. _ARRIVALS.ArID: -- 2.34.1