As an SCBI-CT user, I want EAC-CPF metadata field post validator to not send failed message due to the slight variations in the datastream. The validation is failing because the legacy SCBI-CT route was using a velocity template to create the EAC-CPF datastream and it only included the project name in the identity section where as the new unified SCBI-CT route uses XSL template which includes both the project name and the ID to populate the field. For an example,

The old template would populates the field as "Sumaco Cloud Forest Project" and the new template populates the field as "Sumaco Cloud Forest Project (p157)"

1. validate which version of the template is the correct one to use from Beth
2. update the post validator to handle both cases by only checking the substring

– An example snippet from EAC-CPF datastream from velocity template that has only the project name –
<identity>
<entityType>corporateBody</entityType>
<nameEntry localType="primary">
<part>Okaloosa S.C.I.E.N.C.E. Project</part>
</nameEntry>
<nameEntry localType="abbreviation">
<part>Okaloosa S.C.I.E.N.C.E. Project</part>
</nameEntry>
</identity>

– An example snippet from EAC-CPF datastream from xsl template that has both the project name and ID –
<identity>
<entityType>corporateBody</entityType>
<nameEntry localType="primary">
<part>Sumaco Cloud Forest Project (p157)</part>
</nameEntry>
<nameEntry localType="abbreviation">
<part>p157</part>
</nameEntry>
</identity>