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

README.md: add guidance on expressions of interest #54

Merged
merged 30 commits into from
Apr 12, 2024

Conversation

odscjen
Copy link
Contributor

@odscjen odscjen commented Dec 4, 2023

@jpmckinney jpmckinney changed the title README.md: add guidance on using extension for pre-qual responses. README.md: add guidance on expressions of interest Jan 30, 2024
Copy link
Member

@duncandewhurst duncandewhurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that we should pause this PR until the points discussed in open-contracting/ocds-extensions#41 are settled (whether to add a discriminator field, whether to rename Bid to Response etc.) as that will likely impact the content of the documentation and examples.

README.md Outdated Show resolved Hide resolved
@jpmckinney
Copy link
Member

I think that we should pause this PR until the points discussed in open-contracting/ocds-extensions#41 are settled

I'll follow up - thanks for the reminder.

@jpmckinney
Copy link
Member

whether to add a discriminator field, whether to rename Bid to Response etc.

Let's add a discriminator field and do the renaming, but we can discuss details in open-contracting/ocds-extensions#41

Copy link
Member

@jpmckinney jpmckinney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to also modify the title and description of the Bid definition.

It would be difficult to modify its machine-name to Submission, as other extensions modify the Bid definition (requirements, subcontracting).

Edit:

Schema

Need to add "expression of interest" wording to bids (reword as "Information about ..." and copy the wording of the extension metadata), Bids (and fields), Bid fields, etc. Can maybe consider "submission" to reduce wordiness. Please address style guide issues like "An array of" while making edits.

bidStatus

Need to probably also modify bidStatus to use "bid or expression of interest". Noting that "evaluated" can be used both in the context of qualification criteria and award criteria, e.g. from UNCITRAL:

The procuring entity shall evaluate the qualifications of suppliers or con- tractors in accordance with the qualification criteria and procedures set out in the pre-qualification or pre-selection documents

That said, we probably need to remove "in order to be evaluated" as that's being used to mean "against award criteria" which isn't the case for EOIs.

We can also update "requirements" to "criteria".

statistic

For consistency, in statistic.csv, we should change requests to participate to expressions of interest. We can leave the requests code as-is as it has been present since the first version.

Change the Category for requests to expressionsOfInterest

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
- bids array is not only for received submissions (e.g. can be invited)
- Merge related paragraphs
@odscjen
Copy link
Contributor Author

odscjen commented Apr 9, 2024

@jpmckinney Re. statistic should we also add new codes to disclose the results of the evaluation of the EOIs? So:

  • 'validExpressionsOfInterest'
  • 'disqualifiedExpressionsOfInterest'

@jpmckinney
Copy link
Member

disclose the results of the evaluation of the EOIs

If we didn’t need such codes for eForms, then I think no jurisdiction tracks such statistics.

@odscjen odscjen requested a review from jpmckinney April 10, 2024 09:34
Copy link
Member

@jpmckinney jpmckinney left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made some other changes. Ready to merge.

@odscjen odscjen merged commit bc64015 into master Apr 12, 2024
3 checks passed
@odscjen odscjen deleted the 41_pre-qual_guidance branch April 12, 2024 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bids: Adapt documentation to cover e.g. requests to participate
3 participants