-
Notifications
You must be signed in to change notification settings - Fork 46
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
itemClassificationScheme: Add support for non-item contexts #982
Labels
Codelist: Open
Relating to an open codelist
Milestone
Comments
The change to the codelist was removed from #990, as this needs to be merged to 1.1.5-dev instead of directly to 1.1-dev, as it changes normative content. Attaching the patch. |
Relevant comments from #711 #711 (comment) (copied to issue description) |
Closed by #1033 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
Classification
block presently has an open itemClassificationScheme.csv codelist for itsscheme
field. This, of course, only makes sense when theClassification
block is used in the context of items. (The definition of thescheme
field has "… For line item classifications, this uses the open itemClassificationScheme codelist.")The
Classification
block was intended to be used in other contexts, but it only anticipated needing a codelist in the context of items.I think the solution here is to do something similar to the
documentType
codelist. That list is used forDocument
blocks in the context oftender
,awards
, etc. However, some document types only make sense in specific contexts (as noted by that codelist's Section column).So, for 1.1.5, I would propose adding a
Context
(or similar) column toitemClassificationScheme.csv
, and then add schemes for organization classifications.Then, in 1.2.0, we can rename
itemClassificationScheme.csv
toclassificationScheme.csv
. (Technically, this is allowed in 1.1.5, but I prefer to do it in a minor release in case anyone hard-coded the filename of the CSV.)Split from #711
The text was updated successfully, but these errors were encountered: