Hi, not getting any response to this query, so thought I’d elaborate on the circumstance leading to my question:
AJOL was an early adopter of OJS, starting with the original OJS 1 and eventually upgrading to OJS 2 around 2009. Because of various issues resulting from the early uptake, the system has been quite heavily modified, although I’ve been working on it for some years now doing various upgrades (currently on OJS 2.4.8), and trying to remain as close to OJS core code wherever possible.
AJOL is also quite complex due to the size of the installation, currently supporting 525 live journals (with over 178 000 articles in close to 15 000 issues). Some journals are open access and some have their full text pdf’s behind a paywall.
One major modification that was done years ago, was to create a site-wide registration system, where a user would automatically be enrolled to all 500+ journals upon registration. At the time, in order to limit database growth and improve system performance (being situated in a developing country we’ve always had problems with slow internet and limited resources in general), AJOL got rid of the ‘Reader role’ requirement, and programmatically assumed all users had the Reader Role (0x00100000), else 300 000 registered users registered in 500 journals would inevitably result in millions of records just to manage Reader roles.
Each user could then select which journals they wanted to receive notifications for and this was recorded in table notification_subscription_settings with setting ‘emailed_notification’, which it seemed standard procedure up to OJS 2.4.8.
We’re currently upgrading to OJS3 and one of the last items on the to-do-list is to decide how to proceed with the Reader Role scenario, bearing in mind we’re generally using the upgrade as an opportunity to get our code in line with core OJS code wherever possible. In the past, OJS documentation has been rather sketchy, so I was pleased to find a definition of the Reader Role at https://docs.pkp.sfu.ca/learning-ojs/en/user-accounts#reader
“Readers receive a notification email with the publication of each issue, which includes the Table of Contents for that particular issue.”
This leads to the following questions:
How is this related to the “emailed_notification” setting in notification_subscription_settings table as migrated from OJS 2.4.8?
What other purpose does the Reader Role have in OJS 3?
If that is the sole purpose of the Reader role, should the notification_subscription_settings simply be migrated to Reader roles instead?
Perhaps @ajnyga or @asmecher has some input?