CKAN Budgets
A CKAN extension that improves handling of budget data in CKAN. Central to the budget data handling are budget data packages.
When a CSV file is uploaded to CKAN and the CSV includes all of the headers defined in the budget data package specification, the dataset is automatically converted into a budget data package (i.e. it can be exported as a budget data package). So automatically the budget data distribution is standardised and becomes usable in the different tools that support budget data packages.
Installation
This CKAN extension can be installed via pypi using pip:
pip install ckanext-budgets
If you have followed the CKAN installation documentation remember to activate your CKAN environment (virtual environment) before installing the extension:
. /usr/lib/ckan/default/bin/activate
Then add budgets to the list in ckan.plugins in your CKAN configuration file. Restart your webserver and budget data is automatically handled for you.
Configuration
ckan.budgets.specification - JSON schema file to describe the budget data package specification used.
ckan.budgets.countries - JSON object with country codes as keys and country names as values. Use this if you want to translate the country names into another language (default is English).
ckan.budgets.currencies - JSON object with currency code as keys and currency names as values. Use this if you want to translated the currency names into another language (default is English).
ckan.budgets.statuses - JSON object representing the different status of data with keys as proposed, approved, adjusted or executed) and with the English description of those statuses as values. Use this if you want to translate description into another language (status keys should remain intact).
ckan.budgets.default.country - Country code of a default country which is auto-selected.
ckan.budgets.default.currency - Currency code of a default currency which is auto-selected.
License
Copyright (C) 2014 Open Knowledge Foundation
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see http://www.gnu.org/licenses/.
1 maintainer
Metadata
1 maintainer
Release files for ckanext-budgets 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ckanext-budgets-0.3.2.tar.gz | 17.3 kB | Without provenance | Details for ckanext-budgets-0.3.2.tar.gz |
Release files / ckanext-budgets-0.3.2.tar.gz
| Download URL | ckanext-budgets-0.3.2.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1560268c74f968887a0f6c23a917187d7f5380976ab3245f21d8893a258b0ff5
|
|
BLAKE2b-256 checksum How to use checksums |
12d21fcb3a32a0033fbe19aa7688fbe6d7f7dbcbbb365288509f833c4edf621f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ckanext-budgets 0.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
