[FOLIO-470] Discuss and design support for removable and dynamic fields Created: 09/Feb/17 Updated: 18/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Umbrella | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | Jakub Skoczen |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | spike, sprint8 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
Related to the work on the user-metadata https://docs.google.com/spreadsheets/d/121RpsJNaewhQEKb7k58eNVIhZ7N9oSWowNRJGYjPJ2M/edit#gid=0 We have discussed two different approaches: 1. removable fields are part of the schema and validated there but may be "hidden" and optional 2. dynamic fields are covered by a user define map, where no validation happens 3. we need to be able to constrain the list of values for some fields, that should be configured per installation |