[Esip-cor] Notifications

[Carlos Rueda]

It seems there are two intermingled notification-related aspects at play in
this thread.

One related with the traditional notification mechanism supported by the
COR/ORR (which actually originated the first email in this thread). Those
are generated upon the actual registrations but queued in a way that reduce
the number of emails in case of multiple registrations in a short period of
time.

The other related with Lewis' new LDN stuff, which I of course let him talk
about as I just have a very basic idea of it ; )

Carlos


On Tue, Feb 5, 2019 at 9:44 AM John Graybeal via Esip-cor <
esip-cor at lists.esipfed.org> wrote:

> Well, since it already is a ''notification' (by polling) system, they
> don't *have* to go anywhere. :-)
>
> I think it will be useful to see them for a little bit longer, so it isn't
> urgent. The real question is, how can we turn off notifications for a
> particular ontology? I think we are talking about a configuration setting
> per ontology in COR.
>
> This brings another question to mind, sorry. Do I understand correctly
> that what is happening is that each notification results in an ontology
> update? Is the Python code doing the sorting of incoming notifications to
> make sure none are dropped, and does it then have the option of batching
> the ontology updates (if 5 notifications come in the same second, say)?
>
> John
>
> On Feb 5, 2019, at 8:33 AM, Mcgibbney, Lewis J (398M) <
> Lewis.J.Mcgibbney at jpl.nasa.gov> wrote:
>
> ACK John.
> Do you have a proposal for where notifications should go?
>
> Dr. Lewis John McGibbney Ph.D., B.Sc.
> Data Scientist II
>
>
>
> On 2/4/19, 8:03 PM, "Esip-cor on behalf of John Graybeal via Esip-cor" <
> esip-cor-bounces at lists.esipfed.org on behalf of esip-cor at lists.esipfed.org>
> wrote:
>
>    Our version notification emails will have to be tweaked if this gets
> popular!
>
>    John
>
>
> On Feb 4, 2019, at 18:23, ESIP COR via Esip-cor <
> esip-cor at lists.esipfed.org> wrote:
>
>
> A new ontology version has been registered:
>
> IRI: http://cor.esipfed.org/ont/ldn/inbox
>
> Name: ESIP Linked Data Notifications Inbox Graph
> Version: 20190205T022303
> Owner: ~lmcgibbn
> Submitter: lmcgibbn
> Updated: 2019-02-05T02:23:03.000Z
> Log: (not given)
>
>
>
> The following ontology has been registered:
>
> IRI: http://cor.esipfed.org/ont/ldn/inbox/29b29cdaeaea486eb3aa7267981429e2
>
> Name: ESIP Linked Data Notification: 29b29cdaeaea486eb3aa7267981429e2
> Version: 20190205T022303
> Registered: 2019-02-05T02:23:03.000Z
> Owner: ldn
> Submitter: lmcgibbn
>
>
> (You have received this email because your address is included in
> /etc/orront/notifyemails)
>
>
> ========================
> John Graybeal
> Technical Program Manager
> Center for Expanded Data Annotation and Retrieval /+/ NCBO BioPortal
> Stanford Center for Biomedical Informatics Research
> 650-736-1632
>
>
> _______________________________________________
> Esip-cor mailing list
> Esip-cor at lists.esipfed.org
> https://lists.esipfed.org/mailman/listinfo/esip-cor
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-cor/attachments/20190205/e235dbd6/attachment-0001.html>