2024-03-13 Avyre/Convotis/ULib Meeting notes

Introductions and context

Tim: thanks to Convotis (CV) to meeting with us, we aren't your client and you are saving us time and heartache. The ref doc and what we got from Convotis, we don't have a lot of questions. Setup is fairly vanilla for us. Certain small clarifications for us on setup is all.

Ken: 95% of censhare customers use Convotis for cloud services, so CV knows what they are doing. Avyre contracts with CV to install modules. 
- GK: they will not install censhare in an infrastructure which they did not build or maintaining. Supporting customer and answering questions only. 
- Tim: GK answered a question, bc in a way they can't build this environment without installing some of the software it has to run, right? How can we split the install up? We have apps that are far more complex that this that are homegrown.
- Ken: can bring in some of censhare's tech team when questions come up. censhare partner manager is Shannon. CV role is advising?
- Angela: where is the separation btw CV and implementation partner.
- Tim: We need to be able to stand this up and tear it down at will. Any terraform or ansible guidelines or scripts would be helpful if they are sharable

Tim's questions:
1. Not clear on the adoption at UVA, how users will access content. ER popped in to say "it will depend" on the owners of the content, and this will be a matter resolved internally at UVA. This one is on me.
2. AWS setup between CV and Tim, IP restriction. EC2 instances and ALB/AWS. Flexible to customer requirements (this meeting is being recorded by Avyre). May be a way to cut costs and save performance, per Tim.
3. Is key cloak (open source authentication software) SSO compliant? Also Tim thinks it will be a very small group accessing the censhare environment, but I stepped in to say it is a small group adding content, but a large group accessing it. Ken will put users, domains, access on application side. Ken and Tim will work on that together.
4. Kubernetes and EKS clusters in diagrams for censhare. We don't use those at UVA. Noted as non-production environment. Angela from CV confirms that is an error. We can run things in a docker container instead of Kubernetes, etc. GK and Tim agree.
5. Does install happen manually? Yes. Tim wants to understand what we can quickly rebuild if things go down. Can ansible-ize the full install but it isn't done yet? Unclear, but they don't have it yet anyway.

Tim: these were the main things we needed clarification on, now we are pretty confident about building it at UVA.
Ken: simple and easy, consult with CV when needed. Any other questions for CV before CD and ER fill in gaps on migration?
Tim asks for documentation from CV they can share, Angela will send some.

Switched gears to migration.
CD: unclear about priorities for content. Easy, or not available? I'd go with N/A first.
KZ: "migration tooling" needs to be licensed if we use it ourselves. 
ER: Can KZ define the difference between migration and ingest?
CA: Comms has no metadata structure, so hard to start with. Pulling DPG content is more metadata rich. 
KZ: preparing internal readiness. "Active & live" content, and also "stored" content. 
ER: why would we put "inactive content" into censhare? We are not using DAM for dark storage, clarified this for everyone.
CD: a lot of SC content that needs to go in is not accessible now, but ER/CD clarified it should be accessible at least to UVA patrons, if not OA.

CD: so can we curate content in groups, then put it into censhare? Not hook up a hose and just suck it in, right? 
KZ: yes. We will phase it, get the curation right, then turn on the firehose when/if we are ready. Migration is their business, they know how to work through the process quickly and cost-effectively. 

TS: one more question. we have the ability to create a website in censhare, right? Would this work for our old legacy projects? (So does it work better than IA/ArchiveIt?) ER asked TS to put a pin in that, out of scope for this project.

KZ will take a "discovery route" on migration for SOW.

DAM conf in Oct in NY we should go to.