Skip to content

/scholia

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

Separate the SPARQL queries from the surrounding JavaScript and Python #791

Open
Daniel-Mietchen opened this issue Jul 22, 2019 · 0 comments

Comments

Assignees
No one assigned
Labels
JavaScript Python SPARQL Scholia-sprints documentation usability
Projects
  
To do in Meta
  
Robustifying Scholia (awaiting triage)
  
To do in 1. Back-end development and testing with pilot corpora
  
To do in 6. Improving documentation of corpus, code, queries, workflows, examples and related resources, as well as limits of Scholia
Milestone
No milestone
1 participant
@Daniel-Mietchen
@Daniel-Mietchen
Copy link
Collaborator

commented Jul 22, 2019

I think we had a ticket for this already but could not find it. In any case, the SPARQL Visualizer (cf. #754 ) seems to have done this to some extent already.

@Daniel-Mietchen Daniel-Mietchen added JavaScript SPARQL documentation Python usability labels Jul 22, 2019

@Daniel-Mietchen Daniel-Mietchen added this to To do in Meta via automation Jul 22, 2019

@Daniel-Mietchen Daniel-Mietchen added this to To do in 6. Improving documentation of corpus, code, queries, workflows, examples and related resources, as well as limits of Scholia via automation Jul 22, 2019

@Daniel-Mietchen Daniel-Mietchen added this to To do in 1. Back-end development and testing with pilot corpora via automation Jul 22, 2019

@Daniel-Mietchen Daniel-Mietchen added the Scholia-sprints label Jul 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.