You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Item 3: Establish automatic vocabulary/ontology update cron jobs OR (preferred) implement function to allow IODE staff to update vocabulary/ontologies by uploading RDF
Element 84 has migrated the internal graph database from Virtuoso to Neptune. A vocabulary/ontology ingest pipeline has been successfully implemented that enables IODE OBPS staff to add or update vocabularies/ontologies while only having to interact with AWS S3. IODE OBPS staff are only required to upload the vocabulary/ontology and small metadata file to S3 where the automated process will then asynchronously bulk load the vocabulary/ontology into Neptune. Once the vocabulary/ontology has been bulk loaded, the pipeline automatically triggers an update to the terms index where the new terms are added to the Elasticsearch index. The pipeline then triggers a bulk ingest which results in documents being re-tagged
We have user requests to upload WoRMs and the ASFA subset of the multilingual AGROVOC. With the above can we now upload these two new vocabularies please
The text was updated successfully, but these errors were encountered:
In the E84 Contract Final Report for their contract Dec 2021 https://drive.google.com/file/d/12ngVQqXSpkmwkuCDIzcPKCaHNyB_it8Y/view?usp=share_link, the below extract was included that covered providing the ability to update vocabularies/upload new vocabularies.
Item 3: Establish automatic vocabulary/ontology update cron jobs OR (preferred) implement function to allow IODE staff to update vocabulary/ontologies by uploading RDF
Element 84 has migrated the internal graph database from Virtuoso to Neptune. A vocabulary/ontology ingest pipeline has been successfully implemented that enables IODE OBPS staff to add or update vocabularies/ontologies while only having to interact with AWS S3. IODE OBPS staff are only required to upload the vocabulary/ontology and small metadata file to S3 where the automated process will then asynchronously bulk load the vocabulary/ontology into Neptune. Once the vocabulary/ontology has been bulk loaded, the pipeline automatically triggers an update to the terms index where the new terms are added to the Elasticsearch index. The pipeline then triggers a bulk ingest which results in documents being re-tagged
We have user requests to upload WoRMs and the ASFA subset of the multilingual AGROVOC. With the above can we now upload these two new vocabularies please
The text was updated successfully, but these errors were encountered: