Change Details

As a wikidata editor I want to edit strings which trigger a dropdown on my mobile device So that I can more easily update items Acceptance Criteria - Activating the edit button opens the edit statements screen for datatypes Tabular data (string) , Geographic shape (string) - The edit button for these two statements are updated to codex's active state (blue) - The datatypes are read only (existing properties are displayed (but cannot be edited, i.e. the publish button remains inactive)) - References and qualifiers are updated to include this datatype as well - Ranking functions but cannot be saved - header/foot of edit page and updates to display the new datatypes - layout of the page matches the figma files linked below Question: Is it more or less complicated to separate adding the editing functionality of these datatypes when they're a statement vs as a qualifer/reference? Tabular data (string) {F65992113} [[ https://www.figma.com/design/RtMDwH7sMF5IPRJvyyZPv4/Mobile-editing-experience?node-id=2358-29303&t=C9HTDU2XkF8Mdz6A-1 | Figma here ]] Geographic shape (string) {F65992115} [[ https://www.figma.com/design/RtMDwH7sMF5IPRJvyyZPv4/Mobile-editing-experience?node-id=2358-30552&t=C9HTDU2XkF8Mdz6A-1 | Figma here ]]

As a wikidata editor I want to edit strings which trigger a dropdown on my mobile device So that I can more easily update items Acceptance Criteria - Activating the edit button opens the edit statements screen for datatypes Tabular data (string) , Geographic shape (string) - The edit button for these two statements are updated to codex's active state (blue) - The datatypes are read only (existing properties are displayed (but cannot be edited, i.e. the publish button remains inactive)) - References and qualifiers are updated to include this datatype as well - Ranking functions but cannot be saved - header/foot of edit page and updates to display the new datatypes - layout of the page matches the figma files linked below Question: Is it more or less complicated to separate adding the editing functionality of these datatypes when they're a statement vs as a qualifer/reference? - It would be more complicated to separate the two, so when functionality is added it will be done in one task for all locations Tabular data (string) {F65992113} [[ https://www.figma.com/design/RtMDwH7sMF5IPRJvyyZPv4/Mobile-editing-experience?node-id=2358-29303&t=C9HTDU2XkF8Mdz6A-1 | Figma here ]] Geographic shape (string) {F65992115} [[ https://www.figma.com/design/RtMDwH7sMF5IPRJvyyZPv4/Mobile-editing-experience?node-id=2358-30552&t=C9HTDU2XkF8Mdz6A-1 | Figma here ]]

As a wikidata editor I want to edit strings which trigger a dropdown on my mobile device So that I can more easily update items Acceptance Criteria - Activating the edit button opens the edit statements screen for datatypes Tabular data (string) , Geographic shape (string) - The edit button for these two statements are updated to codex's active state (blue) - The datatypes are read only (existing properties are displayed (but cannot be edited, i.e. the publish button remains inactive)) - References and qualifiers are updated to include this datatype as well - Ranking functions but cannot be saved - header/foot of edit page and updates to display the new datatypes - layout of the page matches the figma files linked below Question: Is it more or less complicated to separate adding the editing functionality of these datatypes when they're a statement vs as a qualifer/reference? - It would be more complicated to separate the two, so when functionality is added it will be done in one task for all locations Tabular data (string) {F65992113} [[ https://www.figma.com/design/RtMDwH7sMF5IPRJvyyZPv4/Mobile-editing-experience?node-id=2358-29303&t=C9HTDU2XkF8Mdz6A-1 | Figma here ]] Geographic shape (string) {F65992115} [[ https://www.figma.com/design/RtMDwH7sMF5IPRJvyyZPv4/Mobile-editing-experience?node-id=2358-30552&t=C9HTDU2XkF8Mdz6A-1 | Figma here ]]