Open pombredanne opened 3 months ago
Some thinking around the scan queue integration. We could avoid having to change the core model keyed by a URL by adding a field to it (say a JSON field) that would contain a dictionary of all the options to use when creating the SCIO project:
This may be also part of a follow up to https://github.com/nexB/purldb/issues/373
The current scanning capabilities of the PurlDB expose a queue entry for:
For the d2d pipeline run we need two URLs with a #from and #to suffix respectively