-
Notifications
You must be signed in to change notification settings - Fork 0
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
AGROVOC does not pull automatically and does not parse anymore #178
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Relevant post about the issue: It seems the OWL-API tries to create a string too large. |
Error (OutofMemory) reproduced by @jvendetti when parsing (the nq file) "outside" of AgroPortal stack. |
An update :
When generating a RDF/XML file with Protégé and re-opening this same file with Protégé the error shows up again, but this time with a line number : Which bring us to the URI : http://aims.fao.org/aos/agrovoc/xDef_8f48da66 |
indexing error fixed here ontoportal-lirmm/goo@ba27011 Agrovoc is now parsed, indexed but we had this issue in the diff process #246 So I don't think that the automatic pull will work, to follow up in the future releases here #251 |
Since July 2021 version, AGROVOC does not parse anymore.
Plus, we have a pullLocation for AGROVOC :
http://data.agroportal.lirmm.fr/ontologies/AGROVOC/submissions/16?display=pullLocation
But the ontology never get updated automatically (I have to do it manually each month).
January or February release is expected soon to make new tests.
The text was updated successfully, but these errors were encountered: