Strategy/Wikimedia movement/2018-20/Working Groups/Partnerships/Recommendations/Q2 R4
Recommendation 4: Data partnerships approach to fulfill the vision of knowledge as a service for our partners
Q 1 What is your Recommendation?
The movement should continue to pursue data partnerships with large knowledge holding organisations such as libraries, archives and research institutes. We recommend prioritising working to bring them into the use of linked data and our software, with a longer term goal of them integrating more into our projects.
This will require more data infrastructure and support for users of our linked data models and software.
Q 2-1 What assumptions are you making about the future context that led you to make this Recommendation?
Linked data and projects such as Wikidata will continue to be important to our movement and the work of partner organisations.
Q 2-2 What is your thinking and logic behind this recommendation?
Not all data holding partner organisations have the same skills, resources and content. Approaching our movement’s data partnerships will require a broader approach beyond projects such as Wikidata.
Encouraging organisations to think about linked data before how they interface with projects such as Wikidata will help manage and distribute capacity (on both sides) and encourage technological innovations in terms of linking the data of knowledge holders and our projects.
Q 3-1 What will change because of the Recommendation?
Our involvement in data will be less focused on our own, single, linked data project, and spread to the many linked data projects of our partners, connecting them together.
Q 3-2 Who specifically will be influenced by this recommendation?
Anyone participating in data partnerships, but also third parties and audiences who may benefit from a larger, Wikimedia movement-driven linked data infrastructure
Q 5 How does this Recommendation relate to the current structural reality?
Our current structural reality is that we try and fit content to our projects (licensing, formatting) and then make that content available via our projects. This moves us slightly away from our project focus to a methodology focus that fits our projects in a less specific way but has wider benefits.