[PROCESS] Need for a explicit 0. Acquire step for external content in the Intake process

[mwherman2000]

Need

Need for a explicit 0. Acquire step for external content in the Intake process

Proposed Solution

Slack conversation:
Michael Herman 14 hours ago
0. Acquire. Acquire content from partner organization. Verify conformance with copyright and licensing conditions upstream as well as ToIP Chapter 6 requirements. Satisfy the 3 sets of requirements. Archive a copy of the original content. (edited)

Daniel Hardman 4 hours ago
Michael: This is interesting. We had imagined that ingestion begins, in one scenario, when someone submits a PR (which captures an archived copy of the original content). The PR is then evaluated as you suggested, and if deemed acceptable, it is merged. Merging doesn't complete ingestion; it just makes the source data publicly visible in a /submissions folder. Then we run a tool (the one we're trying to spec out) to actually complete the ingestion work. So your "Acquire" phase is breaking apart the multipart flow of Ingest. (There are two other Ingest flows we had imagined: one where a single term is proposed, which would be driven through a github issue, and one where a recurring import is proposed, which would require coding or at least config of the new datasource. But ignore those for a moment.)
Do you feel that conceiving of Ingest as separate from Acquire gives us a more helpful mental model? If so, what advantages do you foresee?

Michael Herman 3 hours ago
From a legal/copyright/licensing perspective, there should be/needs to be a clear demarcation point where content external to ToIP is "acquired" ...as in uploaded or stored in any way in a ToIP repository.

Michael Herman 3 hours ago
Ingestion can have a variety of meanings ...hence, I used the term "acquire".

Michael Herman 3 hours ago
There's multiple copyright/licensing requirements that need to be met during the Acquire step ...as soon as external content is accepted ...to avoid issues like issues #46 and #47 .