Missing event and locality change notifications #1969
Comments
|
I just got this one today: This report is available at https://arctos.database.museum/ScheduledTasks/authority_change.cfm?start=2019-03-13&stop=2019-03-14 Code tables changed between 2019-03-13 and 2019-03-14. These data may reflect discarded changes, changes that have not been used in data, or changes that your user cannot access. Contact any Arctos Advisory Group member for more information. Table GEOG_AUTH_REC:
|
|
I received that one! It's these guys that I haven't been getting:
|
|
I haven't received any of those either. In fact, I can't remember when or if I ever have... |
|
Thanks! I gave them both a kick, you should have email inbound and I think they're both happy now. |
|
Email received! Thanks Dusty! |
|
I think the locality change notifications have stopped running, again. |
|
Looks like it was timing out - I ran it and bumped that up. |
|
I'm getting this report (Arctos Locality Change Notification) but instead of changes to existing localities, I'm getting all the new localities that were created by everyone who did data entry in DMNS:Inv in the past day or so. Instead of my name (I'm the only one who routinely edits localities) the UserID is "unknown". Is this what the report is supposed to be? |
|
Let's keep this issue limited to the emails. I think the request to track who creates localities is from an AWG-ish meeting, summarized (under "accepted solution") in #1705 (comment). Feel free to start a new Issue for that - that thread has wandered far and wide... |
|
But I am talking about the emails - the same one that Anna copied into the thread from February 27. Here's the one I got this morning:
These aren't changes. (Nothing is outlined in red.) They're just all the localities created by new specimen records over the past day or so. In the past, what I got was changes to localities that I had made. |
|
In the email Arctos Locality Change Notification received this morning, I'm still getting a list of every locality CREATED by new specimen records - not CHANGES to existing localities. If that's what we want, it's OK, but it's not what we used to get. And the email title would more appropriately be Arctos New Localities and Locality Change Notification. In the email Arctos Collecting Event Change Notification (also received this morning), I am only getting changes to existing Collecting Events, so that one is still working as always. |
|
I agree we should only get changes.
…On Wed, Apr 10, 2019, 6:45 AM Phyllis Sharp ***@***.***> wrote:
In the email *Arctos Locality Change Notification* received this morning,
I'm still getting a list of every locality CREATED by new specimen records
- not CHANGES to existing localities.
If that's what we want, it's OK, but it's not what we used to get. And the
email title would more appropriately be *Arctos New Localities and
Locality Change Notification*.
In the email *Arctos Collecting Event Change Notification* (also received
this morning), I am only getting changes to existing Collecting Events, so
that one is still working as always.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1969 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hLEt0Sigr_w7KzvO3mu5OcSo7NrMks5vfdz2gaJpZM4b0bYo>
.
|
|
The notifications reflect what the trigger captures. |
|
We have the View Locality Edits history to see who has created or edited
localities, which is very useful. However, we don't need to see all new
localities in the emails. For the emails to serve any useful function,they
should just let us know who has made changes to localities used by our
collection. I realize edit and create Locality are now the same trigger -
no way to parse these out? If not, the emails don't really help.
…On Wed, Apr 10, 2019, 8:53 AM dustymc ***@***.***> wrote:
The notifications reflect what the trigger captures.
#1969 (comment)
<#1969 (comment)>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1969 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hNSNYWo4DCDG48YzIo7ToVS-mSgqks5vffrSgaJpZM4b0bYo>
.
|
|
Oh I see, finally, I think... I could remove notifications involving 'unknown' (or DBA or whatever we're calling that). I can't really distinguish between event types. That would also remove the notifications when eg, I mangle a million of your localities - I use the same account to do cross-collection stuff. I PROBABLY won't mangle a million of your localities.... Correct and acceptable? |
|
Yes, that will certainly help.
…On Wed, Apr 10, 2019 at 9:32 AM dustymc ***@***.***> wrote:
Oh I see, finally, I think...
I could remove notifications involving 'unknown' (or DBA or whatever we're
calling that). I can't really distinguish between event types.
That would also remove the notifications when eg, I mangle a million of
your localities - I use the same account to do cross-collection stuff. I
PROBABLY won't mangle a million of your localities....
Correct and acceptable?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1969 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hJlW2x6gwj7Aq7hGL31szufda30Wks5vfgQAgaJpZM4b0bYo>
.
|
|
Yes, it sounds like that will remove what we don't really need. Thanks! |
|
Not sure you've taken any action yet, but the locality change report I received this morning was all new localities added through single item data entry.
|
|
done |
Describe the bug
Dawn and I just realized that we haven't been receiving the nightly locality and event change notification emails for two weeks or so. I'm fairly certain that it's not just CHAS internal junk mail filters because we are still receiving authority table change notifications. Anyone else having this same problem?
The text was updated successfully, but these errors were encountered: