This use case starts when an order has been submitted from an end-user to the archive, and the main purpose is to check if an appropriate DIP already exists. It is assumed that this process is preceded by the ‘Validate Order’ process, but it can just as well be the other way round; or the processes may occur simultaneously.
The process may be automated to a certain degree. It depends on archival policies, local repositories, the level of access to these, the correctness and level of detail in the end-user’s order, and on the complexity of the ordered DIPs.
Check DIP availability and suitability
