Mapping of eForms fields BT-509-Organization-Company, BT-500-Organization-TouchPoint and BT-509-Organization-TouchPoint

[csnyulas]

The following eForms fields do not have direct correspondence in ePO (and therefore cannot be mapped to ePO 4.0.0):

• BT-509-Organization-Company (Organisation eDelivery Gateway)
• BT-500-Organization-TouchPoint (Name)
• BT-509-Organization-TouchPoint (eDelivery Gateway)

This is primarily due to the fact that eForms provide information about organizations, and their various touchpoints separately from any given use case (in a part of the XML that where all organizations-related information is encoded), while in ePO all available information about organizations are contextualized to some role(s) that that organization plays, represented by the "epo:AgentInRole" class.

[andreea-pasare]

As of ePO 5.0.0, the following mappings are available:

• BT-509-Organization-Company - use epo:exposesChannel at the level of an org:Organization
• BT-500-Organization-TouchPoint - use dct:title at the level of an org:OrganizationalUnit
• BT-509-Organization-TouchPoint - use epo:exposesChannel at the level of an org:OrganizationalUnit

Note that a TouchPoint is an unit/department of an Organization and not the same as a Contact Point. Both the Organization and the TouchPoint can have ContactPoint data. The main Organization will have a Contact Point (epo:hasPrimaryContactPoint), while the TouchPoints may have Contact Point at the level of the Role played (epo:hasContactPointInRole)