Need to add a Caveat Lector post about using the data browser

CaRCC / rcd-nexus-portal

RCD Nexus Portal, including Capabilities Model assessment

0 stars 0 forks source link

Need to add a Caveat Lector post about using the data browser #131

Open plschmitz opened 6 months ago

plschmitz commented 6 months ago

Use the case of comparing private institutions by EPSCoR status. It appears to indicate that there is a huge difference between private institutions in EPSCoR and non-EPSCoR jurisdictions. If the user investigates by filtering the institutions by carnegie classification, it emerges that the dataset is skewed such that institutions from EPSCoR jurisdictions are mostly smaller (not R1 or R2) while the non-EPSCoR jurisdictions (like the dataset as a whole) is heavily weighted to R1 and R2 institutions. Said differently, most of the EPSCoR jurisdictions have large publics in the dataset, and few or no large privates. See attached graph privatebyepscor

plschmitz commented 6 months ago

As it turns out, among the 2634 institutions included in our IPEDS import, there are only 3 Private R1 institutions and 3 Private R2 institutions in EPSCoR jurisdictions, vs 36 Private R1 institutions and 37 Private R2 institutions in non-EPSCoR jurisdictions.

plschmitz commented 6 months ago

If we can implement the counts in each category as part of the filtergraph UI, users will be able to see at least part of the problem here.

plschmitz commented 1 month ago

Adding Lauren as this is a good intro to writing up analyses of the data. Question: where do we add this? Is it in the intro, quick start, a separate section in the help docs? Almost certainly a blog post (as well).

lmichael107 commented 4 weeks ago

I think we could do the following:

In the interface, Patrick's suggestions of counts makes a LOT of sense.
In the interface, I think a questionmark after "Filters:" could be added with "Caution: The Quick Start Guide describes important caveats, given limited data."
In the Quick Guide, have a warning with ONE example (maybe this one) that points to a section in the help docs that goes further.

And I agree with a blog post AND making this aspect clear in any training (a couple examples), reports (maybe exhaustive-ish?), etc.

plschmitz commented 3 weeks ago

Pushing to 2.2. Adding counts to the legend is a fair amount of work. We can do the blog post independent of the software release cycle.

plschmitz commented 1 week ago

Add a caveats on viewing data section to the guide.