Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange nesting of BT-761 and BT-76? #1063

Open
mdewinne opened this issue Nov 12, 2024 · 1 comment
Open

Strange nesting of BT-761 and BT-76? #1063

mdewinne opened this issue Nov 12, 2024 · 1 comment
Assignees
Labels
notice-types Related to the notice type definitions (/notice-types).

Comments

@mdewinne
Copy link

Is there a specific reason why in multiple notice types (e.g. 16, 17) the fields BT-761 (Tenderer Legal Form) and BT-76 (Tenderer Legal Form Description) are nested under GR-Lot-TendererQualification, which also holds BT-771 (Late Tenderer Information) and BT-772 (Late Tenderer Information Description)?

In fields.json, they belong to different nodes (ND-TendererLegalForm and ND-LateTendererInformation respectively, both children of ND-LotTenderingTerms)

And since GR-Lot-TendererQualification is translated / labeled as "Information about late submission", BT-761 and BT-76 seem a bit out of place:
image

Or it is just a matter of finding a better label for GR-Lot-TendererQualification?

@encampaen
Copy link

Dear @mdewinne, originally the label was different, but the fact remains right now it's not correct. We can either create separate groups for the legal form and late submission, or find a different label. We will address it in the next SDK version

@YvesJo YvesJo added the notice-types Related to the notice type definitions (/notice-types). label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notice-types Related to the notice type definitions (/notice-types).
Projects
None yet
Development

No branches or pull requests

3 participants