-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Comments
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 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. |
I'll see how far I can get with aggressive caching and simple popup reminders. |
Is this necessary? Those send nightly emails which are hard to avoid and contain everything (and it's expensive)
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?
same as above?? |
I use the unreciprocated relationships notification, but once a month would
be fine.
Barcodes without parts could be a report that I can access - I don't need
an email.
Barcodes in the Universe for my collection (that aren't labels). Same thing
- useful, but at most maybe an annual or semiannual report link to click on?
…On Wed, Jan 30, 2019 at 11:11 AM dustymc ***@***.***> wrote:
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??
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1419 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hBL8BW4Bmq-tpN-JKgUInFjCdnOfks5vIeBAgaJpZM4RxHIP>
.
|
To clarify: I'm working on something like
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. |
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..... |
Consider that stolen - thanks!
Definitely all linked - everything I'm looking at messes with those. |
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). |
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. 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: |
@dustymc this is a start, but a real dashboard looks like this: Click the button, get the report. Could we make it pretty? Can I help? |
see also https://github.com/ArctosDB/SPNHC-2019/issues/4 I can rename the form-probably-soon-to-be-formerly-known-as-dashboard. seems to be more what you're looking for. |
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! |
Stats are being gathered, there's a UI, closing. |
from @DerekSikes
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).
The text was updated successfully, but these errors were encountered: