girder-ess-dive
Plugin implementing ESS-DIVE assetstore in Girder
Install
Through PyPI:
pip install girder-ess-dive
Locally:
git clone https://github.com/girder/girder-ess-dive.git
cd girder-ess-dive
pip install .
Usage
Use Swagger API to use the plugin
Create a new ESSDIVE Assetstore
POST /essdive_assetstores
Params:
name - Name of the Assetstore
url - The base URL for the ESS-DIVE
Import existing data into an assetstore.
Before you do this you will need to do the following in the Girder Web UI:
- Set the current Girder Assetstore to ESS-DIVE Assetstore
- Create a Collection
- Create a folder to import a dataset into
POST /assetstore/{id}/import
Params
id - The Assetstore ID of the ESS-DIVE Assetstore
importPath - the ESS-DIVE dataset ID to import
destinationId - ID of a folder, collection, or user in Girder under which the data will be imported.
destinationType - Type of the destination resource (Must be set to "Folder).
Downloading data
Browse to your collection. Data should appear there and can be clicked on to download
Metadata
Release files for girder-ess-dive 1.0.1
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 | |
|---|---|---|---|---|
| girder-ess-dive-1.0.1.tar.gz | 5.7 kB | Without provenance | Details |
Release files / girder-ess-dive-1.0.1.tar.gz
| Download URL | girder-ess-dive-1.0.1.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96938372212dee4deab71cfe863a92f477ff6414fb1c68bb7db85e1602a1d96c
|
|
BLAKE2b-256 checksum How to use checksums |
53e490ceaca9c98e3e9614924283c2dfdb46abbb9acdd2592afdb287866834e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.8.0 tqdm/4.42.0 CPython/3.5.9
|
Security for girder-ess-dive 1.0.1
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.