Bau metaschema #25
Closed
Bau metaschema #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Our application state must satisfy a number of different constraints: **QUESTION DATA** 1. It must be possible to know the exact questions & answers given 2. As questions evolve over time, we need to know which questions are getting at an underlying meaning so that we can use them to integrate to downstream systems (e.g. case management, risk engine, data analytics) 3. As multiple-selection *answers* evolve over time, we need to know what the options map to **JOURNEY DATA** 1. We need to know what application journey a user was going through (so we can handle their application correctly when we release a new version) 2. In the long run - when we support many application journeys - we will need to distinguish between the journeys themselves
|
|
This analysis has moved - closing this PR & deleting branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our application state must satisfy a number of different constraints:
QUESTION DATA
getting at an underlying meaning so that we can use them to integrate
to downstream systems (e.g. case management, risk engine, data
analytics)
what the options map to
JOURNEY DATA
we can handle their application correctly when we release a new
version)
need to distinguish between the journeys themselves