Page MenuHomePhabricator

WikidataCon 2019: We need a better model communicating quality/relevance of sources in Wikidata / Provenance
Open, Needs TriagePublic

Description

Proposal for WikidataCon 2019

I think we need to try formalize better the TRUST of sources used. My comment at Wikidata conf Q & A 2017 at 42 min

Lesson learned

  1. Adding SBL Property 3217 is that +7500 imported external identifiers has in WIkipedia articles in +200 languages --> that if Property 3217 should be trusted we need to formalize this so an reader easy get an understanding of the quality/trust also if this source is unknown
  2. T200668: Set up Nobel Data as federated search with Wikidata Wikidata <-> Nobelprize.org we have an external datasource with maybe good trust but no provenance and in Wikidata we have sources for most birth/death dates et al but as Nobel prize winners are from the whole world its difficult to understand the quality of sources you never have heard about before

My conclusion: Wikidata/Wikipedia is an excellent platform adding value/feedback/gathering knowledge/discuss the quality of sources and the TRUST we should have when using them. Wikidata is a tool to maybe do this in a machine readable way. Best would be if we also could combine this with data from external organisations.

Some scenarios I start to see were we need models for TRUST

  1. We have a very trusted source with a good QA process - example SBL Property 3217
  2. We have a source that maybe is good it has been there for some 100 years BUT has no Provenance in the old world people trusted this catalogue but now with Linked data we can easy see that we have a mismatch between this catalogue and a catalogue with provienance - example federation with Nobel Prize see T200668: Set up Nobel Data as federated search with Wikidata
  3. We have a source with authorities but we start see antipatterns that they use Wikipedia as a source instead of the primary source
  4. Genealogy sites like GENI and Wikitree - could add excellent value were we have a highly skilled person doing the work with local knowledge but could also be a disaster based on an old unsourced import. Problem I see with genealogy sites is that many profiles dont get so many "eyes checking the quality" ( I guess nearly the same problem as with a small Wikipedia community) --> quaity problems
  5. New applications like iNaturalist makes it easy to add rus to community researched data video / how iNaturalist is used at the Natural History Museum of Los Angeles County


Why not make it easy for the reader and show featured sources

See also

  1. T222006: Presentation Linked Data Sweden - Wikidata
  2. T202530: [Epic] Feedback processes and tools for data-providers
  3. WikidataCon_2019/Submissions/We_need_a_better_model_communicating_quality_of_external_sources_in_Wikidata
  4. CiteWatch
  5. Wikipedia:Reliable_sources/Perennial_sources
  6. Wikipedia:Reliable_sources/Noticeboard
  7. Cite_Unseen
  8. Draft in Swedish about describing a highly trusted source WD Property3217 - Source:SBL in Swedish - Google translated
  9. Discovering Implicational Knowledge in Wikidata pdf

Event Timeline

Salgo60 created this task.Apr 30 2019, 8:29 AM
Salgo60 renamed this task from We need a better model communicating quality of sources to WikidataCon 2019: We need a better model communicating quality/relevance of sources in Wikidata / Provenance.Apr 30 2019, 9:10 AM
Salgo60 updated the task description. (Show Details)
Salgo60 updated the task description. (Show Details)Apr 30 2019, 9:23 AM
Salgo60 updated the task description. (Show Details)Apr 30 2019, 11:47 AM
Salgo60 updated the task description. (Show Details)May 1 2019, 8:25 AM
Salgo60 updated the task description. (Show Details)
Salgo60 updated the task description. (Show Details)May 2 2019, 1:34 PM
Salgo60 updated the task description. (Show Details)May 2 2019, 4:01 PM
Salgo60 updated the task description. (Show Details)May 23 2019, 5:00 AM
Salgo60 updated the task description. (Show Details)May 23 2019, 5:17 AM
Salgo60 updated the task description. (Show Details)May 23 2019, 5:35 AM
Salgo60 updated the task description. (Show Details)May 27 2019, 10:19 AM
Salgo60 updated the task description. (Show Details)Jun 7 2019, 6:15 PM
Salgo60 updated the task description. (Show Details)Jun 28 2019, 8:52 AM
Salgo60 updated the task description. (Show Details)Jun 28 2019, 11:51 AM
Salgo60 updated the task description. (Show Details)Jul 7 2019, 6:44 PM
ElanHR added a subscriber: ElanHR.Aug 2 2019, 5:40 PM
Salgo60 updated the task description. (Show Details)Aug 18 2019, 1:24 AM