[ 
https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Reply via email to