Problem Description
We were able to get the actual XSD used for Doctor's Declarations.
Many mappers to not handle "null" elements well and result in NPEs (NullPointerException).
This ticket should also be the opportunity to adapt the mappers to be lenient enough to support values for all optional fields in XSD.
Proposed Change
Use the actual XSD for Doctor's Declarations for all supported diseases:
- Identify missing fields (not present in the retro-engineered XSD)
- Add mapping into SORMAS for those fields
- Used the more constraint types (instead of string)
Added Value/Benefit
Robustness / more data mapped into SORMAS
Acceptance Criteria
- [ New XSD is used ]
- [ Types still pass ]
- [ New fields can be used ]
- [ New fields are mapped to SORMAS ]
Implementation Details
The XSD can be found on the Sharepoint: "Doctors Declaration" folder: "MS_MINF_MALADIES_INFECTIEUSES_1.8.xsd".
Check on optional fields in XSD and make sure current mappers support the absence of the field.
Add unit tests that cover nullable fields.
Mockups
No response
Additional Information
@XavCol this requires a bigger analysis. Maybe you want to contribute other points.
Problem Description
We were able to get the actual XSD used for Doctor's Declarations.
Many mappers to not handle "null" elements well and result in NPEs (NullPointerException).
This ticket should also be the opportunity to adapt the mappers to be lenient enough to support values for all optional fields in XSD.
Proposed Change
Use the actual XSD for Doctor's Declarations for all supported diseases:
Added Value/Benefit
Robustness / more data mapped into SORMAS
Acceptance Criteria
Implementation Details
The XSD can be found on the Sharepoint: "Doctors Declaration" folder: "MS_MINF_MALADIES_INFECTIEUSES_1.8.xsd".
Check on optional fields in XSD and make sure current mappers support the absence of the field.
Add unit tests that cover nullable fields.
Mockups
No response
Additional Information
@XavCol this requires a bigger analysis. Maybe you want to contribute other points.