Store Odin resource configs in application database

[helrond]

Is your feature request related to a problem? Please describe.

There are a number of enumeration lists (in /transformer/resources/configs.py) which control values in source data. These lists are likely to be institution-specific. We want to limit editing of application code, while also providing an application that is highly configurable and can meet the needs of multiple institutions.

Describe the solution you'd like

Allow enumeration lists to be stored in the application database and managed via Django admin.

Describe alternatives you've considered

An alternative is to move these configs to the main application config file. However, that is less desirable because it adds a lot of weight to the application config, and is less transparent.

Additional context

We'll need to add some helpers to populate these lists with default values, and will need to update tests with fixtures.

[Tyl13]

Using the api provided by ASpace, could we automatically populate the database. For example, we could use a csv provided by ASpace which supplies us with the Enumeration code, Enumeration, Value code, and Value. More detail on idea for implementation with your specific changes are talked about within #526.

[helrond]

Hi @Tyl13 see my comments on #526