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

Notification abonnement on catalogus #156

Open
JanBrek opened this issue Jun 5, 2024 · 5 comments · May be fixed by open-zaak/open-zaak#1757
Open

Notification abonnement on catalogus #156

JanBrek opened this issue Jun 5, 2024 · 5 comments · May be fixed by open-zaak/open-zaak#1757

Comments

@JanBrek
Copy link

JanBrek commented Jun 5, 2024

Coming forth from a comment in ticket open-zaak/open-zaak#1661

Allow notification API to be set per catalogus. So set your abbonement to a catalogus instead of using zaaktype as filtering.

One possible solution would be that the zaak kanaal also will include catalogi name/number/whatever in the notification so that it can be used as a filter.

@joeribekker
Copy link
Member

Refinement: So, Zaken will be filtered in the subscription on the catalog. This is an experimental feature!

Estimate: 5 days

@joeribekker
Copy link
Member

@JanBrek ping

@PeterVanBragt
Copy link

Asked Peter Arkesteijn if he has a budget for this

@PeterVanBragt
Copy link

@joeribekker I can hereby approve this ticket.

@joeribekker
Copy link
Member

joeribekker commented Sep 17, 2024

Refinement:

There's 2 options to implement this:

  1. We add catalog as a "kenmerk" to the subscription AND the notifications that are sent out.
  2. We allow subscribing on catalog and based on the zaaktype-kenmerk, we retrieve the appropriate catalog to decide if a notification should be sent.

We go for option 1 (far less spaghetti) and will retrieve the catalog over the network for external zaaktypes.

Please mark this everywhere as EXPERIMENTAL.

stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 19, 2024
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 19, 2024
…enmerken

and support kenmerken for django-loose-fk fields
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 19, 2024
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 19, 2024
…enmerken

and support kenmerken for django-loose-fk fields
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 20, 2024
…et_kenmerken

and add hook for `_get_field` to support nested attributes in Open Zaak
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 20, 2024
…et_kenmerken

and add hook for `_get_field` to support nested attributes in Open Zaak
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 20, 2024
…et_kenmerken

and add hook for `_get_field` to support nested attributes in Open Zaak
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 20, 2024
…et_kenmerken

and add hook for `_get_field` to support nested attributes in Open Zaak
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
stevenbal added a commit to maykinmedia/notifications-api-common that referenced this issue Sep 20, 2024
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
because this kenmerk is not part of the standard, it is marked as experimental
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 20, 2024
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 26, 2024
because this kenmerk is not part of the standard, it is marked as experimental
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 26, 2024
stevenbal added a commit to open-zaak/open-zaak that referenced this issue Sep 26, 2024
previously this referred to the notifications documentation in the reference implementations, but since an experimental kenmerk was added (zaaktype.catalogus), this reference is no longer accurate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants