WIP (Not Ready) Feature/cda 103 adr for handling location kind

[rma-bryson]

Summary

Describe the change.

Related Issue

Closes #

Validation

Describe how this was tested.

Checklist

• AI tools used

[rma-psmorris]

Met with @rma-bryson regarding this ADR. Guidance as follows:

1. Revise the ADR to document the current data structures as they exist today.
2. Identify and describe the proposed new data structures.
3. Document the hierarchy of location kinds.
4. Define the roles of CDA endpoints in handling location kinds, specifically differentiating between:
   • General location endpoint behavior
     • The location endpoint should not inspect kind-specific tables.
     • Determining whether a location is a marker should not be the responsibility of the general location endpoint.
   • Kind-specific endpoint behavior
     • Marker identification can occur at the kind-specific endpoint level.
   • Catalog endpoint behavior
     • Consider adding a capability to fully identify a location's specific kind and determine which kind-specific records exist for that location.
     • Whether a location is a marker can then be derived from this information.
5. Work through representative use cases to illustrate how location kind transitions affect at_physical_location, kind-specific tables, and marker identification. This should include transitions both upward and downward through the location kind hierarchy.
6. Identify risks to external applications and integrations resulting from these changes, along with proposed mitigation strategies and migration guidance.