Data Stewardship Policies
The Wikibase Stakeholder Group surveyed its members about data management policies for Wikibase projects they’re working on or are affiliated with.
In the table below policies are expressed in columns A to E, and distinguished by different abilities for “members” of a community (checkboxes in green) and “non-members” or “anyone” (checkboxes in blue). Every project has its own way of defining the boundary of its community.
The term “outside repository” is used from the perspective of a Wikibase project for any linked open data repository that is not stewarded by the project. This includes, but it not limited to, Wikidata.
This survey data might be updated in the future.
A | B | C | D | E | |
internal | community | community + federation | community + data sync | fully open | |
access | |||||
anyone can browse & query | ✔ | ✔ | ✔ | ✔ | |
editing | |||||
non-members can edit | ✔ | ✔ | |||
community can edit | ✔ | ✔ | ✔ | ✔ | ✔ |
moderation | |||||
anynone can moderate | ✔ | ✔ | |||
community can moderate | ✔ | ✔ | ✔ | ✔ | ✔ |
technical infrastructure | |||||
outside community control | ✔ | ✔ | ✔ | ||
community-controlled | ✔ | ✔ | ✔ | ✔ | |
Policy summary | Community runs a fully private instance of Wikibase, possibly federating in a network of such instances. | Community runs a public-facing Wikibase, only community members can edit. | Community runs a public-facing Wikibase that federates with an outside repository; links are pointing from the community instance to the outside repository to enrich local presentation of data. | Community runs a public-facing Wikibase that exchanges data with an outside repository. Users of the outside repository can discover the community's Wikibase. | All data is publicly available and free to edit. |
Ravensburger AG | |||||
LUDAP | |||||
CDS | |||||
Digital Scriptorium | |||||
Smithsonian Lib Archives | |||||
Beyond Notability | |||||
enslaved.org | |||||
EU Knowledge Graph | |||||
Rhizome ArtBase | |||||
Semantic Lab @ Pratt | |||||
WikiFur | |||||
Wikidata | |||||
Wikimedia Commons |
If a project spans two columns, it either has parts of both or is currently using one policy but moving towards another. In the survey data presented, all projects that want to further develop their policies are moving towards policy C.
The result shows a strong bias towards cases B and C, in which communities create and publicly share data. Half of these projects are using remote public data to offer users of their system more information gathered from outside resources.