Record and show relationships between requests

[RichardTaylor]

• One request may be a "drill down" as a result of a response to a previous request.
• A request might be a request for an updated version of previously requested information.
• A request might be part of a batch made via Alavetlei [already handled]
• A request might be part of a "batch" not made via the Alavetlei system [could be handled by tagging]

See also: Special annotations - for links to articles based on responses, summaries of correspondence, or admin notes #34 where there is also discussion of this kind of thing. The aim of this feature request could be achieved now by use of the existing annotation feature, but improving annotations might make using annotations more effective.

Similar, but for bodies not requests:

• Record and show relationships between bodies Record and show relationships between bodies #4714

[RichardTaylor]

Another example of a relationship between requests is when one request is for a replacement response, needed because WDTK has removed an original response. (The removal might be due eg. to personal data being inappropriately` released in the original).

[HelenWDTK]

This issue has been automatically closed due to a lack of discussion or resolution for over 12 months.
Should we decide to revisit this issue in the future, it can be reopened.