The terminology updates broke newly-cloned repos (without terminology) and the server config dialog box that appeared when you click on the version identifier at the bottom of the interface if you attempt to use the old terminology files. Also, the interface did not state if some codesystems are now being restricted from use due to licensing issues.
This makes it so that inferno should work on a newly cloned instance, an instance with the old validators loaded, and an instance with the new validators loaded. Additionally, this messgae should pop up if you enable the terminology_config.yml that is in resources/terminology with restricted terminology.
Summary
The terminology updates broke newly-cloned repos (without terminology) and the server config dialog box that appeared when you click on the version identifier at the bottom of the interface if you attempt to use the old terminology files. Also, the interface did not state if some codesystems are now being restricted from use due to licensing issues.
This makes it so that inferno should work on a newly cloned instance, an instance with the old validators loaded, and an instance with the new validators loaded. Additionally, this messgae should pop up if you enable the
terminology_config.ymlthat is inresources/terminologywith restricted terminology.