Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reporting #1419

Closed
dustymc opened this issue Jan 29, 2018 · 15 comments
Closed

reporting #1419

dustymc opened this issue Jan 29, 2018 · 15 comments
Labels
Enhancement I think this would make Arctos even awesomer! Help wanted I have a question on how to use Arctos Infrastructure-limited Issue which could be resolved, or more easily resolved, with additional computational power Priority-High (Needed for work) High because this is causing a delay in important collection work..

Comments

@dustymc
Copy link
Contributor

dustymc commented Jan 29, 2018

from @DerekSikes

Maybe when an admin logs in there could be a summary of that admin's data and things waiting to attended to like a count of unchecked localities, overdue loans, etc.? Ideally the admin would be able select from a list of items to be presented so they're not getting bothered by things they don't care about? Seems like a slippery slope of nearly infinite things though...

I like the idea of a "report central" and something more fine-grained than the current collection contact based approach. (E.g., a student may deal with {something} and need only reports involving that.)

There are a bunch of existing reports which do not send email, and perhaps some (all??) users would like an occasional email of specimens which have been used and not cited (or anything else that currently lives under the Reports tab).

I can also see value in having a centralized way to access current email reminders. There's an email for overdue loans and another for unreciprocated relationships, it's possible to find both of those things from Arctos, but there's no one "show me active/current problems" place.

A framework which supports "send email when {user-supplied SQL query returns something}" would be useful. (This started from a probably-collection-specific container issue.)

"nearly infinite" doesn't scare me as long as it's by subscription, but depending on implementation might require more resources (eg, a server dedicated to scheduled tasks - which would benefit us now).

Flagging "wish list" - this might require funding (eg, meetings, development, hardware).

@dustymc dustymc added Blocked: Needs Discussion Enhancement I think this would make Arctos even awesomer! Help wanted I have a question on how to use Arctos labels Jan 29, 2018
@dustymc dustymc added this to the Wish List milestone Jan 29, 2018
@Jegelewicz
Copy link
Member

I like the idea of a "report central" and something more fine-grained than the current collection contact based approach

Agree. It would be fabulous if the first time I log in each month (that is 12 times a year) I would be greeted with a page that offered me links to:

Overdue loans
Unresolved annotations
Unreciprocated relationships
Barcodes without attached parts
Barcodes in "The Universe" (that aren't just container labels)
Scientific Names used in my collection(s) with no associated classification
Locality description/coordinate mismatches
Parts with disposition "being processed" for longer than a year
Media I uploaded which are not associated with anything
other?....

The page with links could be available in Reports/Services, but the monthly reminder might help get more things resolved. Or it might not - see my SPNHC/TDWG presentation on iDigBio data quality flags. We really don't have time for flags/annotations. We need more staff.

@dustymc dustymc added the Infrastructure-limited Issue which could be resolved, or more easily resolved, with additional computational power label Sep 12, 2018
@dustymc dustymc modified the milestones: Wish List, Active Development Jan 30, 2019
@dustymc
Copy link
Contributor Author

dustymc commented Jan 30, 2019

I'll see how far I can get with aggressive caching and simple popup reminders.

@dustymc
Copy link
Contributor Author

dustymc commented Jan 30, 2019

Unreciprocated relationships

Is this necessary? Those send nightly emails which are hard to avoid and contain everything (and it's expensive)

Barcodes without attached parts

I think this would just be overwhelming - there are hundreds of thousands, and having thousands in any collection (that uses barcodes) at any time is probably "doing it right." What don't I understand?

Barcodes in "The Universe" (that aren't just container labels)

same as above??

@dustymc
Copy link
Contributor Author

dustymc commented Jan 30, 2019

Locality description/coordinate mismatches

What is meant by this?

screen shot 2019-01-30 at 2 01 15 pm

has the difference between assigned and service coordinates, but the service isn't very good. Anything more robust is probably going to require GIS capability.

@campmlc
Copy link

campmlc commented Jan 31, 2019 via email

@dustymc
Copy link
Contributor Author

dustymc commented Jan 31, 2019

To clarify: I'm working on something like

It would be fabulous if the first time I log in each month (that is 12 times a year) I would be greeted with a page that offered me links to:

which seems a useful approach for things that area easy to miss in the normal notifications, or things that are in reports which require user action to view, or maybe things that should be in reports but aren't yet. The relationship email report is cumulative - anything you miss will be in the next one. The loan report goes out something like once a year after the email flurry around the due date - more-frequent lightweight notifications ("you have 59 overdue loans - click for more") might be useful for that. The loan report doesn't go out at all if there's no due date - looking for different ways to view data often uncovers stuff like that, and minimally should make our documentation better.

I'm hoping to build a framework and maybe provide some useful data, and from that we can figure out what individual user customization and user-generated reports and such would take.

This isn't going to directly change anything existing - file an Issue to do that, or for new reports/forms.

@Jegelewicz
Copy link
Member

Dusty,

I think we are all envisioning a "dashboard" even though no one has said that term. I am thinking about it because of recent conversations with Deb Paul about collection metrics - a future issue on that, but I am overwhelmed right now.....

@dustymc
Copy link
Contributor Author

dustymc commented Feb 1, 2019

dashboard

Consider that stolen - thanks!

collection metrics

Definitely all linked - everything I'm looking at messes with those.

@Jegelewicz
Copy link
Member

Hey @dustymc I was doing other stuff when I stumbled upon this: http://arctos.database.museum/Reports/georef.cfm

This would be awesome on the "dashboard", but I only want to see my collection (or a collection of my choice if I manage many).

@dustymc
Copy link
Contributor Author

dustymc commented Feb 5, 2019

There is a basic framework in place for this now, mostly dealing with finding and caching problematic data.

We should be able to add email alerts or personalization or whatever later, if that proves useful.

I'll continue to add reports - please continue to request them here.

I think this could be more effective as small tasks presented often rather than (or perhaps in addition to) one giant list of tasks presented periodically, so I've added a couple things to the Random widget for manage_collection users.

screen shot 2019-02-05 at 10 34 35 am

That should perhaps be in the header (maybe the announcement area) or something - it's modular so shouldn't be much problem to sprinkle it around.

You can access the giant list here:

screen shot 2019-02-05 at 10 27 41 am

@dustymc
Copy link
Contributor Author

dustymc commented Mar 15, 2019

#1702

@Jegelewicz
Copy link
Member

@dustymc this is a start, but a real dashboard looks like this:

image

Click the button, get the report.

Could we make it pretty? Can I help?

@Jegelewicz Jegelewicz added the Priority-High (Needed for work) High because this is causing a delay in important collection work.. label Mar 15, 2019
@dustymc
Copy link
Contributor Author

dustymc commented Mar 22, 2019

see also https://github.com/ArctosDB/SPNHC-2019/issues/4

I can rename the form-probably-soon-to-be-formerly-known-as-dashboard.

Screen Shot 2019-03-22 at 12 41 24 PM

seems to be more what you're looking for.

@Jegelewicz
Copy link
Member

Well, really we have two dashboards. The stats, which are great for showing how awesome we are and the low quality data which shows that we still have work to do (job security?) I like the idea of having them both and making them both pretty!

@dustymc
Copy link
Contributor Author

dustymc commented Aug 7, 2020

Stats are being gathered, there's a UI, closing.

@dustymc dustymc closed this as completed Aug 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement I think this would make Arctos even awesomer! Help wanted I have a question on how to use Arctos Infrastructure-limited Issue which could be resolved, or more easily resolved, with additional computational power Priority-High (Needed for work) High because this is causing a delay in important collection work..
Projects
None yet
Development

No branches or pull requests

3 participants