Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

This document outlines feature pilots within various DataHubs. These pilots aim to provide tools for instructors to manage their conda environment, identify and fix accessibility issues and for admins to track the courses using a particular hub.

Current Pilots - Spring 2026

1. JupyterLab-a11y-checker Extension Pilot

Status: Ongoing

Description: JupyterLab-a11y-checker is a JupyterLab extension that performs accessibility checks on Jupyter Notebooks in DataHub, aiming to help authors align their notebooks with WCAG 2.0 AA guidelines. Notebook authors can identify accessibility issues in their notebooks and receive actionable suggestions to fix them.

Key Objectives:

Piloting Hubs:


Completed Pilots - Fall 2025

1. Shared-Conda-Environment

Status: Completed

Description: This pilot focused on implementing Shared-Conda-Environments across multiple hubs. Shared conda environments let instructors and TAs install custom packages and register new Jupyter kernels for their courses, without needing GitHub pull requests or waiting for the admins to deploy the new software.

Key Outcomes:

Piloted Hubs:

https://astro.datahub.berkeley.edu/

Documentation:

For more information on using shared conda environments, see the Shared Conda Environment workflow guide.


2. bCourses Based Authorization

Status: Completed

Description: This pilot restricted access to per-course hubs based on user’s affiliation with bCourses. Students/TAs/Teachers who are in the bCourses roster for authorized courses can access certain hubs.

Key Outcomes:

Piloted Hubs: