Find units and inspect current or historical structure

Purpose

Readers obtain a consistent view of units, their ancestry and their placements on earlier dates.

How It Works

Readers can find units through a filtered list or a code-and-name search. A paged tree provides enough parent information to present the structure incrementally. Unit-specific ancestry and descendant reads return complete collections. Readers can also inspect the retained parent periods. A historical request supplies an effective date and, when needed, the moment whose knowledge should be reproduced. This distinguishes a backdated correction from what an earlier report could know. Codes and names still come from the current unit records. Collection reads for unknown references return empty answers, so integrations must distinguish that behavior from reading one missing record. Published database functions let connected applications use the same current structure within their work. Query registration describes how reports can navigate unit ancestry. Registration evidence does not establish that those datasets have been deployed and exercised.

Relationships

• Restructuring supplies the dated periods used in historical reads.
• Access controls govern staff reads and workspace isolation.