(Made-up name, looking for a better one.)
As suggested in this discussion, add constraint type for properties used in references which require another ("sibling") reference.
For example, "archive URL" should be used with "archive date".
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T213803 [Tracking] Request for new constraint types | |||
| Open | Feature | None | T229178 Add "sibling reference" constraint (use of one property in a reference requires another property) |
Event Timeline
Comment Actions
Sounds reasonable to me as well. One could argue that this is a variant of the existing “item requires statement” constraint – see T175562: Check “conflicts with” and “item requires claim” constraints on qualifiers and references?.
Comment Actions
Side note/spoiler: This month I expect to sound out users in the context of the analysis on property constraints, with which we'll know what constraint types users most want, considering this one, the rest of subtasks of T213803, and others.