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

Execute LOV locally / offline #11

Open
JohannesLipp opened this issue Oct 13, 2021 · 5 comments
Open

Execute LOV locally / offline #11

JohannesLipp opened this issue Oct 13, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@JohannesLipp
Copy link
Member

JohannesLipp commented Oct 13, 2021

Currently, our recommender contacts the live LOV API. We would like to avoid downtimes and bandwidth limitations and therefore need a local instance of LOV. Please deploy LOV locally (see their source code). The software versions might require a proper investigation (cf. this issue).

FYI: The LOV repo has multiple forks, out of which some might give insights on version numbers.

@JohannesLipp JohannesLipp added the enhancement New feature or request label Oct 13, 2021
@JohannesLipp
Copy link
Member Author

JohannesLipp commented Oct 26, 2021

@alihussainiam please note this recent comment that might help, because it particularly point to these run instructions.

@alihussainiam
Copy link
Member

alihussainiam commented Nov 15, 2021

matched the compatibility of dependecies, solved for config and .pem file issues. Version lts/fermium for node.js is working for now.

But Elasticsearch connector throwing maximum heap size inside node app (investigating). Using elasticsearch latest via docker container. With self host mongd server

image

@JohannesLipp
Copy link
Member Author

Thanks, what are your suggestions: How can we continue?

@alihussainiam
Copy link
Member

alihussainiam commented Dec 14, 2021

Thanks, what are your suggestions: How can we continue?

Investigated and resolved the errors. The app is now working but the data files are missing. sparql editor crashes the app at the moment due to no error handling in case of data store failing to return no results whereas a few api endpoints for getting descriptive info works. Pasting screenshots below.

screencapture-localhost-3333-dataset-lov-sparql-2021-12-14-12_48_10

screencapture-localhost-3333-dataset-lov-api-2021-12-14-12_48_26

screencapture-localhost-3333-dataset-lov-2021-12-14-12_47_54

@JohannesLipp
Copy link
Member Author

@alihussainiam please post any intel/insights you gathered to this issue or to a branch in this repo. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants