Page MenuHomePhabricator

[Epic] Feedback processes and tools for data-providers
Open, Needs TriagePublic


Wikidata editors find a number of mistakes in the data that we get from other places (i.e. authority controls files, GLAMS, ...). We'd like to have standardized tools and processes to give feedback to the institution/company/... that provided the data so it can be corrected at the source and not just in Wikidata.

Potential problems we'd like to report:

  • wrong mappings to Wikidata items
  • duplicate entries in the source database
  • learning how we should map concepts in 2 different domains e.g. should books in Wikidata has the same structure as a library that use BIBFrame, should a church in Wikidata follow the same structure as a church at the Swedish National Heritage use....
  • ...

Existing tools and processes:


Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 22 2018, 1:33 PM
Salgo60 added a subscriber: Salgo60.

Property proposal related to this see maintenance_tag

Salgo60 updated the task description. (Show Details)Nov 18 2018, 2:34 PM
Salgo60 added a comment.EditedTue, May 14, 12:51 PM

We are right now seeing a small chaos at VIAF regarding handling the Swedish National Libraries new system that is LIBRIS-URI Property:P5587 see T223259: LIBRIS XL <-> VIAF <-> Wikidata

I have asked VIAF and LIBRIS has been asked about plans but

  • no one has published what they will do
  • VIAF is starting mixing Property:P906 and Property:P5587
  • Swedish LIBRIS says after 2 email/questions to them that they have error reported it to OCLC/VIAF but they give us no Task ID or description what they think is wrong or the status

My conclusion is

  • a better change process is needed
  • tasks/progress should be trackable
  • public Workboards are needed so we can link and track what is happening like we can with Wikidata using Phabricator