T-Rec 2.2 If the mappings are separated from the associated metadata, Include an additional metadata field containing the PID pointing to the mapping or crosswalk

[linikujp]

We recommend establishing the mapping PID and include the PID in the metadata that describes the individual mapping. Incorporating the PID that directs to the mapping in the associated metadata establishes a transparent connection between the information describing the mapping (or crosswalk) and the mapping (or crosswalk) itself. This practice ensures that users encountering the metadata can easily find the corresponding mapping or crosswalk.

[graybeal]

Note that the topic of data/metadata linkage and PIDs is explicitly addressed also in #65, #66 and #71. Consolidating this content into a single ticket may improve clarity and discussion.

I am not clear whether this ticket is referring to the mapping set PID, or each mapping PID, or both? (The same argument applies to both, but there is already an identifier required for the mapping set, mapping_set_id.)

If you are going to point to the mapping(set) PID from the mapping(set) metadata, you also need to do the opposite: point to the mapping(set) metadata PID from the mapping(set) data. Not being able to find the metadata for a mapping(set) is as bad as not being able to find the mapping from the

This cross-referencing concern suggests to me that the metadata and data should always be together, another way of easily finding the corresponding mapping or crosswalk.