Skip to main content

Blue Core Graph Toolbox

Web Application for loading and manipulating Blue Core RDF.

The Toolbox is being rebuilt as an Airflow 3 plugin that runs inside Blue Core Workflows. Until its screens are moved over, the original PyScript site lives alongside it in this repo.

Through Pyscript, the rdflib Python package is used for loading RDF through Blue Core.

Existing and Planned Functionality

  • Run SPARQL queries on one or more Blue Core Resources
  • Download RDF in various serializations like Turtle, XML/RDF, and json-ld
  • Chat with Blue Core AI Agents
  • Import and convert MARC to Blue Core BIBFRAME Resources
  • Export Blue Core Constrained Bound Descriptions (CBD) to MARC21 records

Running as an Airflow plugin

The bluecore_graph_toolbox package registers itself with Airflow through the airflow.plugins entry point, so installing it into the Airflow environment is all that's needed; nothing goes in the plugins folder. Shared helpers, the base template and styles come from bluecore-airflow-common.

Requires Python 3.12 and Airflow 3.2 or later (tested against 3.3.2).

Releases are published to PyPI as bluecore-graph-toolbox

uv build
uv add bluecore-graph-toolbox

In bluecore-workflows, add the pin to dependencies in its pyproject.toml and run uv lock; the Docker image installs it from the lockfile, so no wheel is copied in. When a new Toolbox release adds screens or API routes, bump that pin and uv lock again in a Workflows pull request.

Once installed, a Toolbox item appears in the Airflow navigation. The UI shows it in an iframe at /plugin/graph-toolbox; the app itself is mounted at /graph-toolbox:

Route Sign-in Purpose
GET /graph-toolbox/ required Landing page
GET /graph-toolbox/health none {"status", "version"}
/graph-toolbox/static/… none Toolbox and shared Blue Core assets

Sign-in is Airflow's own: the page uses Airflow's JWT cookie (Keycloak in a Blue Core stack), and the Toolbox has no login of its own.

All URLs follow [api] base_url, so the same build works with Airflow at the root or proxied under a path such as /workflows (AIRFLOW__API__BASE_URL=http://localhost/workflows), where the routes above become /workflows/graph-toolbox/….

Development

uv sync
uv run ruff check src/bluecore_graph_toolbox tests
uv run pytest

Releasing

Releases go to PyPI from .github/workflows/python-publish.yml using trusted publishing, so no API token is stored in the repo.

  1. Bump version in pyproject.toml (uv version --bump minor, say) and merge it to main.
  2. Create a GitHub release whose tag is v plus that version, e.g. v2.1.0.
  3. Publishing the release runs the workflow: it checks the tag against pyproject.toml, runs the tests, builds the wheel and sdist, checks that the wheel installs as an Airflow plugin, and uploads both to PyPI. Approve the pypi environment deployment if it asks.
  4. Bump the pin in bluecore-workflows as described above.

Metadata

Release files for bluecore-graph-toolbox 2.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bluecore-graph-toolbox 2.0.0
File Size Uploaded Provenance Actions
bluecore_graph_toolbox-2.0.0.tar.gz 11.1 kB With provenance Details for bluecore_graph_toolbox-2.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bluecore-graph-toolbox 2.0.0
File Interpreter ABI Platform Actions
bluecore_graph_toolbox-2.0.0-py3-none-any.whl Python 3 none any Details for bluecore_graph_toolbox-2.0.0-py3-none-any.whl

Total release size: 23.1 kB

Release files / bluecore_graph_toolbox-2.0.0.tar.gz

Download URL bluecore_graph_toolbox-2.0.0.tar.gz
Size 11.1 kB
Tags Source
SHA-256 checksum
How to use checksums
40c21594f649a172f0880918ef823413a77d67e07f2c898b9c7a6a6999e96fb3
BLAKE2b-256 checksum
How to use checksums
877af8d0f8458678e029de3647c81b86d9ca2920ef399033e9d2fbba29b67cb5
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 30, 2026.

Transparency log

Release files / bluecore_graph_toolbox-2.0.0-py3-none-any.whl

Download URL bluecore_graph_toolbox-2.0.0-py3-none-any.whl
Size 12.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5c244d29f61b01b22162770d04af07c601ff307bf92c43f94a9a61195349bad0
BLAKE2b-256 checksum
How to use checksums
54666672486ca412ccd848f17dfa027600d667da32d59f9a717adb266cd0b9fc
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 30, 2026.

Transparency log

Security for bluecore-graph-toolbox 2.0.0

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for bluecore_graph_toolbox-2.0.0.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 30, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

2.0.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page