As a user, I want to prioritize keeping well-connected entities in the Wikidata graph in the event of catastrophic data loss, so that I can queries are potentially more effective.
This ticket is a part of WDQS disaster planning, and reflects research into mitigation strategies for catastrophic failure of Blazegraph: specifically in the case that the Wikidata graph becomes too big for Blazegraph to continue supporting. This is not a commitment to a long term state of WDQS or Wikidata, but part of the disaster mitigation playbook in a worst case scenario.
- Determine number of Items that don’t have 3 backlinks
- Look at the distribution of number of backlinks, and use that to determine how many backlinks might make more sense