Re: [jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
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)"wrote: > > [ > https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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) >
Re: [jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
On 23/09/15 15:46, Stian Soiland-Reyes wrote: 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? (for some reason emails don't appear to be copied to JIRA - I'm sure they use to) Adding e-tags to Fuseki is easy enough (well, corner cases around transactions long term maybe ... details ...) but to check requires modification to YASQE/YASR AFAICS. At the moment they are opaque and delivered as minified JS. Haven't found a way to poke from outside but the source looks like there are flags to control persistence which is another option. From a design point of view, it's not like it is wrong; it's difefrent use case. Being able to go back and see previous work in a workbook style is a use case. It's just different from the "explore what is there" use case. Andy
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351144#comment-14351144 ] Stian Soiland-Reyes commented on JENA-890: -- Thanks Ian and Andy for taking this to a more structured discussion. I agree that there is a danger of bloatware - I didn't consider this as such, as Pivot Table was an existing feature in an external dependency, but I see your point on the general direction. +1 to have a wider discussion on dev@ about what is in scope for Jena/Fuseki with regards to data consumers, etc. I have been thinking of several features that would be very useful in that respect that would help query building in a UI, e.g. canned queries per dataset, vocabulary browsing/popup to pick right term, and showing definitions of properties/classes loaded from ontologies. Exactly how to do this in a UI I think needs help from a UX expert like Ian. It might be that such an RDF consumer interface (without going down a bloatware path) could be in scope for Jena, but agree that it might not be in scope for the Fuseki admin UI. I like the common-config.js solution - that means it's fairly easy to enable for particular instances (which I could be bothered to document), and thus I can still play with it right away :-) Can we close this issue, (assuming the most confusing bits are reported upstream) and perhaps re-open it if the data consumer perspective shows up? 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350329#comment-14350329 ] Andy Seaborne commented on JENA-890: Thanks for that - I used the common-config.js route for not, by default, having the pivot table and it seems to cleanly remove it. It is easy to re-enable, manually for now. I think keeping the data developer functionality separate for data consumer functions will be better in the long term; it leaves it as to whether open either set of needs, separately, being a fixed set of functionality or an open ended set of tools for certain situations. But first ... a release. 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349638#comment-14349638 ] Ian Dickinson commented on JENA-890: That's an interesting take, thanks. I wonder if it's worth us taking a step back and thinking about what the goal for Fuseki is, or could be(come). And probably doing it on dev@, rather than on this issue thread! Fwiw, my instinct is to keep focussed on a simple interface that does a good job of managing datasets. Some level of query is a natural part of that process - after I've loaded data, I may want to inspect it to make sure I've done my job correctly. But (imho) what the user of this Fuseki cares about is effectively managing data: loading, monitoring, backing up, performance testing, and security, and doing that effectively, simply and reliably. An alternative view is that Fuseki is an 'out-of-the-box' tool to help get people going on their RDF/linked-data journey. These users problaby don't care so much about managing complex collections of datasets, but want a one-stop shop to load, query and explore their data. Another view is that serious production users want all of the basic management capability, plus the tools to diagnose queries that don't work as expected, monitor usage patterns, etc. Or another is that Fuseki is a 'lite' BI tool for RDF and linked data: load your data, and generate reports and dataviz that allow you to explore data and discover its value. And doubtless many others. It isn't that any one of these is undesirable - I've had situations where I would have loved every capability on the above list. To me, it's at least in-part, a question of keeping focus and avoiding creeping bloatware. One tool *could* do all this and more, but I think that tool would become fat, complex, hard to maintain and harder to use. Treading the Protege path, for example, is something I would want to avoid. 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349611#comment-14349611 ] Ian Dickinson commented on JENA-890: I'm going to ignore your absurd straw man argument, except to note that it's not an effective way to participate in a collaborative discussion. I'm happy to have a reasoned discussion; I don't care about bluster. To the actual point: it doesn't really matter whether you spent 45 seconds or 45 minutes writing a paragraph of explanatory text - people in general won't read it. There's plenty of research to back that up. Here's a sample: http://www.nngroup.com/articles/satisficing/ http://www.nngroup.com/articles/how-users-read-on-the-web/ http://www.uxbooth.com/articles/10-usability-lessons-from-steve-krugs-dont-make-me-think/ notes 1-3 http://guidelines.usability.gov/guidelines/172 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348670#comment-14348670 ] Andy Seaborne commented on JENA-890: Is this a place we want to get to? (We are not there now) # There is a query page that is focused on SPARQL queries, general if simple display of table or graph results. For general usage; quite detailed; for debugging of SPARQL queries etc. The assumption is the user can write SPARQL. # There is one or more higher level functions, task focused, not necessarily general purpose, such as the pivot table. These are on different pages, tabs, ... somewhere away from the general query UI. Getting there may have several steps such as having fixed additional functionality before a general plugin architecure is available. This would be good start a discussion on the YASGUI aspects with Laurens (maybe at https://github.com/LaurensRietveld/yasgui/issues if that is more effective). 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348015#comment-14348015 ] Stian Soiland-Reyes commented on JENA-890: -- I'm afraid I only spent 45 seconds on writing that sentence, that was not my proposed explanation. Are you suggesting that any feature that can't be understood by 99% of users with 5 words must be dropped? There are many features in Jena at risk then.. 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347937#comment-14347937 ] Ian Dickinson commented on JENA-890: That's a remarkable example of a simple instruction text. I'm afraid I stick to my point. Pivot tables have their place, no doubt, but it's far from clear to me that the base dataset management tool is that place. And surely anyone who requires the full capability of Yasr can just run their own Yasgui instance, no? 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14346672#comment-14346672 ] Stian Soiland-Reyes commented on JENA-890: -- -1 to remove it all together. I would still consider it as a useful tool when developing a query - you think you have made the right query, but it's hard to inspect thousands of result rows by hand, and so putting together some stats in the Pivot table can help you check that. There should be many warnings.. for instance using a Pivot table together with a query with LIMIT is a bit pointless. Neither Table nor Pivot tabs work when you do a non-SELECT query. Perhaps a simple instruction text also could help, like To check correlation between variables, drag one of them to the column box, and the other one to the rows box. Drag the value to show to the center box (the default is a count of of matching triples). For instance, with a query like SELECT ?age ?based_near ?gender { WHERE { ... } }, to find the average ?age per ?based_near, drag ?based_near to the rows box, drag ?age to the centre, and select AVERAGE as the function. To split the numbers by gender, drag ?gender to the colunns box. This should give you a table with two columns 'male' and 'female', one row per ?based_near location, and table data containing the average age of those combinations 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345320#comment-14345320 ] Stian Soiland-Reyes commented on JENA-890: -- I would be sad to see it go.. but if I am the only one using it.. Could it be a configurable option to turn on for a dataset? Technically it we get this from the yasr http://yasr.yasgui.org/ which has no easy way to programmaticlly disable it (except hacking the [plugins] list): https://github.com/YASGUI/YASR/issues/56 To disable pivot, comment out 'pivottable' from this line: https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/webapp/js/common-config.js#L58 (This file can also be edited in ./webapp/js/common-config.js of the server distro) 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345364#comment-14345364 ] Stian Soiland-Reyes commented on JENA-890: -- Any defailed feedback on the actual UX of it should be directed upstream to http://yasr.yasgui.org/ https://github.com/YASGUI/YASR/issues .. Ian are you able to formulate this for YASR? 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345351#comment-14345351 ] Stian Soiland-Reyes commented on JENA-890: -- Can also be done programmatically with outputPlugins - see http://yasr.yasgui.org/doc/#config 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345363#comment-14345363 ] Stian Soiland-Reyes commented on JENA-890: -- How about this: Disable pivottable dependency now (is this blocker for the release?) - and then it could later be added in optionally through a Configure dataset button (new bug) 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345384#comment-14345384 ] Ian Dickinson commented on JENA-890: Sorry, but what's the use case for having analysis and charting tools in Fuseki at all? I totally get that such things can be useful for some users in some contexts, and I'm all for people experimenting with RDF-based dataviz workbenches, but Fuseki is a dataset control and publishing UI. It should, in my opinion, be focussed on doing that task well. I'm not, in general, in favour of adding user-configurable options to UI's. I strongly recommend Steve Krug's book on this topic (http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321965515/ref=asap_bc?ie=UTF8). Whenever as a developer you put a user configuration option in a UI, you're doubling the test surface of the system, but moreover you're making the user do the hard work of figuring out what the right behaviour should be for you. 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345385#comment-14345385 ] Ian Dickinson commented on JENA-890: Happy to feed back comments to upstream. The pivot table isn't the only problem with Yasgui, but it is the worst. 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345394#comment-14345394 ] Ian Dickinson commented on JENA-890: (is this blocker for the release?) Do you mean a blocker or the blocker? There are a number of problems with the recent clutch of changes to Fuseki2 - I'm working on fixing them but I'm also very busy with client work. I'll start a separate thread on dev@ to discuss. 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344944#comment-14344944 ] Rob Vesse commented on JENA-890: +1 We should remove unnecessary UI, a nicer UI is valuable but unnecessary UI functionality is not 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344314#comment-14344314 ] Stian Soiland-Reyes commented on JENA-890: -- Hm... I would agree that it is slightly confusing, but it's not very different from how Pivot tables works in Excel - which takes much more time to get used to. http://en.wikipedia.org/wiki/Pivot_table anecdotally I figured it out in a couple of minutes and used the Fuseki 2 pivot tables and plots during an RDF hackathon to show correlation (or lack of) between different plant phenotypes (e.g. fruit size vs. leaf size). 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)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344687#comment-14344687 ] Ian Dickinson commented on JENA-890: anecdotally I figured it out in a couple of minutes That, right there, is a perfect illustration of a non-discoverable user interface. If it takes the user several minutes to figure out, and is easier with prior experience of a reference tool that itself is quite complex, then clearly it's not aimed at the general user. Fuseki is not an RDF analysis and charting tool. That's a great thing for someone to develop, but it's a separate research and development activity. Fuseki should simply do a good job of providing a UI for people to manage the serving of RDF data via HTTP. 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)