| Author | Marc Johnson |
|---|---|
| Status | DRAFT |
| Feedback Requested | |
| Deadline for Feedback | |
| Summary of Decision | |
| Decision Maker(s) | |
| Date Decided |
Context
FOLIO primarily has two ways to represent the choice of a value from a set in back end APIs: enumerations and reference records (there are some exceptions, including unconstrained strings and hard coded sets).
...
Below is a comparison of how the characteristics affect this (and related behaviour) behaviour.
| Situation | Enumeration | Reference Records |
|---|---|---|
| When importing a MARC file, how does data import know the correct source to use? | Can be safely hardcoded | Needs to be identified during the process, maybe via configuration |
Impact of the characteristics
...
If the set of reference records can be changed for a tenant (one of the powerful characteristics) then there needs to be an understand of how that effects other records or systems that refer to members of the set e.g. what happens if a status or type no longer exists?
Open Questions
- Are there any other options that have not been considered above?
- How do client modules identify a specific member of the set in order to attach meaning or semantics to it?
- What should happen if no reference record can be found using the chosen identification?
...