For some of the manual data tenders, the amount and the year was deduced from the context by the people who gathered the manual data.
Therefore, 2 new fields were added in the API response on [/networks/{networkID}/tenders/{tenderID}(https://api.defense.tenders.exposed/docs/#/network_tender/getNetworkTender) to mark these approximated tenders:
tender. xYearApproximated
tender. xAmountApproximated
❗️ This field will only appear for manual tenders. TED tenders will not have it at all so make sure you handle that case.
If it does occur and the value is true we should display a ⚠️ next to the amount and the year of the tender in the Contracts table (year will be added in #505):
When people click the question mark they should be able to see a tooltip saying:
This value was deduced from the context by our team. You can consult the source by clicking on the contract title.
zufanka
commented
4 years ago
For some of the manual data tenders, the amount and the year was deduced from the context by the people who gathered the manual data. Therefore, 2 new fields were added in the API response on [
/networks/{networkID}/tenders/{tenderID}(https://api.defense.tenders.exposed/docs/#/network_tender/getNetworkTender) to mark these approximated tenders:❗️ This field will only appear for manual tenders. TED tenders will not have it at all so make sure you handle that case.
If it does occur and the value is
truewe should display a ⚠️ next to the amount and the year of the tender in the Contracts table (yearwill be added in #505):When people click the question mark they should be able to see a tooltip saying:
This value was deduced from the context by our team. You can consult the source by clicking on the contract title.