Change Details

To avoid for the user to come back and schedule again the same origin later, this also manage origins as if the save code now was a lister and record the origin submitted by the user. WIP as tests need updating. Also opened to discuss where that part should go. I've chosen immediately when creating the oneshot task but this could also be put after the first actually ingestion occur and is successful (and not a plain not_found and failed status for example)... @anlambert any thoughts? ^ Related to T1524

To allow user to come and requests once the url and we take care of the rest. We schedule it immediately. Wait for the ingestion to to be ok (it could fail for multiple reasons) and then schedule it for later. todo: - update the tests Related to T1524

To avoid for thellow user to come back and schedule againrequests once the same origin later, this alsourl and we take care of the rest. manage origins as if the save code now was a lister and record the origin submitted by the usWe schedule it immediately. Wait for the ingestion to to be ok (it could fail for multiple reasons) and then schedule it for later. WIP as tests need updating. Also opened to discuss where that part should go. I've chosen immediately when creating the oneshot task but this could also be put after thetodo: first actually ingestion occur and is successful (and not a plain not_found and failed status for example)... @anlambert any thoughts? ^- update the tests Related to T1524