Allow institutions/funders outside the predefined Organization list (?)

[dougollerenshaw]

institution (and Funding.funder) only accept members of the predefined Organization set. Each entry freezes its name, abbreviation, and ROR id as Literals, and the field is a closed union over those classes, so anything not already in the list is rejected.

This leaves no opportunity to add a new institution beyond what's on the list short of putting in a PR against the aind-data-schema-models repo. This encourages people using the schema to choose Organization.OTHER if the desired institution isn't already listed.

I understand that this avoids, for example, multiple spellings of the same institution. But it adds friction that will discourage proper use of this field, especially if external users adopt the schema. As an alternative, what about accepting an arbitrary ROR-identified organization, then validating that a registry id is present and well-formed, rather than that the org is a known member? This would be in addition to keeping the existing curated entries as convenience constants. That preserves machine-resolvable, deduplicated institutions for the common case without blocking anyone who isn't already in the list.

[dougollerenshaw]

Dan is telling me that I should be able to build the organization model even with it not being in the orgs in data models.

But we should just add this one to the data schema models. Self-assigning.