No subject

scalability, for large consortia.  It can handle a huge amount of data
and complexity.  It may be overkill for a K12.  Yet a lot of smaller
libraries use and are very happy with Evergreen.

> How do upgrades, etc. work?

This too can vary, particularly depending on who is doing the work and
how the software has been configured.  Evergreen _can_ be deployed in
such a way that minor upgrades can happen seamlessly without any
downtime, and major upgrades very quickly (while allowing for a
read-only view of the catalog and SIP interface during the upgrade).

> What are the potential challenges of using open source software?