CKAN BAE Publisher
CKAN extension that allows users to publish datasets in the FIWARE Business API Ecosystem GE as offerings in an easy way. To do so, a new tab is added in the Datasets Manage menu that offers a form to set the basic options of the offering.
Offerings are not automatically published so the dataset creator must access this form and complete it in order to publish the dataset using the FIWARE Business API Ecosystem.
Note: This software is intended to integrate a CKAN instance with the FIWARE Business API Ecosystem and it won't work with other Marketplaces/Stores.
Requirements
- A CKAN instance able to connect to the FIWARE Business API Ecosystem via HTTP(s)
- FIWARE/TMF Business API Ecosystem v5.4.0 or higher
- OAuth2 CKAN Extension. This extension is needed since the requests sent to the BAE must include the OAuth2 credentials to identify the user that is creating the offering.
- CKAN Private Dataset Extension
Installation
Install this extension in your CKAN instance is as easy as intall any other CKAN extension.
- Activate your virtual environment (generally by running
. /usr/lib/ckan/default/bin/activate) - Install the extension by running
pip install ckanext-baepublisher - Modify your configuration file (generally in
/etc/ckan/default/production.ini) and addbaepublisherin theckan.pluginssetting. - In the same config file, specify the location of FIWARE BAE to use by adding the
ckan.baepublisher.store_urlsetting. - Restart your apache2 reserver (
sudo service apache2 restart) - That's All!
Tests
This sofware contains a set of test to detect errors and failures. You can run this tests by running the following command:
nosetests --ckan --with-pylons=test.ini ckanext/baepublisher/tests/
Note: The test.ini file contains a link to the CKAN test-core.ini file. You will need to change that link to the real path of the file in your system (generally /usr/lib/ckan/default/src/ckan/test-core.ini).
You can also generate coverage reports by running:
nosetests --ckan --with-xunit --with-pylons=test.ini ckanext/baepublisher/tests/ --with-coverage --cover-package=ckanext.baepublisher --cover-inclusive --cover-erase . --cover-xml
Release files for ckanext-baepublisher 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ckanext_baepublisher-0.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for ckanext_baepublisher-0.5-py2.py3-none-any.whl |
Release files / ckanext_baepublisher-0.5-py2.py3-none-any.whl
| Download URL | ckanext_baepublisher-0.5-py2.py3-none-any.whl |
|---|---|
| Size | 39.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4d2e5f9801eb80b83c7ef4b3c6e10a087618776e8784213af7fa77c8b4c0f87a
|
|
BLAKE2b-256 checksum How to use checksums |
3c351a687e7685197ca524234544d8be8f9c3ef63c2ad4ed8b3a9b36f01e2abc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ckanext-baepublisher 0.5
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.
