Pool: IsManagedBy Relation Validity Periods That Lie In the Past Should Not Be Changeable #1555
Description
As an operator I want the golden record process to ensure that the past validity of IsManagedBy relations is not not changeable. This means, the golden record process should reject new IsManagedBy relations that have validity periods that span into the past. Likewise, the golden record process should reject updates to existinf IsManagedBy relations whose validity periods contradict existing past validity periods. Basically, the past of IsManagedBy relations should be unchangeable.
Technical Considerations
In the golden record process the Pool is the last instance to ensure data consistency and validation of new golden record information. Here, we want to include no validations to the IsManagedBy relation.
Whether something lies in the past is determined by the JAVA system setting of the Pool.
So the current time is taken into account from the Instant.now() method.
The current data is not considered a past date.
When upserting a IsManagedBy relation the Pool should execute additional validations:
If the relation does not exist yet: Reject it if there exists any validity period with a valid from date in the past.
If the relation already exists:
For the existing relations' validity periods and the new validity periods compare the sets of all validFrom and validTo dates that lie in the past. Reject the relation if the two sets are not equal.