Is there a field that links a ReviewDecision to a ReviewRequest

[csnyulas]

As described in https://github.com/OP-TED/ePO/issues/777 the ePO ontology defines a mandatory property that links every epo:ReviewDecision instance to one epo:ReviewRequest instance, with the meaning that the given decision "resolves" or "answers" the request. Is there a field defined in the eForms SDK that provides this information? Should it be perhaps an "id-ref" typed field that refers to a value defined in the BT-804-Review field, which is of "id" type?

Note: Although the SDK provides the field BT-785-Review ("Review Previous Identifier"), that is used to instantiate the epo:refersToPreviousReview relationship (in ePO 4.0.0, or epo:refersToPrevious in ePPO 5.0.0), not this special, mandatory, relationship between a epo:ReviewDecision and a epo:ReviewRequest.

[pdonohoe]

Yes there is - BT-785-Review "Review Previous Identifier". This is optional in the eForms schema ( see https://docs.ted.europa.eu/eforms/latest/schema/all-in-one.html#reviewSection ), and "EM" in the DG GROW Guide (see https://code.europa.eu/eproc/eforms/docs/-/blob/main/guides/gde_005_rew.md).

"EM" is short for "Exists Mandatory" which means that if the item exists, then it is mandatory. But this is the responsibility of the Buyer/Reviewer, and we (OP/eForms) don't have access to their files, so "Exists Mandatory" translates to "Optional" for us.

[csnyulas]

I would like to reopen this issue (but I don't have the rights), to have a few things confirmed/clarified.

According to ePO 4.0.0 model

as I mentioned in the Note at the end of this issue description (see above), we map the field BT-785-Review ("Review Previous Identifier") to the epo:refersToPreviousReview property. This provides a quite generic mechanism that can work for describing Review objects (requests or decision) that are defined in this or in other (previously published) notices.

@pdonohoe are you suggesting that in certain cases (in addition to the epo:refersToPreviousReview property) we should also create the epo:resolvesReviewRequest relationship between the epo:ReviewDecision and epo:ReviewRequest instances from the same BT-785-Review field value? What are these cases when we need to and can do this? Is the value of the BT-785-Review field always something that represent a review object that is present in this notice? Are those values technical ids that uniquely refer to another element in this notice?

CC: @andreea-pasare

[pdonohoe]

Hi Csongor,

BT-785-Review can refer to another review object in the same notice, or in another notice. It is not a technical ID, it is supplied by the Buyer/Reviewer. We don't have any validation on this ID. We also can't check if a review object with that ID actually exists, or what type of review it is. So you can't create an epo:resolvesReviewRequest object.