IDS Coverage notebook - Update logic for cases where all OC4IDS fields need not be present

[neelima-j]

The current IDS coverage check is strict for elements that map to multiple OC4IDS fields - It currently mandates that all possible fields for a given element be present in an OC4IDS project to be considered a match.

For example, the Address IDS element is mapped as follows:

IDS element	Coverage	Field Coverage
Contact details	0.00	parties: 100% parties/id: 100% parties/roles: 100% parties/address: 100% parties/address/streetAddress: 100% parties/address/locality: 100% parties/address/region: 100% parties/address/postalCode: 0% parties/address/countryName: 100% parties/contactPoint: 100% parties/contactPoint/email: 100%

Here, the postcode field is absent, and the overall coverage is calculated as 0%. This could be down to regional preferences, and coverage can be counted as 100%, due to the presence of the other address fields.

Tasks:

• Identify all instances where an IDS element is mapped to multiple OC4IDS fields and the coverage check uses an incorrect "AND" logic.
• Update the logic for these instances to use a more appropriate "OR" condition, where the check passes if at least one of the mapped OC4IDS fields is present.

[neelima-j]

Sample IDS Coverage report with notes to identify where logic needs to be changed