Open gbinal opened 10 years ago
I think it's reasonable to require specificly capitalized strings where there are only a set number of valid entries (enums). It would be nice if the tool itself accepted multiple capitalizations but only saved the proper one, but I'm not sure this is a bug. On the user side of the inventory it's easier to parse the json if you don't have to account for multiple possible capitalizations.
For the few metadata fields that only allow certain very specific entries, the validation is sometimes breaking if something is capitalized when it shouldn't be or the other way around.
At issue are the accesslevel, dataQuality, and accrualPeriodicity fields.