Change Details

As a Wikibase editor, I want to be able to select from both local and remote properties so that I can make statements about my local items using properties from different sources. **User's Task flow (Current State, FedProps v1)** # On a local entity page (e.g. Q1), select +add statement, # Enter property label or Pxx in search # Select a federated property from the results list # Enter a local value # Publish (save) the statement **FedProps v2 Changes** - Users will be able to add statements to local entities using either local or remote properties. They will need to be able to distinguish between local and remote properties when adding new statements. - Entity pages will display statements containing properties from up to 2 sources (1 local, 1 remote). Editors/readers should be able to quickly determine the source of each property used to make a claim about an entity. - Users should still be able to search for both types of properties by either the P-id or property label **Questions to answer:** - Should the user always be shown BOTH local and remote properties in the search results when adding statements? - If yes, how should the properties be displayed? - How will the user know which properties in the results are local and which are remote? - How are the properties sorted in the results? E.g. Local properties first, then remote… or whichever is closest to the search term? - If no, should the user instead select their property source before searching for the properties? **Proposed User’s Task Flow for FedProps v2 :** TBD

As a Wikibase editor, I want to be able to select from both local and remote properties so that I can make statements about my local items using properties from different sources. **User's Task flow (Current State, FedProps v1)** # On a local entity page (e.g. Q1), select +add statement, # Enter property label or Pxx in search # Select a federated property from the results list # Enter a local value # Publish (save) the statement **FedProps v2 Changes** - Users will be able to add statements to local entities using either local or remote properties. They will need to be able to distinguish between local and remote properties when adding new statements. - Entity pages will display statements containing properties from up to 2 sources (1 local, 1 remote). Editors/readers should be able to quickly determine the source of each property used to make a claim about an entity. - Users should still be able to search for both types of properties by either the P-id or property label **UX Guidance** - Should the user always be shown BOTH local and remote properties in the search results when adding statements? - Yes, with local properties somehow privileged in the ranking/sorting [Stage 1] - How will the user know which properties in the results are local and which are remote? - Display an indicator for the remote properties that is consistent across the UI [Stage 2]

As a Wikibase editor, I want to be able to select from both local and remote properties so that I can make statements about my local items using properties from different sources. **User's Task flow (Current State, FedProps v1)** # On a local entity page (e.g. Q1), select +add statement, # Enter property label or Pxx in search # Select a federated property from the results list # Enter a local value # Publish (save) the statement **FedProps v2 Changes** - Users will be able to add statements to local entities using either local or remote properties. They will need to be able to distinguish between local and remote properties when adding new statements. - Entity pages will display statements containing properties from up to 2 sources (1 local, 1 remote). Editors/readers should be able to quickly determine the source of each property used to make a claim about an entity. - Users should still be able to search for both types of properties by either the P-id or property label **Questions to answer:****UX Guidance** - Should the user always be shown BOTH local and remote properties in the search results when adding statements? - If yes, how should the properties be displayed? - How will the user know which properties in the results are local and which are remote?- Yes, with local properties somehow privileged in the ranking/sorting [Stage 1] - How are the properties sorted in the results? E.g. Local properties first, then remote… or whichever is closest to the search term? - If no, should the user instead select their property source before searching for the properties? **Proposed User’s Task Flow for FedProps v2 :** TBDwill the user know which properties in the results are local and which are remote? - Display an indicator for the remote properties that is consistent across the UI [Stage 2]