Page MenuHomePhabricator

[statements-ui] Advanced handling of deleted properties in Claims and References/Qualifiers (Allowing to change Property to an existing one)
Closed, ResolvedPublic

Description

After a Property Entity got deleted, an Item's Claims/Statements might run into some issues. If a Claim has a Main Snak using the deleted property, the whole Claim is not shown anymore.
The Claim should still be shown but display a message that the property is deleted. The UI should allow to change the Claim's property or to delete the Claim.
The same goes for References. Each Snak of the Reference affected will not be shown anymore and in case all Snaks of a Reference are affected, the whole Reference won't be shown. Instead of not showing those Snaks, a message should be displayed and it should be possible to change the property.
Also, for Qualifiers we will run into the same problem.


Version: unspecified
Severity: enhancement

Details

Reference
bz44639

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:32 AM
bzimport set Reference to bz44639.
bzimport added a subscriber: Unknown Object (MLST).
  • Bug 44689 has been marked as a duplicate of this bug. ***

*** Bug 44636 has been marked as a duplicate of this bug. ***

This has not been picked up, this is about advanced handling of the situation such as being able to change the property to a different one. I have set bug 44636 and bug 44689 to assigned instead.

marked this as dependent on bug 44689 and changed the title, so this is just about being able to change a Claims/References/Snaks/Claim Bundles property if it is deleted.

This is not a trivial change and it had to be discussed how this would even look like.

We have a list of Claims, say 10 Claims, but the name of the used Property is only displayed once because all Claims are displayed in a section. Allowing to change the property in the section would change it for all Claims at once. We had to trigger several API calls to do that.

This might be something for later. Just having bug 44689 solved seems appropriate for now.

  • This bug has been marked as a duplicate of bug 55911 ***