Low Quality Dashboard - Githubissues

ebraker commented 5 years ago

@Jegelewicz what do you think about doing an intro to the dashboard and mini-recap of our SPNHC talk for a webinar?

Jegelewicz commented 5 years ago

Oh yeah - that would be really good. Just say when.

ebraker commented 5 years ago

Awesome! I'm thinking the 2nd Tuesday in September or November (Aren is on the docket for October). Probably up to you since I'd like to schedule the GitHub Documentation how-to in one of those slots and I'm hoping to rope you and Michelle into that (again...sorry :/). I'm free either month for the Dashboard/Metrics webinar. Let me know if you have a preference and then I'll reach out to Michelle to confirm she can help with the GitHub demo so we can fill the schedule for the first 3 webinars this fall.

Jegelewicz commented 5 years ago

Let's take September since we don't have to plan from scratch unless Michelle wants to do Documentation then.

ebraker commented 5 years ago

we should put together a webinar abstract - do you think we should cover some of the metrics found throughout Arctos or just stick to the low quality dasboard and tools available for infilling data gaps?

campmlc commented 5 years ago

I like the idea of the dashboard showing some good metrics as well that we can show to administrators and use for reports.

On Wed, Aug 7, 2019, 1:01 PM Emily Braker notifications@github.com wrote:

we should put together a webinar abstract - do you think we should cover some of the metrics found throughout Arctos or just stick to the low quality dasboard and tools available for infilling data gaps?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ArctosDB/arctos-webinars/issues/29?email_source=notifications&email_token=ADQ7JBHD6V6MPPFEA7UTQQLQDMLW7A5CNFSM4IF2R54KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ZMSEQ#issuecomment-519227666, or mute the thread https://github.com/notifications/unsubscribe-auth/ADQ7JBFKM2QOBZBEYFEOS2DQDMLW7ANCNFSM4IF2R54A .

dustymc commented 5 years ago

Possibly-stoopid idea which everyone should feel completely comfortable ignoring: Take a quick detour into development/history-land. I'm not sure how, but I think it's important to emphasize that current Arctos reporting isn't what could be; there are ~∞ ways in which one could look at the data in Arctos (and beyond - eg, reports could easily pull from GenBank), and somewhat fewer ways to visualize the results of that.

Here's where I think we are now.

various people asked for various statistics, mostly when Arctos was both smaller and simpler
we did some stuff that more or less worked for that
keeps happening, but there's no unity - these were built for, and often linked to, specific nodes/purposes
dashboard idea comes along
We now have a framework. It's easy to add arbitrary things to it. REALLY arbitrary if necessary - a report of Agents who've collected soricids in july and have a 7 in their phone number is completely possible and fairly easy.
Many of these queries are stupid-expensive (eg, sorting through 800 million taxon terms), so there's caching; the cost is paid for when the DB isn't busy, not while users are waiting for pages to load.
The cache makes it cheap/easy to grab summary statistics, so we can sprinkle it around (eg, top of try something random).
There's a simple UI "dashboard," but it was just the fastest/easiest way I could make the data accessible.
- More tools might need funding, certainly needs discussion.
- I think there's some desire for a "brightly-colored boxes" UI
- An API could support stats packages, external report services, etc.
- Someone somewhere mentioned a subscription option (but see eg, https://github.com/ArctosDB/arctos/issues/1679 - do we as a community really want to make that easier to ignore? Maybe...)
- etc. - not really many technical limitations here

We have carefully designed the datastore to readily support unanticipated queries, now we have a back-end tool that makes it easy to gather summary data in response to user's requests, and that in turn could be used to feed most anything.

ebraker commented 5 years ago

@Jegelewicz How about this for the abstract?:

Arctos, an online collaborative museum collection management solution, is capable of providing its users with several metrics. Collection statistics, reporting features, data quality feedback and discovery tools aid Arctos users in improving data and quantifying collections use and impact.

In this presentation, we will demonstrate some of the Arctos metrics and tools currently available as well as highlight the “Low Quality Data Dashboard.” Still in its infancy, this dashboard compiles data improvement opportunities for Arctos users, including automated suggestions to enhance data integrity and linkages. Many summary tools were initially developed by request in isolation from one another and placed in proximity to the data tables that they summarize. Ultimately, the Arctos community plans to bring these dispersed performance metrics together in a centralized dashboard to help Arctos collections better comprehend, visualize, and communicate their holdings and activities, both quantitatively and qualitatively. We invite suggestions and feedback for any metrics or enhancements users would like to see implemented to achieve these aims.

Jegelewicz commented 5 years ago

Given @dustymc comments, my only edit.

Arctos, an online collaborative museum collection management solution, is capable of providing its users with ~~several~~ an infinite variety of metrics. Collection statistics, reporting features, data quality feedback and discovery tools aid Arctos users in improving data and quantifying collections use and impact.

In this presentation, we will demonstrate some of the Arctos metrics and tools currently available as well as highlight the “Low Quality Data Dashboard.” Still in its infancy, this dashboard compiles data improvement opportunities for Arctos users, including automated suggestions to enhance data integrity and linkages. Many summary tools were initially developed by request in isolation from one another and placed in proximity to the data tables that they summarize. Ultimately, the Arctos community plans to bring these dispersed performance metrics together in a centralized dashboard to help Arctos collections better comprehend, visualize, and communicate their holdings and activities, both quantitatively and qualitatively. We invite suggestions and feedback for any metrics or enhancements users would like to see implemented to achieve these aims.

ebraker commented 5 years ago

@Jegelewicz Can we schedule a combo soundcheck/planning session soonish? I am free this Friday, and my schedule is fairly open next week. Let me know what works.

Jegelewicz commented 5 years ago

I have a thing all day Friday. Tuesday or Wednesday afternoon between 2 and 5?

ebraker commented 5 years ago

Sure - let's do Tuesday @ 2pm

Jegelewicz commented 5 years ago

Shall we meet in the Zoom Room or should we schedule to iDigBio room?

Jegelewicz commented 5 years ago

Also - should we just use our slide deck from SPNHC augmented with real-time Arctos examples?

ebraker commented 5 years ago

That's along the lines of what I was thinking...I'll reserve Adobe Connect room so we can sound check while chatting about content

Jegelewicz commented 5 years ago

You're the BEST!

ebraker commented 5 years ago

Teresa and I both noticed some timeout errors and slow-loading pages earlier today while trying to prep for webinar, specifically:

'see results as' specimen summary page
'see results as' graph
review annotations page and unreviewed annotations link (from low-quality dashboard)

The 'see results as' pages timed out despite the same query working when run as a regular specimen search. Just checking to see if there was some sort of issue this morning or if we should avoid complex or large queries when live-demoing these tools. Mostly just putting it on your radar @dustymc

ArctosDB / arctos-webinars

Low Quality Dashboard #29