Skip to content

Conversation

@alexskr
Copy link
Member

@alexskr alexskr commented Feb 7, 2024

syphax-bouazzouni and others added 25 commits April 4, 2022 14:30
- Rename variables and methods to make a clear distinction between
  OntoPortal site admins, ontology admins and support.
- Add new feature to optionally disable notifications send to OntoPortal
  admins for each event associated with ontology creation, new user, etc
- LinkedData.setting.support_contact_email is a new configuration option
  for setting end user support contact email.
  BioPortal requires different emails for contacting BioPortal site
  admins and end user support

In order to clarify the distinction between the OntoPortal site admins and
ontology owners/admins the following settings and methods are renamed:

LinkedData.setting.admin_emails is renamed to ontoportal_admin_emails
LinkedData::Utils::Notifier.admin_mails -> ontology_admin_emails
LinkedData::Utils::support_mails -> ontoportal_admin_emails
LinkedData::Utils::notify_support_grouped -> notify_ontoportal_admins_grouped
@codecov
Copy link

codecov bot commented Feb 7, 2024

Codecov Report

Attention: 30 lines in your changes are missing coverage. Please review.

Comparison is base (4b6b7f4) 80.76% compared to head (5900570) 79.96%.
Report is 9 commits behind head on master.

❗ Current head 5900570 differs from pull request most recent head 1e8bd29. Consider uploading reports for the commit 1e8bd29 to get more accurate results

Files Patch % Lines
lib/ontologies_linked_data/utils/notifications.rb 61.97% 27 Missing ⚠️
lib/ontologies_linked_data/utils/notifier.rb 94.82% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #187      +/-   ##
==========================================
- Coverage   80.76%   79.96%   -0.80%     
==========================================
  Files          63       64       +1     
  Lines        4917     4957      +40     
==========================================
- Hits         3971     3964       -7     
- Misses        946      993      +47     
Flag Coverage Δ
unittests 79.96% <78.41%> (-0.80%) ⬇️

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.

@alexskr alexskr changed the title Merge Develop to Master Merge Develop to Master, release v5.28.0 Feb 7, 2024
@alexskr alexskr merged commit 0423a45 into master Feb 7, 2024
@jvendetti
Copy link
Member

The screenshot below was provided as an example of the notification that an ontology owner receives after a successful processing. The text of "Parsed successfully" directly followed by "Obsolete" is confusing, and I believe will generate traffic on our support list from users asking what this means. I object to releasing this in production without addressing this.

Screenshot 2024-02-09 at 11 35 39 AM

@alexskr
Copy link
Member Author

alexskr commented Feb 9, 2024

obsolete submission status in the REST API is associated with determining obsolete classes and properties. Including this status in email notification can create some confusion so it should not be included in the email notification
..

@alexskr
Copy link
Member Author

alexskr commented Feb 9, 2024

The screenshot below was provided as an example of the notification that an ontology owner receives after a successful processing. The text of "Parsed successfully" directly followed by "Obsolete" is confusing, and I believe will generate traffic on our support list from users asking what this means. I object to releasing this in production without addressing this.

addressed by c77d0b3

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.

4 participants