Added a test to handle DIF10 records from NPI #236
Merged
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.
NPI releases DIF10 records with an appearance like:
'''
<Metadata_Dates>
<Metadata_Creation>2023-12-04T17:11:12Z</Metadata_Creation>
<Metadata_Last_Revision>Not provided</Metadata_Last_Revision>
<Data_Creation>Not provided</Data_Creation>
<Data_Last_Revision>Not provided</Data_Last_Revision>
</Metadata_Dates>
'''
This cause issues on ingestion side for MMD records which have dates of type "Not provided". A hack to prevent such strings to pass through has been added. Full datetime validation would be easier with XSLT 2, but for now we are using XSLT 1.