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

Bidder eligibility criteria #35

Closed
practicalparticipation opened this issue Sep 1, 2014 · 6 comments
Closed

Bidder eligibility criteria #35

practicalparticipation opened this issue Sep 1, 2014 · 6 comments
Assignees
Labels
Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues
Milestone

Comments

@practicalparticipation
Copy link
Contributor

practicalparticipation commented Sep 1, 2014

Requirement generated from User Research process: R17

There is user demand for fields which would indicate the eligibility criteria in order to be able to bid for a tender.

This requirement was articulated in the context of anti-corruption use-cases, where those involved with contract scrutiny are interested in understanding the complexity of tender requirements as a means of assessing whether particular barriers to bidding are being put in place.

They suggest analysis may look at "Length of eligibility criteria: character length of text defining which bidders are eligible to bid;".

As yet, requirements from firms for structured data on this have not been identified.

@birdsarah birdsarah added this to the Release prototype (1.0) milestone Oct 1, 2014
@birdsarah birdsarah added the Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues label Oct 1, 2014
@birdsarah
Copy link
Contributor

I believe this could be handled by submissionDetails for now. I am marking this as a documentation issue for the 1.0 release, and then a more detailed proposal can be submitted by a working group if its insufficient moving forward.

@LindseyAM
Copy link

@practicalparticipation i think this was also brought up by mihaly today

@practicalparticipation
Copy link
Contributor Author

Related to #139

@practicalparticipation practicalparticipation modified the milestones: After 1.0, Release candidate (1.0) Nov 10, 2014
@practicalparticipation
Copy link
Contributor Author

I've also added an eligibilityCriteria document to the documentType list.

Re-opening this against post 1.0.

@jpmckinney jpmckinney assigned jpmckinney and unassigned jpmckinney Nov 19, 2014
@timgdavies timgdavies modified the milestones: Version 1.1, After 1.0 May 16, 2016
@timgdavies
Copy link
Contributor

Version 1.0 of the standard has an eligibilityCriteria field which is a free text field for describing the eligibility of bidders. This meets the original use-case from the standard for checking the length of eligibility criteria descriptions.

I've been looking through issues, and thinking over cases we've encountered, to find any other requirements for structured eligibility criteria date.

The only two things I can think of are:

(1) Cases where only bidders on a given framework are eligible to bid;

(2) Cases where only national firms are eligible to bid (I seem to recall an issue on this from procurement analytics, but can't find this right now)

I suspect these are best handled as their own issues, so propose creating new issues for frameworks, and national-only eligibility issues, and closing this one.

@timgdavies
Copy link
Contributor

Frameworks handling is addressed in #310.

The proposed features extension in #223 will also allow criteria of bidders, such as 'national bidder only' to be captured in a structured form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues
Projects
None yet
Development

No branches or pull requests

6 participants