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