-
Notifications
You must be signed in to change notification settings - Fork 9
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
Run a StemWeb algorithm and fetch results (backend) #103
Comments
@tla Could you please clarify what is meant by this issue exactly? It is possible that I have already implemented this without referencing this issue in the corresponding PR. |
This is yet another service (DHUniWien/Stemweb) that runs through stemmaweb (and has its own set of containers in the docker stack). You haven't implemented it; we can discuss it further at the next meeting. |
Ok perfect, I am looking forward to getting more details about the service. I thought that this issue was referring to the main result fetching after a user visits the home page. |
I dumped all available routes of Stemweb for future reference:
|
OK - also for reference, the only ones we need to care about are the ones specified in the white paper. These are:
|
It's also worth clarifying: we do have to implement one endpoint, referred to in the white paper as |
Just as a reminder: https://github.com/DHUniWien/Stemweb/tree/main/client |
Description
Reimplement the functionality to send data to Stemweb and receive the results. This needs both frontend and backend work.
Requirements
StemwebService
on the frontend to access Stemweb through the middlewareThe text was updated successfully, but these errors were encountered: