Incorrect Incident Detection for Uniqueness Constraints: Missing or False-Positive Incidents

🐛 Bug Report

Summary

The uniqueness constraint mechanism does not function as intended. It is not possible to enforce validations such as "For Term each Language is unique" or "For TitleWrap each Appellation Value is unique". As a result, essential quality checks cannot be conducted.

Steps to Reproduce

Define a uniqueness constraint on a Term element with language differentiation.

Define another uniqueness constraint for Appellation Value inside a TitleWrap.

Run the constraint check.

Observe that no validation error is triggered in a manipulated xml-file

What is the current bug behavior?

Uniqueness constraints such as "For Term each Language is unique" are not enforced.

Also the quality check "For TitleWrap each Appellation Value is unique" is not working — duplicate values for e.g., original vs. alternative title are allowed.

In the case of "For TitleWrap each Appellation Value is unique", no incident is triggered, even when a duplicate clearly exists.

In the case of "For Term each Language is unique", an incident is always triggered, even when no duplicate is present.

This breaks expected validation behavior and leads to both missed errors and false positives.

What is the expected correct behavior?

It should be possible to enforce uniqueness rules as expressed in the constraints: "For Term each Language is unique" -> Incident if a Term has two identical Language attributes, but no incident if there is only one language attribute "For TitleWrap each Appellation Value is unique" -> Incident if a title is repeated in the same wording as additional title

Duplicate entries violating these rules should be recognized.

Relevant Logs, Screenshots, or Gifs

-> incident expected

Possible Fix or Suggested Solution

Ensure that constraints such as "For Term each Language is unique" are evaluated properly