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:** [[ https://www.figma.com/proto/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4?node-id=1147-17923&viewport=1000%2C200%2C0.37&t=0v8tm8clogxLaxvF-1&scaling=scale-down&content-scaling=fixed&starting-point-node-id=1147%3A18292&page-id=1147%3A17921 | Figma here ]] [[ https://www.figma.com/proto/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4?node-id=1147-17923&viewport=1000%2C200%2C0.37&t=0v8tm8clogxLaxvF-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=1147%3A18292&page-id=1147%3A17921 | Prototype here ]] - 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: {F80112156} - 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)** [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4?node-id=1134-15725&m=dev | Figma here ]] - 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: {F80112383} - if he selects a value not used yet, he can publish as usual 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 [[ https://www.figma.com/proto/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4---5?page-id=1319%3A23027&node-id=1319-24986&viewport=-822%2C621%2C0.35&t=bArtC6xyZ6CiDKDD-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=1319%3A25093 | Prototype ]] {F88605730} AC [] when the user tries to add a duplicate, a warning message appears. More specifically, when the user selects the property from the dropdown [] below the warning message, there is a button to go directly to edit the chosen already existing property [] if the user tries for a new property, as soon as he enters the property field again, the message and button disappear [] while the message and button are there, he cannot publish [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4---5?node-id=1134-4507&m=dev | Figma design ]]

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:** [[ https://www.figma.com/proto/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4?node-id=1147-17923&viewport=1000%2C200%2C0.37&t=0v8tm8clogxLaxvF-1&scaling=scale-down&content-scaling=fixed&starting-point-node-id=1147%3A18292&page-id=1147%3A17921 | Figma her---5?page-id=1319%3A23027&node-id=1319-24986&viewport=-822%2C621%2C0.35&t=bArtC6xyZ6CiDKDD-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=1319%3A25093 | Prototype ]] [[ https://www.figma.com/proto/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4?node-id=1147-17923&viewport=1000%2C200%2C0.37&t=0v8tm8clogxLaxvF-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=1147%3A18292&page-id=1147%3A17921 | Prototype here ]]{F88605730} - 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: {F80112156}AC - He can still select another property[] when the user tries to add a duplicate, and if it is not being used yet,a warning message appears. 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)** [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4?node-id=1134-15725&m=dev | Figma here ]]More specifically, when the user selects the property from the dropdown [] below the warning message, there is a button to go directly to edit the chosen already existing property - when[] if the user selects an already existingtries for a new property, we allow him to select a valueas soon as he enters the property field again, but make values already in use for this property visible: {F80112383}the message and button disappear - if he selects a value not used yet[] while the message and button are there, he cannot publish as usual 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. [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4---5?node-id=1134-4507&m=dev | Figma design ]]