Name a set of unrelated refdata kinds that a screen or export groups
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
Decide how the architecture names a set of kinds that a screen, an export or a boundary lists together when no invariant joins them. The BFF convention screen lists the document families, one composite family, and two kinds that the conventions document does not carry: tenor and currency pair. The data classification page does not name that set.
2. Why
The page says a bundle needs an invariant or an all-or-nothing operation, and that a set which needs a screen to be true is not a bundle. It says a package is bytes that move between systems, and a list of several kinds is not a list. It closes the set of classifications, and it says a data set that fits none is a finding to report. This set fits none, so the BFF keeps a short hand-written catalogue and states in its comments that the catalogue is a screen choice.
Two answers are open. One adds a classification for a set that is grouped for presentation or transport and has no atomicity. The other keeps each case as several lists and accepts the small catalogue. Other screens and exports probably meet the same question, so the decision should come before the next one is built.
3. References
- Data classifications: entity, list, family, bundle, package and artefact
- The bundle and package catalogue
- task: the BFF family list task in the conventions story.