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

Refactor: notifications #148

Conversation

syphax-bouazzouni
Copy link

@syphax-bouazzouni syphax-bouazzouni commented May 26, 2022

Changes :

@syphax-bouazzouni syphax-bouazzouni marked this pull request as ready for review May 26, 2022 21:11
@syphax-bouazzouni syphax-bouazzouni changed the title Refactor notifications Refactor: notifications Sep 14, 2022
@alexskr alexskr requested a review from mdorf November 6, 2023 20:53
Copy link

codecov bot commented Dec 1, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (master@fc90752). Click here to learn what that means.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #148   +/-   ##
=========================================
  Coverage          ?   80.66%           
=========================================
  Files             ?       64           
  Lines             ?     4959           
  Branches          ?        0           
=========================================
  Hits              ?     4000           
  Misses            ?      959           
  Partials          ?        0           
Flag Coverage Δ
unittests 80.66% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@alexskr alexskr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This refactor of notifications is highly valuable and useful.

The BioPortal team acknowledges the potential value in receiving notifications for new user/ontology additions. However, BioPortal does not curate ontologies, so such notifications could potentially generate unnecessary noise. Having an option to disable these specific notifications send to the support email would be greatly appreciated.

Ideally there should be an option for ontology admins to opt in/out of the notifications when ontology is processed/pull fails.

lib/ontologies_linked_data/utils/notifications.rb Outdated Show resolved Hide resolved
<li>Click the &quot;Edit submission information&quot; link.</li>
<li>In the Location row, verify that you entered a valid URL for daily loading of your ontology in the URL text area.</li>
</ol>
If you need further assistance, please <a href="mailto:support@bioontology.org">contact us</a> via the BioPortal support mailing list.
If you need further assistance, please <a href="mailto:%support_mail%">contact us</a> via the %ui_name% support mailing list.
Copy link
Member

@alexskr alexskr Dec 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR introduces a new configuration variable LinkedData.settings.admin_emails to enable notifications sent to OntoPortal Administrators, addressing the necessity of replacing hard-coded email addresses.

However, upon deployment in BioPortal, this change will result in end users receiving emails requesting them to contact administrators of BioPortal instead of the expected support email list. To mitigate this, it might be necessary to introduce a secondary configuration option, something equivalent to $SUPPORT_EMAIL in the UI. This new option would serve to differentiate between contacting support and contacting administrators unless BioPortal team chooses to change the default method of contacting support for these kind of notifications.

@alexskr alexskr changed the base branch from master to pr-refacotor-notification January 18, 2024 07:45
@alexskr alexskr merged commit dca560d into ncbo:pr-refacotor-notification Jan 18, 2024
4 checks passed
@alexskr
Copy link
Member

alexskr commented Jan 18, 2024

merged PR into pr-refacotor-notification branch instead of master. We need to do additional tests and make a few minor tweaks before merging it into master.

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

Successfully merging this pull request may close these issues.

2 participants