"Collections and Granules" page with some "Glossary" things

[saberbrasher]

I created the page for "Collections and Granules". I also created a .qmd file for a "Glossary" page (and added it to the Appendices) that comes with a search bar and drop-downs. Still more to do on filling out the glossary (and perhaps making it better / more sophisticated in the future), adding in the extension features (so clicking on the phrase and getting the definition), but figured it was worth it to go ahead and push up the "Collections and Granules" page in the meantime. I also alphabetized the .yml version of the glossary. I also removed some sidebar headers that we currently have no page/ content for... they can always be added back later, but figured it better to take them away for now as they are not clickable. Take a look, please! :-)

[saberbrasher]

Also, I was curious about the auto checks failed error... my limited research suggested that a repo admin may need to adjust the workflow permissions (I guess for me) or it has something to do with the PR not coming from a branch within the main repository (aka, my fork).

[andypbarrett]

I am not sure about removing stubs (sidebar headings with no content). This was done so that we have a structure to build out. Removing them seems like a backwards step.

I suggest we keep these lines in the _quarto.yml but comment them so that they do not show up.

An alternative would be to keep the headings and have a page with "Work in Progress"

[andypbarrett]

Looking at the details, the failing check appears to be because a url link does not exist. That might need some trouble shooting.

[saberbrasher]

@andypbarrett thanks for looking so fast! I'm not sure why I didn't think to just comment out the unused sidebar headers... I can put those back in hidden.

Regarding the glossary.qmd: I actually did try to figure out a way to script this and ended up getting frustrated / limited by my python-ing haha. I can definitely tinker with it more, but for the short term, and while our glossary is short, I did like the idea of still having something of a glossary in our appendix... I do think a script will be better for the long term, but until I/ you/ someone figures out the best way to do it, I am okay maintaining this static version when the glossary.yml gets updated. If you hate this short term idea, or others do, it can obviously be ditched.

Are you okay with the collections-granules.qmd? I wasn't sure how deep to go, but thought this was an okay start.

[andypbarrett]

I've identified some sections that need clarification or don't quite nail the concept. I've also made some suggestions for additions and changes.

I don't think we will get to scripting the glossary for a while so what you have for the glossary page works for now.

[saberbrasher]

@andypbarrett and anyone else following along:
I made the revisions and pushed up a new commit. I left the public-facing glossary as is for now, but have a "glossary-test" file now that does actually pull from the glossary.yml... but doesn't do any pretty formatting. It can be tinkered with more later and is not currently rendering anywhere on the site.

[mikala-nsidc]

My only comment so far is regarding this definition:
Each granule usually represents a single point in space and/or time,
I'm not sure how often (for which percentage of data sets) this is actually the case, so I'm hesitant to say "usually". It's not the case for along-track data, such as for the ICESat-2 mission. And if I think of SMAP L2 swath data, a swath is collected over time, not in a snap shot, and so it isn't really a single point in time (or space). I don't think we need to be quite so specific. Granules are divided and bundled in a way that makes sense for a particular sensor and its data, and can vary greatly.

[saberbrasher]

@mikala-nsidc just made a new commit that modifies this language to be less specific!

[mikala-nsidc]

@saberbrasher Thanks!! Looks good!