Thank you!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 22 2017
Dec 20 2017
Cool. Anyone up for making a patch again?
Dec 19 2017
Yeah that seems like a good way forward.
I think it'd need to be per property. So something like "P345:tt0133093" would give you The Matrix and only The Matrix. There is probably very little overlap between identifiers that are basically random numbers and letters. But when it comes to account names on social networks for example you want to be sure that you get the right item and not another item who happens to have the same value but for a different social network.
External identifiers are definitely interesting. We have T99899, which might be best solved with Elastic? That would require indexing the external identifiers with the property. If that's not feasible it should also be doable with the SPARQL endpoint though.
The first graph on https://grafana.wikimedia.org/dashboard/db/wikidata-datamodel?refresh=30m&orgId=1 shows the number of new items created over time.
For the particular problem indeed bots could be taken out. The make up the biggest part of new page creations on Wikidata (see https://stats.wikimedia.org/v2/#/wikidata.org/contributing/new-pages if you split by editor type).