Page MenuHomePhabricator

Named Queries
Closed, InvalidPublic

Description

history -> result <- query, value inserted for param, value... (has a wiki title, rendering shows result, how to deal with mutliple languages?) <- query template, param, ... (has a wiki title, content contains editable SPARQL, possibly is an entity with label for multilingual title)

This allows not duplicating the same queries all over the place. And the stored result can be updated when there are resources instead of not being available when the cache timed out. The history of results can be used to show a diff and to trigger notifications when the content changed.

Similar to Query Templates / Named Queries is the idea of Query Entities / Query Entity Type. We also talked about possibly needing conversion of a sparql result to wikidata data model and back. Can we link more to past discussions?

Stored results and named queries will be needed for T126741. See also T126730. Scribuntu / Lua also needs access to those results.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 29 2016, 9:16 PM
JanZerebecki renamed this task from named Queries to Named Queries.Apr 29 2016, 9:32 PM
JanZerebecki updated the task description. (Show Details)

Dedup this ticket with T67626 and T132784.

thiemowmde closed this task as Invalid.Dec 7 2017, 3:13 PM