...
| Code Block |
|---|
{
"Observation": {
"name": "observation",
"description": "test observation",
"primaryCtegory": "Observation",
"identifier": "do_1_observation",
"frameworkTemplate": [],
"ecm": [
"ecm1",
"ecm2",
"ecm3"
],
"children": [
{
"identifier": "do_1_question1",
"name": "question1",
"parent": "do_1_observation",
"domain": "domain1",
"criteria": "criteria1",
"pageNumber": 1,
"ecm": "ecm1" // ecm meta is optional
},
{
"identifier": "do_1_question2",
"name": "question2",
"parent": "do_1_observation",
"domain": "domain1",
"criteria": "criteria1",
"pageNumber": 2,
"ecm": "ecm2" // ecm meta is optional
}
]
}
} |
...
Pros:
This approach is simpler one as we are not changing the structure
...
because it provides required views with minimum computation.
creation of different needs to perform two operation: filter by metadata and group by pageNumber
this approach requires minimal changes in the platform.
Cons:
player need to understand
pageNumbermetadata.player need to perform two operation: filter by metadata and group by pageNumber
storing the forms is still not solved with this approach
Approach 2: FrameworkTemplate and View
...