Which email address should Hakai ERDDAP admin points to about hakai-datasets

[n-a-t-e]

how about [email protected] ?

[JessyBarrette]

After talking to a few of the different people getting emails from [email protected], we're thinking it would be best to use another address.

[email protected] is more an email to reach out about data questions related to Hakai.

how about creating [email protected]

[JessyBarrette]

Perfect! Do both variant - or . are pointing to the same groups

[steviewanders]

Ah Java, even your logs are verbose nonsense

[fostermh]

what kind of emails are sent from erddap? or is it to advice users who to contact if they have questions?

[JessyBarrette]

ERDDAP sends a log summary and some key flag keys to trigger some actions on the server side.

It does suggest the user to contact the ERDDAP admin through this page at least I can see:
https://catalogue.hakai.org/erddap/legal.html#contact

[JessyBarrette]

[email protected] is now however taken over by @Br-Johnson @timvdstap and I for hakai data wide specific issues. Though it could added in there certainly. But I guess this group would have to filter down what it gets back since the logs are very frequent

[n-a-t-e]

I think the log emails go to emailEverythingTo, no?

https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#setup.xml

[JessyBarrette]

Oh yeah I guess your right, this is setup to point to ***@***.*** Which i think is alright and I am getting those.

…

On Thu, Jan 11, 2024 at 5:08 PM Nate ***@***.***> wrote: I think the log emails go to emailEverythingTo, no? https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#setup.xml — Reply to this email directly, view it on GitHub <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHICYOMTLZSUKYWP4MPSFADYOBPE3AVCNFSM6AAAAABBXDUOWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGA2DMMJVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Jessy Barrette M.Sc.* *Marine Data and Instrumentation Specialist* Hakai Institute <https://www.hakai.org/> | CIOOS Pacific <https://cioospacific.ca/> | CIOOS <https://cioos.ca/> | ***@***.*** | (C) [phone]

[JessyBarrette]

Then I'm not too sure what is sent to the adminEmail. Then if the logs aren't sent via that admin email. I'm ok pointing to [email protected]

We can always reassess later.

[JessyBarrette]

Here's an example of email received presently at [email protected]

---------- Forwarded message ---------
From: <[[email protected]](mailto:[email protected])>
Date: Thu, Jan 11, 2024 at 12:03 PM
Subject: df14a0d39f57 ERDDAP: ERROR in HakaiKetchikanBoLResearch constructor (inotify)
To: <[[email protected]](mailto:[email protected])>


https://localhost:8443/erddap reports:
java.nio.file.NoSuchFileException: /datasets/HakaiKetchikanBoLResearch
 at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
 at java.base/sun.nio.fs.UnixException.asIOException(UnixException.java:115)
 at java.base/sun.nio.fs.LinuxWatchService$Poller.implRegister(LinuxWatchService.java:246)
 at java.base/sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:266)
 at java.base/sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:364)
 at java.base/java.lang.Thread.run(Thread.java:833)

[fostermh]

That sounds reasonable, who would be in the group?

[steviewanders]

@fostermh Is this a Google group you are creating or an email alias or a new Google user?
Personally I've been creating Google Groups for project specific email collection and adding everyone involved so that the entire history of emails is preserved regardless of who is in the group and anyone added in the future can see previous.

[fostermh]

I was thinking of a google group, yes. similar to [email protected], [email protected], etc.

instead of [email protected] we could consider [email protected]. It matters not to me. I'm happy to create, or someone else can.

[JessyBarrette]

Just to summarize the emails related to this erddap deployment:

emailFromAddress: [email protected]
emailEverythingTo: [email protected]
emailDailyReportsTo:
adminEmail: [email protected] -> [email protected]

. or -

erddap.support seems good to me. I guess the only thing is since we're already using [email protected], perhaps it should be instead erddap-support. Or we move erddap-notifications to erddap.notifications I don't really care though.

Who to add to the group. You can at least add me, not sure you wanna be included but all guess perhaps the 4 us.

PS We'll have to think about something similar for the cioospacific erddap.

[steviewanders]

I'll be included while we are doing the ongoing ERDDAP dev work and when that is over I will leave the group.

[fostermh]

erddap support email group
[email protected]
[email protected]

erddap notifications email group
[email protected]
[email protected]

are all live

[JessyBarrette]

Both Hakai ERDDAP were updated with the admin email [email protected]

[JessyBarrette]

I don't think I received any erddap-support emails yet. lots of notitifcations one though haha

[jpkellogg]

Woohooo! I haven't received any in the last 24 hours. Yippee! Thanks guys! Jonathan

…

On Wed, Jan 24, 2024, 12:13 PM Jessy Barrette ***@***.***> wrote: I don't think I received any erddap-support emails yet. lots of notitifcations one though haha — Reply to this email directly, view it on GitHub <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APA2V4DUM4ELBMNF7VTK3WDYQFTQHAVCNFSM6AAAAABBXDUOWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYHA2DOMJYGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[JessyBarrette]

All the erddap referencing [email protected] were taken down.