[
https://issues.apache.org/jira/browse/JENA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833005#comment-13833005
]
Andy Seaborne commented on JENA-420:
------------------------------------
Added a way to add ne datasets+endpoints to a running server.
The URL for the collection of datasets {{/$/datasets}}
{noformat}
POST /$/datasets
{noformat}
with a body that is an RDF graph that is an assembler description of the
{{fuseki:Service}} and RDF dataset will create a create a new set of endpoints.
Currently, you must use "--uber" when starting the server to get dynamic
dispatch. This will change to be the default after more testing.
{noformat}
GET /$/datasets/<dsname>
{noformat}
returns a JSON description of that dataset. This is not the assembler - it's
not possible to recreate a dataset assembler from just the dataset. It may be
useful to store the original assembler.
{noformat}
GET /$/datasets
{noformat}
returns a JOSN structure { "datasets" : [ ... datasets ... ] } (c.f.
{{/$/status}})
What we might have is a collection of templates ... TDB dataset, TDB+test
index, etc etc stored server-side with a few parameters and fill these in by
string manipulation.
The UI can get a template, allow values to be filled in, and then POST to the
collection of datasets.
> Web-based User Interface for Jena Fuseki
> ----------------------------------------
>
> Key: JENA-420
> URL: https://issues.apache.org/jira/browse/JENA-420
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Reporter: Stephen Allen
> Labels: gsoc2013, java, javascript, mentor, rdf, sparql,
> velocity, web
> Attachments: fuseki1.png, fuseki2.png, fuseki3.png, fuseki4.png
>
>
> Fuseki could use an overhaul / rewrite of the web interface. It would be
> great to design a nice web-based GUI interface for both querying/exploring
> the data and for managing Fuseki itself.
> Tools and skills that may be required:
> Java, HTML+CSS, Javascript, Velocity (templates used server-side in place of
> JSP)
> A few ideas to get started:
> 1) Resource Explorer
> This interface allows the user to select any resource from either a list of
> all triples in a graph, or from the results of a SPARQL query. After
> selecting the resource, they can view all of the statements that reference
> the resource.
> 2) Improved Query Input
> It would be great to enhance the query input form for both queries and
> updates. Some features here that could be useful would be an IDE-like input
> box that performed syntax highlighting, automatic indentation, and easy
> commenting out of selected lines of text. Additionally being able to
> pre-populate the input box with the user's commonly used prefixes would be
> great (stored in a cookie or some such).
> 3) Improved Query Results
> Better display of query results (especially SELECT queries). Already
> mentioned was a tie-in to the Resource Explorer, so a user can easily see the
> statements about some interesting resource in the results. But it would also
> be great to layout and format the result table better. Even display the
> results on the same page as the query input box using AJAX. Or allow the
> table to be resorted after the query results have been returned. Also
> display the total number of rows.
> 4) Query Management
> View and manage currently running queries. Display how long queries have
> been executing, and allow the user to cancel queries that may be taking too
> long.
> 5) Fuseki Management
> There are many tasks here that would be great. Expose JVM properties via JMX
> in a nice UI. Things like CPU/Memory usage, disk space remaining, etc.
> Allow initiation of back-up tasks. Allow the user to download a snapshot of
> the repository. Shut down the server. Possibly add and remove datasets
> dynamically.
> Attached are screenshots indicating the current UI and the workflow for
> issuing a query. The idea would be to overhaul and replace most of this!
--
This message was sent by Atlassian JIRA
(v6.1#6144)
