Agreed about stale results. I guess it could be tricky to invalidate if the dataset is updated out of bounds (e.g. in a different browser or separate http calls) - is there a timestamp resource in Fuseki that the UI could check? On 22 Sep 2015 13:36, "Andy Seaborne (JIRA)" <[email protected]> wrote:
> > [ > https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902505#comment-14902505 > ] > > Andy Seaborne commented on JENA-890: > ------------------------------------ > > (restarting discussion) > > The YASGUI has some other interesting effects - it uses local storage for > query and also results. Restarting the server, or updating the data, does > not invalidate the local storage. When going back to the query page, the > old results are present. > > This seems to be controlled by files defaults.js YASQE (query persistence) > and YASR (results persistence). I have not found out how to control that > externally - the files are in the minified js. > > Persistent query is tolerable, but I find stale results confusing. They > may not even be related to the dataset as they are global, not per dataset. > > Proposal: Move this to a separate pages, put in qconsole for a more > admin-task-focused query-live experience. > > > Pivot table in Fuseki2 has confusing design and user experience > > --------------------------------------------------------------- > > > > Key: JENA-890 > > URL: https://issues.apache.org/jira/browse/JENA-890 > > Project: Apache Jena > > Issue Type: Improvement > > Components: Fuseki > > Affects Versions: Fuseki 2.0.0 > > Reporter: Ian Dickinson > > > > The SPARQL query tab on the Fuseki2 interface has an option in the > results pane labelled 'pivot table'. It's very, very unclear what this > does. It appears to be an experimental feature of some kind, but it does > not provide a clear, discoverable user experience. In fact, after playing > with it for some minutes, I still can't figure out what it is actually for. > > I suggest that either the UX of this feature is radically improved, or > we remove it from Fuseki2 until it is ready for wider exposure. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
