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

Add properties.published_by to notification message #106

Open
antje-s opened this issue Mar 8, 2024 · 1 comment
Open

Add properties.published_by to notification message #106

antje-s opened this issue Mar 8, 2024 · 1 comment

Comments

@antje-s
Copy link
Contributor

antje-s commented Mar 8, 2024

We had problems with notifcations that are republished by GCs and also have set cache="false".
In these cases, it is not possible to determine who republished the notification via the download link value. In the event of notification format errors, no suitable contact person can be found.
Initial value could be center-id of the originator and then be replaced by the GCs with their center-id.

If we always carry this value with us, we can also determine which GCs republished which origin notification. This could be a useful information in the pre-operational phase.

To be discussed during our next TT-WISMD meeting if useful/needed...

@tomkralidis
Copy link
Collaborator

tomkralidis commented Mar 25, 2024

TT-WISMD 2024-03-25:

  • allowing consumers subscribing to 'cache'd data may or may not be aware that a given organization has set their notification to cache: false
  • what is the value of differentiating between origin and cache then?
  • may be difficult for users to "search" for topics, not knowing what is routed where
  • needs more thought
  • origin will have more data notifications than cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants