Determining production install

[RussellMcOrmond]

We have some options that we didn't have before.

• Separate AIP package creation from DIP creation (=Upload to Access platform)
• DIP creation can be managed within Archivematica by Platform staff, handled as a separate automation, or both.
  • DIP creation (upload to Access) from previously stored AIPs can be in partner data centers, controlled using the Archivematica API
  • This would be the Archivematica replacement of the current Smelter functionality
  • This could alternatively/additional be done manually by Production staff using the same Atchivematica installation as they create AIPs.
• AIP creation can be via servers in partner data centers, or within the same networks as digitisation storage (IE: currently Wellington LAN) with only AIP output being sent to our Swift cluster
• AIP creation can be directly on Linux servers maintained by the Platform team, or on Windows servers maintained by Production team (with support from Platform team).

These different options are worth discussing and exploring.

[RussellMcOrmond]

@hstgelais-crkn-rcdr , @enouserid ,

My recommendation is that for the purpose of this project we proceed under the assumption that a Vagrant setup on Oma, with adequate CPU/RAM allocated, will be used.

DIP work is now in a separate project, so on this server DIP only needs to connect to NAS so that staff can look at what DIPs will look like.

What is still unknown is what we want to do for authentication. Ideal is if we can use OpenID with our existing Microsoft O365 accounts #15

If we are fine with this setup, we can just close this ticket and the work will be completed with other tickets that have already been created. #16 , #18

New tickets will be created as they proceed, for instance on what AIP containers in Swift they wish to create. #16 ends with 3 containers in an "AUTH_crkntest" storage URL, and when they are ready to be making AIPs "for real this time" we will want them in the "AUTH_crkn" storage URL with appropriate names.

[RussellMcOrmond]

Closing -- we can re-open if there are further things we wish to discuss.