Page MenuHomePhabricator

[Task] Composite Constraints
Closed, InvalidPublic

Description

Composite constraints (like "Person" or "Taxon Name") could be lost during migration from templates to statements on properties. One possible solution could be to let the user enter "Person" as value of the Constraint-Statement and in the background the four constraint statements get created via an API call.

Event Timeline

Jonas.keutel raised the priority of this task from to Low.
Jonas.keutel updated the task description. (Show Details)
Jonaskeutel lowered the priority of this task from Low to Lowest.Jun 22 2015, 11:28 AM
Lydia_Pintscher renamed this task from Composite Constraints to [Task] Composite Constraints.Aug 17 2015, 4:14 PM

Is this task still relevant? The migration to constraint statements was done a few weeks ago, but I have no idea what composite constraints are/were.

Is this task still relevant? The migration to constraint statements was done a few weeks ago, but I have no idea what composite constraints are/were.

Complex constraints, I believe, are SPARQL or SQL queries.

And composite constraints are the same thing as complex constraints?

And composite constraints are the same thing as complex constraints?

As far as I know there were 2 type of constraints on the talk pages: the regular constraints, which now are converted to statements and the complex constraints, which never were linked to Quality Constraints and the reports are maintained by PLBot. Other constraints I've never spotted on talk pages. If @Jonas.keutel isn't talking about complex constraints, I suggest he adds links to property talk pages that have composite constraints.

Closing, since there’s no one around anymore who knows what this task means. If it’s a real problem, someone can open a new task.

I see, thank you… but that template was subst only before this issue was even opened, so if I understand correctly there’d be no difference between composite constraints and regular ones except when you added them.