Change Details

User story: When i create a statement, i want to know if that same statement already exists - without scrolling and reading a lot especially on mobile - so that i don't waste my time creating a duplicate **Concept one - acting already on the property level:** - When the user selects an already existing property, a warning message is deployed that also allows him to jump to the instance in edit mode: {F80076734} - He can still select another property, and if it is not being used yet, publish it. **Concept two - acting on value level (the user will be adding a value to the already existing statement instead of being re-directed)** - when the user selects an already existing property, we allow him to select a value, but make values already in use for this property visible: {F80078011} Explanation: Despite the fact that the user is trying to add a statement that already exists, we still allow him to use the "add statement" screen to add a new value. This, combined with the floating add button, would enable users to more easily add statements and add values to statements, instead of blocking or redirecting them.

User story: When i create a statement, i want to know if that same statement already exists - without scrolling and reading a lot especially on mobile - so that i don't waste my time creating a duplicate **Concept one - acting already on the property level:** - When the user selects an already existing property, a warning message is deployed that also allows him to jump to the instance in edit mode: {F80076734} - He can still select another property, and if it is not being used yet, publish it. **Concept two - acting on value level (the user will be adding a value to the already existing statement instead of being re-directed)** - when the user selects an already existing property, we allow him to select a value, but make values already in use for this property visible: {F80078011} Explanation: Despite the fact that the user is trying to add a statement that already exists, we still allow him to use the "add statement" screen to add a new value. This, combined with the floating add button, would enable users to more easily add statements and add values to statements, instead of blocking or redirecting them. Both concepts, especially together with the floating button, will make the users live easier and diminish duplicate statements.

User story: When i create a statement, i want to know if that same statement already exists - without scrolling and reading a lot especially on mobile - so that i don't waste my time creating a duplicate **Concept one - acting already on the property level:** - When the user selects an already existing property, a warning message is deployed that also allows him to jump to the instance in edit mode: {F80076734} - He can still select another property, and if it is not being used yet, publish it. **Concept two - acting on value level (the user will be adding a value to the already existing statement instead of being re-directed)** - when the user selects an already existing property, we allow him to select a value, but make values already in use for this property visible: {F80078011} Explanation: Despite the fact that the user is trying to add a statement that already exists, we still allow him to use the "add statement" screen to add a new value. This, combined with the floating add button, would enable users to more easily add statements and add values to statements, instead of blocking or redirecting them. Both concepts, especially together with the floating button, will make the users live easier and diminish duplicate statements.