Python client for NGD Backend
A Python client package to operate with NGD-Backend
NGD Backend purpose is to manage and process Bar Code of Life information, applied to decision-making in conservation of biodiversity. It is a software system (a set of software components) developed as part of project "NEXTGENDEM" activities. BCS-Backend is the main component, an engine capable of managing bioinformatic information (import, export, visualization) and providing easy access to bioinformatic processes by filling parameters and submitting to available compute resources.
Getting started
Prerequisites
- Python >= 3.8
- An NGD backend instance has to be running and accessible. The URL of the API endpoint is the required parameter for the construction of the client. See the example in "Basic Usage" section below.
- An API Key to authenticate into the NGD Backend instance (go to the GUI of NGD and request and download an API Key file)
Installing
pip install ngd-biond
Basic Usage
from biond import Client
# Use "http://dev_balder_2_app_1/" as URL if from Jupyter Notebook at jupyter.nextgendem.eu
c = Client("http://localhost:5000/") # Construct client
c.check_backend_available()
c.login(
"api_key_file.txt") # Login, using API Key in a file (direct API key not supported to avoid unintended upload of API keys)
c.logout()
Package authors
- Rafael Nebot Medina. ITC-DCCT (Instituto Tecnológico de Canarias, SA - Departamento de Computación)
- Daniel Reyes Parrilla. ITC-DCCT
Nextgendem Platform
- Alejandro Curbelo Fontelos. ITC-DCCT
- Juli Caujapé Castells. JBCVC-UACSIC (Jardín Botánico Canario "Viera y Clavijo", Unidad asociada CSIC)
- Ruth Jaén Molina. JBCVC-UACSIC
- Antonio Díaz Pérez. Gesplan (Gestión y Planeamiento del territorio, SA)
- Isabel Saro Hernández. JBCVC-UACSIC
- Carlos Caraballo. ITC-DCCT
License
This project is licensed under the BSD-3 License - see the LICENSE file for details
Acknowledgements
The development of this software was carried out under project NEXTGENDEM (https://www.nextgendem.eu), funded by the Interreg MAC 2014-2020 Cooperation Programme with project code "MAC2/4.6d/236". This work reflects the authors' view only; the funding agencies are not responsible for any use that may be made of the information it contains.
Metadata
Release files for ngd-biond 0.3
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 |
|---|---|---|---|---|
| ngd-biond-0.3.tar.gz | 15.4 kB | Without provenance | Details for ngd-biond-0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ngd_biond-0.3-py3-none-any.whl | Python 3 | none | any | Details for ngd_biond-0.3-py3-none-any.whl |
Total release size: 35.7 kB
Release files / ngd-biond-0.3.tar.gz
| Download URL | ngd-biond-0.3.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa6492b08aba73e50b5e5d8d896404a5bc39292c5afb87d1aa3f89a8250dcc1a
|
|
BLAKE2b-256 checksum How to use checksums |
1f22a38857a53660b86ec15a6ba20bb417ebfd454feeb48e0c3ba397212a4ea1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.7.0 requests/2.24.0 setuptools/51.1.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.7.6
|
Release files / ngd_biond-0.3-py3-none-any.whl
| Download URL | ngd_biond-0.3-py3-none-any.whl |
|---|---|
| Size | 20.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0c018991b0241a77c29020041d9e9e538d4d76dc0686e2381937c97f4bc8363
|
|
BLAKE2b-256 checksum How to use checksums |
e6a3549c45e8f699f74b3146d610ef3f28b9625f0662fa6b03bcb24b1aefec62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.7.0 requests/2.24.0 setuptools/51.1.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.7.6
|
Security for ngd-biond 0.3
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.