Submit approved URL Task

[maxachis]

When URLs are finally approved, we should not submit them right away, but store them to be submitted as a task

Workflow

1. SC retrieves all sources labeled as approved and relevant in the database, along with the user ID of the approving user
2. SC routes these sources to the Data Sources App
3. Once confirmed as approved in the API response, SC marks the source as submitted in the source collector database.

Internal Logic

The entry submitted to the /data-sources endpoint will receive additional details, including:

• record_type: Provided by final review
• agency_id: If any, provided by final review
• url_status: ok
• approval_status: approved
• name: Provided by final review, see Create logic for auto-providing name, description, other data sources metadata, where applicable. #158
• description: Provided by final review, see Create logic for auto-providing name, description, other data sources metadata, where applicable. #158
• submission_notes: "Collected by {collector_name} collector, url_id: {sc-url-id}

The properties to be provided will be comparatively sparse compared to the full array of options available in the data_sources table or the /data-sources GET endpoint, lacking details such as detail_level, agency_originated, and so on. These would need to be amended at a later point.

[maxachis]

This is blocked until the sub-issues are resolved: We need to add additional information prior to submitting to the data sources.

[maxachis]

Note that my current logic I'm working on will also resolve #157, so bear that in mind