-
In the same way that the built docs include a translated version of the core CoST IDS mapping CSV files, it would be helpful to build a translated version of `sustainability.yaml`, for use in the upda…
-
Users prefer specific examples. We now have many specific examples on deeper pages (e.g. for the Map step).
However, much of the older content still has generic/abstract examples – or no examples.
…
-
Також в мешап потрібно буде додати пояснення - перше стосується таблиці, друге стосується стовпчикового графіку
- Показник "Наповнення" у таблиці розраховується як частка заповнених секцій проєкту…
-
I've started a review but only got about 1/3 of the way through the example, I'm putting my comments so far in this issue so that they aren't lost.
General comments:
* Use sentence case in headi…
-
Building on #6, what open standards could we fit our data into? Recognizing there may be some (or many) gaps, are there still formats that are worth trying to massage our data to fit? [The wiki](https…
-
As mentioned in https://github.com/open-contracting/standard/issues/319 there's some demand for a web API people can interact with programatically to get the same information Cove currently provides i…
-
Great minds and all that.
I was actually working to stand something similar up within http://github.com/government, e.g., `/governemnt/procurement` to serve as a shared resource for contracting langu…
-
E.g. to say that the indicators require certain fields to exist and you can use this command to check what red flags are possible to calculate.
-
See docs: https://ocds-merge.readthedocs.io/en/latest/handle-bad-data.html
The user should be able to add options for how the compile-releases step behaves. (see #222)
-
The schema contains some classes (definitions) that are only used in one place, e.g. `FibreTypeDetails`.
If we inline these definitions as nested properties that will reduce the length of the referen…