| abian added a comment. |
Sadly, I can't guess how many people would finally use these features, this would mainly depend on how much we promoted KNIME and the Wikidata nodes after their possible development. I'm sure I would use these nodes very often if available; :-) however, I'm a regular user of KNIME, and that's not the general rule.
In Wikidata it happens that many people dump data once and don't worry about keeping these data updated. KNIME workflows can contribute to improve this situation, but only if editors want to install and use KNIME with that purpose and if they want to share their workflows under a free license to ensure the continuity of their tasks. The ideal situation would be to have a complete, ad hoc web application to design and share Wikidata workflows, but that would be too resource-consuming, so I see KNIME as the nicest alternative.
About the R integration, I wonder if users would have to install R separately as a requirement to use the Wikidata nodes. If so, this could make the installation tedious and could reduce the impact of this development.
As a first step, I think it would be positive to try contacting KNIME directly and telling them how cool Wikidata is and how useful it would be to integrate KNIME with Wikidata in case they can take care of the development (see also https://www.knime.com/nodeguide/visualization/geolocation/visualization-of-the-world-cities-using-open-street-map-osm). Some contacts that I've just found are Rosaria Silipo (Twitter DMR_Rosaria, email address rosaria dot silipo at knime dot com) and general addresses info at knime dot com and contact at knime dot com.
- we need to understand exactly and precisely what functionality we would like to have integrated via KNIME nodes to work with Wikidata.
My proposal, feel free to change it if convenient:
- To read:
- Submit an arbitrary SPARQL query and return the results as a KNIME table.
- Given a KNIME table with a column of Wikidata IDs as an input, add one or more new columns with the requested values: the label or the description in a certain language or the truthy values for the requested properties.
- To write:
- Given a KNIME table as an input, add the statements in it to Wikidata. Each row is a different statement, and each column is a different part of the statement (the ID, a property/predicate and a value should be mandatory; an arbitrary number of pairs property-value as qualifiers or references should be optional). This format could be very similar to QuickStatements'. With any number of violations of mandatory constraints greater than 0, KNIME should throw an error so that the node can't be executed until there are no violations of mandatory constraints. Ideally, the rest of violations should be marked as KNIME warnings.
- Extra: The same, but for Lexemes and Forms.
- To login: Being logged should be a requirement for editing Wikidata from KNIME. Credentials shouldn't be permanently stored in the workflow nor exported.
Cc: GoranSMilovanovic, Lydia_Pintscher, abian, Aklapper, Lahi, Gq86, Soteriaspace, Jayprakash12345, JakeTheDeveloper, QZanden, LawExplorer, Wikidata-bugs, aude, TheDJ, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
