QuickStatements 3.0/Survey/Results

QuickStatements 3.0Software collaboration for Wikidata

AboutSurveyUser storiesTalk page

QuestionsResults

Profile

Please provide your contact information here:

Interpretation

The majority of respondents of the survey shared their contact information: username (94%) and/or email address (92%).

How often do you use QuickStatements?

Interpretation

The majority of respondents of the survey (72%) uses QuickStatements weekly or monthly, which indicates a consistent, but not intense use of the tool.

How long have you been using QuickStatements?

Interpretation

The majority of respondents of the survey (89%) has been using QuickStatements for more than a year, 69% for more than 3 years, which indicates a steady usage of the tool throughout the years.

On which devices do you most frequently use QuickStatements?

Interpretation

Desktop is unanimous among the respondents of the survey. That reflects the nature of the tool dealing with batches and its syntax, both of which are difficult to manage in mobile devices.

How would you describe your role in Wikidata?

Interpretation

The majority of respondents of the survey (75%) declared that they like to model and think about Wikidata ontology, and 33% declared to only do big data imports. We didn't have answers from beginners and linguists, which indicates that those profiles are not very common among QuickStatements users, perhaps of the learning curve for beginners and the limitation of creation of lexemes using the tool. The respondents appear to have a more technical profile interested in ontology and big data imports.

How would you rate your proficiency with QuickStatements?

Interpretation

The majority of respondents of the survey (86%) are sufficiently proficient with the tool.

What types of tasks do you primarily use QuickStatements for?

Interpretation

The majority of respondents of the survey (59%) uses QuickStatements to create new items, including thematic items (bibliographical, artworks and people) and database imports; 68% of the respondents also informed that they use QuickStatements to edit specific or generic statements.

Would you like to join a focus group and/or test QuickStatements 3.0 for feedback?

Interpretation

The majority of respondents of the survey (61%) wish to test the new version upon release. Less respondents (25%) wanted to do a focus group to test the tool.

QuickStatements User Experience

How easy and intuitive is it for you to navigate and use the QuickStatements interface?

Interpretation

Nearly half (46%) of the respondents of the survey have a neutral position about the interface; 37% find it intuitive and/or easy to navigate, which indicates that the interface is not widespread considered hard or confusing to navigate.

How satisfied are you with the performance of QuickStatements?

Interpretation

51% of the respondents of the survey are satisfied with the performance of QuickStatements; 29% of the remaining respondents have a neutral evaluation, which indicates that the performance is not a widespread problem.

Have you encountered any technical issues while using QuickStatements?

Interpretation

78% of the respondents of the survey indicated that they had problems while using QuickStatements. Below there's a list of different types of issues mentioned, with an indication of the most mentioned:

Performance issues

• Slowness in background mode;
• Batches sometimes hang for a long time;
• Hiccups on browser mode;
• Commands often crashes and need to be retried;
• Overload causes long pauses;
• Sometimes batches commands do not load.

Usability Issues

• Statements with different qualifiers are always merged;
• Button "New batch" does not work properly;
• Can not log out;
• Complex syntax;
• No rank editing/setting;
• Statements and references commands are executed separately;
• Structured Data on Commons often does not work.

Documentation and Reporting

• Unclear error messages;
• No status report of the tool;
• Non-detailed documentation.

Functionality and Feature Limitations

• Deleting statements fails;
• EntitySchema formatting fails;
• Can not delete qualifiers and/or references without deleting the whole statement;
• The integration with the API is not intuitive;
• Integration with other tools is often down.

How would you rate the documentation and help resources available for QuickStatements?

Interpretation

51% of the respondents of the survey find the documentation to be at least good. 33% find it average. That indicates that, although the documentation is considered good, there is room to improve.

How do you usually learn about new features or updates in QuickStatements and other Wikidata tools?

Interpretation

52% of the respondents of the survey are updated about QuickStatements through the documentation page. Some respondents also included Magnus Manske's blog posts as one of the channels.

Improvements to QuickStatements

What features do you find most useful in QuickStatements?

What features do you find least useful or redundant in QuickStatements?

Are there any features or functionalities you would like to see added to QuickStatements?

Description	Number of users that mentioned this feature (n = 31)
Add, edit or remove qualifiers or references	8
Add multiple statements with different qualifiers	6
Set and/or edit ranks for statements	4
Aggregate set of commands of the same item in one unique edit	2
Edit the commands directly on the interface	2
Improve error report before running	2
Report of the items edited or created and errors	2
Add images to Wikimedia Commons, with title and captions	1
Add statements with different qualifiers as distinct statements	1
Create an API for tools	1
Define restrictions of entities edited	1
Find a better way to prepare repetitive data	1
Improve error report while/after running	1
Display status report of the tool	1
Undo edits	1

What specific improvements would you suggest for enhancing the QuickStatements user interface?

Description	Number of users that mentioned this feature (n = 14)
Buttons for specific actions (validation of commands, preview item to be created etc)	1
Ensure compatibility with different browsers (Brave, Firefox etc)	1
Errors highlight	1
Examples of different actions and with different types of data	1
Filter executed commands by all types of statuses	1
Guarantee that the stop button works properly	1
Improve documentation	1
Improve speed of execution	1
Integrate EditGroups functionality of reverting batches	1
Interactive and user friendly form for adding, editing or removing statements	1
Keep minimalistic	1
Named batches	1
Spreadsheet-like editor	1
Syntax highlight	1
Upload images with QIDs	1

Which area of improvement should be prioritized for QuickStatements 3.0?

Do you have any additional comments or suggestions for improving QuickStatements?

• Five respondents of the survey demonstrated that they were happy and grateful for this project.
• One respondent raised concerns about the maintenance of the project.
• Another respondent asked for the tool to have its performance improved.
• Another one suggest the implementation of a QuickStatements syntax command line tool interpreter.