hsclient
A python client for interacting with HydroShare in an object oriented way. The hsclient Python package can be use to create, modify, and interact with HydroShare resources. It was designed to allow you to write code to do pretty much everything you can do through HydroShare's web user interface.
Jupyter Notebooks
HydroShare has a resource with example Jupyter notebooks for using hsclient. Click here then click the blue Open with... dropdown at the top of the page and select Cuahsi Jupyterhub to launch the notebooks into HydroShare's linked Jupyter Environment. Click here for information on how to access the HydroShare linked JupyterHub environment.
Install the hsclient HydroShare Python Client
The hsclient package is installed already in HydroShare's linked JupyterHub Python environment. However, if you want to use hsclient outside of that Python environment, hsclient won't be installed by default. You'll need to install it before you can work with it. Use the following command to pip install hsclient from the Python Package Index (PyPI). You can also use the package manager for your interactive development environment to do this.
pip install hsclient
Getting Started and Documentation
The following are quick examples of how to get started with hsclient. Refer to the Jupyter notebooks above for more extensive examples. Click here to access documentation for hsclient.
Authenticate with HydroShare
Before you start interacting with resources in HydroShare you will need to authenticate.
from hsclient import HydroShare
hs = HydroShare()
hs.sign_in()
Create a New Empty Resource
A "resource" is a container for your content in HydroShare. Think of it as a "working directory" into which you are going to organize the code and/or data you are using and want to share. The following code can be used to create a new, empty resource within which you can create content and metadata.
This code creates a new resource in HydroShare. It also creates an in-memory object representation of that resource in your local environmment that you can then manipulate with further code.
# Create the new, empty resource
new_resource = hs.create()
# Get the HydroShare identifier for the new resource
resIdentifier = new_resource.resource_id
print('The HydroShare Identifier for your new resource is: ' + resIdentifier)
# Construct a hyperlink for the new resource
print('Your new resource is available at: ' + new_resource.metadata.url)
Creating and Editing Resource Metadata Elements
Editing metadata elements for a resource can be done in an object oriented way. You can specify all of the metadata elements in code, which will set their values in memory in your local environment. Values of metadata elements can be edited, removed, or replaced by setting them to a new value, appending new values (in the case where the metadata element accepts a list), or by removing the value entirely.
When you are ready to save edits to metadata elements from your local environment to the resource in HydroShare, you can call the save() function on your resource and all of the new metadata values you created/edited will be saved to the resource in HydroShare.
Resource Title and Abstract
The Title and Abstract metadata elements can be specified as text strings. To modify the Title or Abstract after it has been set, just set them to a different value.
# Set the Title for the resource
new_resource.metadata.title = 'Resource for Testing the HS RDF HydroShare Python Client'
# Set the Abstract text for the resource
new_resource.metadata.abstract = (
'This resource was created as a demonstration of using the HS RDF '
'Python Client for HydroShare. Once you have completed all of the '
'steps in this notebook, you will have a fully populated HydroShare '
'Resource.'
)
# Call the save function to save the metadata edits to HydroShare
new_resource.save()
# Print the title just added to the resource
print('Title: ' + new_resource.metadata.title)
print('Abstract: ' + new_resource.metadata.abstract)
Funding and Acknowledgements
This material is based upon work supported by the National Science Foundation (NSF) under awards 1931278 and 1931297. Any opinions, findings, conclusions, or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of the NSF.
Metadata
Release files for hsclient 1.1.9
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 | |
|---|---|---|---|---|
| hsclient-1.1.9.tar.gz | 30.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hsclient-1.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.8 kB
Release files / hsclient-1.1.9.tar.gz
| Download URL | hsclient-1.1.9.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bc1d8246ad98a8856d4e03995b113fec6830f09b4dda07ebb05908a6663cd41
|
|
BLAKE2b-256 checksum How to use checksums |
f714cf30fa3597cc139dbb011838622c9aeece3d64561f2b05b9536c197f63cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / hsclient-1.1.9-py3-none-any.whl
| Download URL | hsclient-1.1.9-py3-none-any.whl |
|---|---|
| Size | 20.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc52d8571d9c9c293893123549267f5f916a22792684c8dedc73ec6f0d39b7b8
|
|
BLAKE2b-256 checksum How to use checksums |
982bdfa4a775dccc83017b6a6eb8b0c2dc582942a2c65212eb0595f1edb20d69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for hsclient 1.1.9
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for hsclient-1.1.9.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA 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.