Change Details

If we need to use the WDQS for some of our searches, then we need to store commons data in BlazeGraph Wikidata already does this, so perhaps we could copy their approach? We would also need to decide //how// to store data about files (as opposed to wikidata items) Also we'd probably need a mechanism to back-populate BlazeGraph with existing commons data

If we need to use the WDQS (or something analagous to it) for some of our searches (see T194185 194245 T194255), then we need to store commons data in BlazeGraph Wikidata already does this, so perhaps we could copy their approach? Other considerations: - Do we need another instance of BlazeGraph for commons? For the CDQS? Or would it be appropriate to use the WDQS? - We need to decide //how// to store data about files (as opposed to wikidata items) - We'd probably need a mechanism to back-populate BlazeGraph with existing commons data

If we need to use the WDQS (or something analagous to it) for some of our searches (see T194185 194245 T194255), then we need to store commons data in BlazeGraph Wikidata already does this, so perhaps we could copy their approach? Other considerations: - Do we need another instance of BlazeGraph for commons? For the CDQS? WeOr would alsoit be appropriate to use the WDQS? - We need to decide //how// to store data about files (as opposed to wikidata items) Also we'd - We'd probably need a mechanism to back-populate BlazeGraph with existing commons data