Closed skalee closed 2 years ago
@skalee initially we will be using an identical schema for administrative data (incl. NormativeStatus) because the users are ISO and IEC. Other organizations may be supported in the future that utilize different statuses.
To add to this, yes the list of accepted statuses can differ per glossary. If they can be read through a config that would be great.
https://github.com/glossarist/concept-model defines many enums. For example, designation's normative status can be either
preferred
,admitted
, ordeprecated
.Is it possible that some glossaries will require custom values for these enums? For example, normative status in glossary X limited to
preferred
anddeprecated
, whereas normative status in glossary Y extended to e.g.preferred
,admitted
,discouraged
(instead of deprecated),obsoleted
,under_review
?I'm asking because I'm going to validate data, and I wonder if allowed values can be hardcoded in
glossarist
gem, or maybe they should be configurable per glossary? This may have some impact on technology stack.cc @ronaldtse @opoudjis