opensarlab_notifications

A JupyterLab frontend and backend extension for OpenSARLab that provides calendar notification popups within JupyterLab.

The extension needs to have access to the following environment variables within the JupyterLab server extension:

• OPENSARLAB_PROFILE_NAME: The name of the OSL user profile being used
• OPENSARLAB_LAB_SHORT_NAME: The short name of the lab deployment (as used by the OSL Portal)
• OPENSARLAB_PORTAL_DOMAIN: The schema+host domain of the OSL Portal (e.g., https://opensarlab.asf.alaska.edu)

The server extension part retrieves from the /notifications/{short_lab_name}?profile={profile_name} Portal service the calendar notifications in JSON format which then passes to toastr within the frontend extension for display.

Requirements

• JupyterLab >= 3.0

Install

To install the extension, execute:

pip install opensarlab_notifications

Uninstall

To remove the extension, execute:

pip uninstall opensarlab_notifications

Troubleshoot

If you are seeing the frontend extension, but it is not working, check that the server extension is enabled:

jupyter server extension list

If the server extension is installed and enabled, but you are not seeing the frontend extension, check the frontend extension is installed:

jupyter labextension list

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the opensarlab_notifications directory
# Install package in development mode
pip install -e .
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Server extension must be manually installed in develop mode
jupyter server extension enable opensarlab_notifications
# Rebuild extension Typescript source after making changes
jlpm run build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm run watch

# Run JupyterLab in another terminal
# To avoid polluting the parent environment, prepend the needed Environment Variables.
OPENSARLAB_PROFILE_NAME=opensarlab_profile_name \
    OPENSARLAB_LAB_SHORT_NAME=opensarlab_lab_short_name \
    OPENSARLAB_PORTAL_DOMAIN=opensarlab_portal_domain \
    jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm run build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

# Server extension must be manually disabled in develop mode
jupyter server extension disable opensarlab_notifications
pip uninstall opensarlab_notifications

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named opensarlab-notifications within that folder.

Packaging the extension

See RELEASE