Skip to content

Move "in-development" tutorials to PRs #421

Description

@ateucher

There are a number of tutorials that are sitting in the in-development folder. These should be in a PR and deleted from the in-development folder. The PR can be draft until someone is able to pick it up.

These are the in-development notebooks:

  - section: "In Development"
    href: in-development/index.qmd
    contents:
      - text: "Search & Download NSIDC Cloud"
        href: examples/NSIDC/ICESat2-CMR-OnPrem-vs-Cloud.ipynb
      - text: "Access NSIDC Cloud w/ CMR"
        href: examples/NSIDC/ICESat2-CMR-AWS-S3.ipynb
      - text: "Direct Access & Harmony Workflow"
        href: examples/Transform-workflow.ipynb
      - text: "Search & Access USGS Landsat Cloud" 
        href: examples/USGS_Landsat/Landsat_C2_Search_Access.ipynb
      - text: "Direct S3 Data Access: NetCDF - Daymet v4 Daily TMAX Example"
        href: examples/ORNL/Data_Access__Direct_S3_Access__ORNL_DAYMET.ipynb
      - text: "Access ECCO data via Harmony & the Zarr reformatter service"
        href: external/cof-zarr-reformat.ipynb
      - text: "zarr-eosdis-store example"
        href: external/zarr-eosdis-store.ipynb
      - section: "Example Workflows"
        href: examples/index.qmd
        contents: 
          - text: "GES DISC - MERRA2"
            href: examples/GESDISC/GESDISC_MERRA2_tavg1_2d_flx_Nx__Kerchunk.ipynb
          - text: "LP DAAC ECOSTRESS"
            href: examples/LPDAAC/LPDAAC_ECOSTRESS_LSTE__Kerchunk.ipynb
          - text: "PO.DAAC ECCO SSH"
            href: examples/PODAAC/PODAAC_ECCO_SSH__Kerchunk.ipynb
      - text: "`earthdata`: Python-R Handoff"
        href: in-development/earthdata-python-r-handoff.qmd  

Some of the tutorials are in the examples/ directory (which is not rendered on the site as a navigable directory), some reference notebooks in external/ (which is also not in the navigation). One ("earthdata: Python-R Handoff") is only in the in-development folder and it looks very dated (it references the earthdata python package instead of earthaccess as it is now named) and may warrant removal.

I think each one should be evaluated:

  1. Decide if it is a tutorial we want to keep.

If Yes:

  1. Open a PR that adds it in what will be its final destination (tutorials, how-tos, etc).
  2. Open a PR that deletes it from the in-development folder. Merge this PR immediately, leaving the in-dev tutorial as a PR only.

If No:

  • Open a PR deleting the tutorial itself, and its link in _quarto.yml

I've started by modifying #405 to have the destination be tutorials/ instead of in-development/.

@ronnyhdez what do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions