Skip to content

Feature/provenance (no to be merged) - #29

Merged
white-gecko merged 21 commits into
AKSW:masterfrom
Kyrosh:feature/provenance
Jan 11, 2018
Merged

Feature/provenance (no to be merged)#29
white-gecko merged 21 commits into
AKSW:masterfrom
Kyrosh:feature/provenance

Conversation

@Kyrosh

@Kyrosh Kyrosh commented May 30, 2017

Copy link
Copy Markdown
Collaborator

No description provided.

@splattater

Copy link
Copy Markdown
Contributor

Hey @Kyrosh thank you for your pull request. Can you please

  • create a module containg utils.py and all rdflib clones (evaluate.py ...)
  • move git.py (replacing GitRepo) and graphs.py to core.py
  • check if there is a solution for add/delete quads (via Flask API) that supports provenance without use of FileReference class. If so, delete FileReference from core.py
  • delete deprecated.py
  • are there other candidates that may be merged to a module? (serializer, parser?)

@white-gecko white-gecko left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to put the complete web frontend for the browser presentation into a separate code base? Quit should only contain the SPARQL endpoint and any additional API needed.

@@ -0,0 +1,6 @@
/*!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should not include a static version of bootstrap in the repo, but use something like this: https://pythonhosted.org/Flask-Bootstrap/

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#50

@Kyrosh

Kyrosh commented Aug 10, 2017

Copy link
Copy Markdown
Collaborator Author

@white-gecko It would be possible to provide the frontend as a seperate project. One possibility to do so: the quit store itself provides an API and a minimalistic server for the sparql endpoint. When the fronend is used it could provide its own server, only using the provided API and bypassing the quit store server (only one running). What do you think about this approach? Or we provide the frontend as a seperate package and check in the quit store if it is installed, if so, we use those endpoints instead. Both approaches would be sufficient, i think.

@white-gecko

Copy link
Copy Markdown
Member

@white-gecko It would be possible to provide the frontend as a seperate project. One possibility to do so:
the quit store itself provides an API and a minimalistic server for the sparql endpoint. When the fronend is used it could provide its own server, only using the provided API and bypassing the quit store server (only one running). What do you think about this approach?

I thinks this sounds like the option I'm preferring. The Quit Store provides the necessary API and the front-end is using it. What do you mean by “bypassing the quit store server”?

Or we provide the frontend as a seperate package and check in the quit store if it is installed, if so, we use those endpoints instead. Both approaches would be sufficient, i think.

What exactly do you mean by separate package?

Further I'm looking for the documentation of the newly introduced store modes. Could you please add them to the README in your branch?

@Kyrosh

Kyrosh commented Aug 15, 2017

Copy link
Copy Markdown
Collaborator Author

I thinks this sounds like the option I'm preferring. The Quit Store provides the necessary API and the front-end is using it. What do you mean by “bypassing the quit store server”?

By that I just meant that the frontend has its own flask server, which will be used instead of the one included in the quit store. So we only have one server running at a time.

What exactly do you mean by separate package?

It's basically the same idea as the previous one. Two seperate and indepentent projects and packages.
In the first scenario the frontend server is startet via its own quit.py (just as an example).
In the second one we could run the quit.py of the main project, which checks if the frontent package is installed and available. If so, it registers the frontend endpoints, or otherwise its own endpoints.
Therefore the user won't have to run a seperate project, but instead he/she only needs to install the frontend package (extension).

Further I'm looking for the documentation of the newly introduced store modes. Could you please add them to the README in your branch?

Sure

current_app.logger.error(traceback.format_exc())
return "<pre>"+traceback.format_exc()+"</pre>", 400
else:
return render_template('sparql.html')

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should move to new Quit UI

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#50

current_app.logger.error(traceback.format_exc())
return "<pre>"+traceback.format_exc()+"</pre>", 400
else:
return render_template('provenance.html')

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should move to new Quit UI

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#50

@white-gecko
white-gecko changed the base branch from feature/provenance to master August 21, 2017 14:40
@white-gecko white-gecko changed the title Feature/provenance Feature/provenance (no to be merged) Aug 22, 2017
@white-gecko

Copy link
Copy Markdown
Member

I've deleted some already resolved comments. We should continue the discussion in #47

@white-gecko
white-gecko merged commit 5a77237 into AKSW:master Jan 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants