Docker Deployment Agreement

There are a few things we discuss with all the customers who receive access to our Docker installation. We ask you to confirm that you understand and agree to these stipulations while you work on the CEDAR platform in your environment.

1. Some requests of you:
   • Don't re-distribute or operationally deploy this Docker installation.
   • Please let us know your requirements/schedule for deploying CEDAR, so we can work with you to meet those goals if possible.
   • Please give us feedback on both CEDAR, and the Docker installation, using appropriate GitHub repositories (issues and pull requests welcome).
2. There are several issues you need to know about (all of which we hope to address at some future date):
   • As our Template Model changes regularly (2-3 times yearly), your deployment templates and instances (or web form instances) will become incompatible with the CEDAR main deployment;
   • Any value sets or provisional classes created by your deployment will become a part of the BioPortal repository (visible to the CEDAR community), and will not be editable by you; and
   • We do not yet commit to an upgrade path that makes it easy to deploy future CEDAR versions.
3. We expect to add features to CEDAR to improve our management of remote instances:
   • tracking the number and size of remote deployments;
   • monitoring and managing the interaction with the BioPortal endpoint, to ensure acceptable response times; and
   • establishing and tracking license(s) under which deployments are being operated and modified.