When searching in a catalogue, the backend stores all records it found in the triplestore so that they can be reused when a collection is accessed. However, this may take up to a couple of seconds and there is no reason to wait until the request has been answered.
Django does not have built-in support to execute code after the response has been returned, so this would have to be done using Celery, threads or otherwise.
In theory, it is possible that a user adds records to a collection and then requests them before the records are completely added to the triplestore. However, in practice that is almost impossible.
When searching in a catalogue, the backend stores all records it found in the triplestore so that they can be reused when a collection is accessed. However, this may take up to a couple of seconds and there is no reason to wait until the request has been answered.
Django does not have built-in support to execute code after the response has been returned, so this would have to be done using Celery, threads or otherwise.
In theory, it is possible that a user adds records to a collection and then requests them before the records are completely added to the triplestore. However, in practice that is almost impossible.