intake-esm_require_all_on_usage

require_all_on.ipynb

By the way, I thought I would let you know that intake-esm now supports relative paths for the csv files. This will make it easy for other users to explore the catalog even when they don't have access to the data storage.

As example

{
  "esmcat_version": "0.1.0",
  "id": "mistral-cmip6",
  "description": "This is an ESM collection for CMIP6 data accessible on the DKRZ's MISTRAL disk storage system in /work/ik1017/CMIP6/data/CMIP6",
  "catalog_file": "/home/mpim/m300524/intake-esm-datastore/catalogs/mistral-cmip6.csv.gz",
...
}

becomes

{
  "esmcat_version": "0.1.0",
  "id": "mistral-cmip6",
  "description": "This is an ESM collection for CMIP6 data accessible on the DKRZ's MISTRAL disk storage system in /work/ik1017/CMIP6/data/CMIP6",
  "catalog_file": "mistral-cmip6.csv.gz",
...
}

So, If the json and the csv are in a GitHub repo, I can easily open both the json and csv without needing access to mistral. In earlier versions of intake-esm, this would have failed since I cannot access /home/mpim/m300524/intake-esm-datastore/catalogs/mistral-cmip6.csv.gz without access to the system.