openbis-parser-example
Example parser for openBIS using the bam-masterdata parser interface.
This repository can be used as a template for creating new parsers that can be used with the openbis-upload-helper.
1. Create a new parser repository
You can either fork this repository or use it as a template.
Click Use this template and choose Create a new repository:
Choose:
- the organization or profile where the repository will be created;
- a repository name;
- a short description;
- the desired visibility.
At BAM, parsers are typically hosted under the BAMresearch organization.
2. Define your parser
Clone your new repository:
git clone https://github.com/BAMresearch/<repository-name>.git
Note: The examples below use this repository's current package name, openbis_parser_example. Replace it with your own repository name where needed.
The repository has the following structure:
openbis-parser-example
├── LICENSE
├── pyproject.toml
├── README.md
├── src
│ ├── openbis_parser_example
│ ├── __init__.py
│ ├── parser.py
│ └── _version.py
└── tests
├── __init__.py
├── conftest.py
└── test_parser.py
To create your parser:
- Define your parser class in
src/<package-name>/parser.py. The class must inherit from thebam-masterdataparser interface,AbstractParser. - Expose the parser in
src/<package-name>/__init__.py:
from .parser import MyParser
my_parser_entry_point = {
"name": "My Parser",
"description": "Description of the parser.",
"parser_class": MyParser,
}
- Register the parser in
pyproject.toml:
[project.entry-points."bam.parsers"]
my_parser = "<package-name>:my_parser_entry_point"
- Update the remaining package-specific values in
pyproject.toml, such as the project name, package paths, URLs, andsetuptools-scmconfiguration.
3. Implement and test the parser
Implement the parsing logic in:
src/<package-name>/parser.py
Add or update tests in:
tests/test_parser.py
The parser should transform the source files into bam-masterdata objects that can later be written to openBIS.
4. Use the parser with openbis-upload-helper
Once the parser is developed, tested, and released as a Python package, it can be included as a dependency of the openbis-upload-helper.
openbis-upload-helper automatically discovers installed parsers registered under the bam.parsers entry-point group.
If the parser should be included in the distributed application, contact the openbis-upload-helper maintainers and provide the parser repository and released package version.
Metadata
Release files for openbis-parser-example 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 | Actions |
|---|---|---|---|---|
| openbis_parser_example-1.0.1.tar.gz | 64.5 kB | With provenance | Details for openbis_parser_example-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openbis_parser_example-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for openbis_parser_example-1.0.1-py3-none-any.whl |
Total release size: 77.0 kB
Release files / openbis_parser_example-1.0.1.tar.gz
| Download URL | openbis_parser_example-1.0.1.tar.gz |
|---|---|
| Size | 64.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75a1384df3f658c3ab2be285e70b8a64c4ce50b965327a5b5a6961ee44e1c52c
|
|
BLAKE2b-256 checksum How to use checksums |
022e465937373577c45866c0829383ffdcea015d2e01abfe6bc8a250017f3cfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logRelease files / openbis_parser_example-1.0.1-py3-none-any.whl
| Download URL | openbis_parser_example-1.0.1-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8bdd63d91bbbe0ba4b2b1175cca0a65c54dbf5ff793f536dc894773c8101f51
|
|
BLAKE2b-256 checksum How to use checksums |
adae0306521a5987f47d22b9019200ba33a5e716ba5ffeb5fbdbe41ff46f0ffd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logSecurity for openbis-parser-example 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for openbis_parser_example-1.0.1.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 22, 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.