There is only one where the testing if a new file exists, is in the pull_location CRON job . Which is done once a day.
The problem is that if we do an ontology reprocess with the ncbo_ontolgy_process script, it will not test the existence of a new version.
Solution
There are two ways to solve this
The first and simple one is to just add a script called ncbo_ontology_pull to do the pull on demand.
The second more complex, is to add in the submission process workflow a step that comes before the generate_rdf step called do_pull_location that will download and create a new submission if a new version is found.
Issue
There is only one where the testing if a new file exists, is in the pull_location CRON job . Which is done once a day.
The problem is that if we do an ontology reprocess with the
ncbo_ontolgy_process
script, it will not test the existence of a new version.Solution
There are two ways to solve this
ncbo_ontology_pull
to do the pull on demand.