separating how-do-i's for python, r, opendap

[jules32]

Coworking with @cassienickles @ScienceCat18 @stefaniebutland

To prep for transition to "Repo B" with only .ipynb python how-tos.

We're restructuring the How-To's in a small structural way with several benefits:

• separate files so that .ipynbs (to start) can be in Repo B for the Hub
• only files for languages we have (no more "coming soon" because can lose trust when that lingers)

Next steps for Julie:

• [x] convert python .qmds to .ipynbs

[jules32]

I've converted and pushed .ipynb files (quarto convert access-cloud-python.qmd and quarto convert access-local-python.qmd) - we were doing this correct live I just needed to wait another moment before viewing!

Next steps before coworking and merging

• [ ] rework read data in this same way https://nasa-openscapes.github.io/earthdata-cloud-cookbook/how-tos/read_data.html (@stefaniebutland )
• [ ] rework subset data in this same way https://nasa-openscapes.github.io/earthdata-cloud-cookbook/how-tos/subset.html (@stefaniebutland )

Next coworking

Next coworking: review folders and delete old stuff

• [ ] https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/tree/main/how-tos/working-with-data-in-cloud
• [ ] https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/tree/main/examples

Something to consider in next coworking - keeping navbar on one line but including "data" in the access sections?

[jules32]

• [x] find-python.ipynb @cassienickles will find a new working example

Note from Michele:

I think the granules needs this: for g in granules: print(g.data_links(access="external"))

[jules32]

Next steps for https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/tree/main/examples:

Michele: Back up and think about options we need to cover for users. Look for themes - kerchunk

Slack specific DAACs and ask if there's anything in there that needs to be kept or if we can delete.