REST services need to have test cases as well. Since this will be run against a Postgres server, do not mock the values - test against Postgres. Mock is not good enough, as all programmatic responses will always generate positive outcomes. This should be tested against a real service that can be freely destroyed in a test environment.

Add a component that will allow for objects to be stored as an array, renumbered, edited, and deleted from the UI. Example would be to use this in the "Add" section in Fields, as fields can take arrays of examples or enumeration values.

Data types need to be loaded with initial values from the database that indicate core types. These are core types that cannot be modified or deleted.

Add the ability to test a data type through the UI

Namespaces must be changed to:

• Change "name" to be permanently lowercase
• Not allow duplicates

Namespaces service must report namespace errors back in the appropriate response code to the UI app, and the UI app must show the appropriate error when an error is returned.