Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configurable yasgui prefix and query #1683

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SimonBin
Copy link
Contributor

GitHub issue resolved #1680

Pull request Description:

fusekiUI will look for a dataset named yasgui-config to load Example Queries and Prefixes based on the current dataset name


  • Tests are included.
  • Documentation change and updates are provided for the Apache Jena website
  • Commits have been squashed to remove intermediate development commit messages.
  • Key commit messages start with the issue number (GH-xxxx or JENA-xxxx)

By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the Contributor's Agreement.


See the Apache Jena "Contributing" guide.

@SimonBin
Copy link
Contributor Author

if it's decided that we need to avoid using JSON then I can work on manual unwrapping json-resultset, but I wanted to open the PR first

@afs
Copy link
Member

afs commented Dec 16, 2022

Just to be clear - this is too late for 4.7.0.

@SimonBin
Copy link
Contributor Author

no worries, there's always a next version

@kinow
Copy link
Member

kinow commented Jan 6, 2023

Not necessarily what we are doing here, but I thought interesting that prez uses a triplestore dataset that documents the existing datasets in the triple store. Then, through existing vocabularies (dcat/prof/skos/etc) it tries to automatically know what users can do with the dataset, and it renders templates for the user (they are working on a python + vue web app refactoring).

Maybe the idea of a global "triplestore" dataset of sorts, storing some data common to all vocabularies like example queries, and maybe settings, could be helpful for this issue too.

@afs
Copy link
Member

afs commented Jan 7, 2023

Fuseki admin has a system database. Its not used much (flexible data representation not required! and on disk file are easier or user to work with). That could be repurposed.

@kinow
Copy link
Member

kinow commented Jan 7, 2023

Fuseki admin has a system database. Its not used much (flexible data representation not required! and on disk file are easier or user to work with). That could be repurposed.

Didn't know that. +1 !

@SimonBin
Copy link
Contributor Author

SimonBin commented Jan 9, 2023

I didn't see the system database in the dataset list so it might be harder to edit the config from the UI(?)

@afs
Copy link
Member

afs commented Jan 9, 2023

For managing fixed structures, an RDF database is probably over-engineering.

A basic HTTP PUT/GET to a "prefix store" (persisted by a text file - i.e. human editable) and a URL scheme may be better (simpler, easier to maintain, does not require RDF handling in the UI code (potentially yet more dependencies)).

But please ensure the parts of the UI that provide the "workbench" also work when just a SPARQL query endpoint is the target - i.e. it works for any triplestore and that includes a Fuseki server where the UI user is not in charge (not admin). Specific features may not be available in a graceful way.

Yasgui has some configuration features - presumably it uses browser-local storage.

@kinow
Copy link
Member

kinow commented Mar 26, 2023

I think this one requires further discussion and thinking on how to implement it. Also some work on YASGUI integration with Vue.js.

@SimonBin
Copy link
Contributor Author

sure, that's why I opened the discussion :-)

for the example in this pull request, it provides the possibility to change the prefix and sample query list per dataset in the Fuseki UI, and you can edit it using the Fuseki UI built-in graph editor, so that was a plus for us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants