You are viewing the PKP Support Forum | PKP Home Wiki

reader role vs notifications

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

reader role vs notifications

Postby jmir » Wed Jan 16, 2008 5:01 pm

Conceptually, what is the difference between signing up as a "reader" for a journal, and checking the "notification" checkbox?

In single-journal installations of OJS, users find in their profile a checkbox for "Reader", and another checkbox for "Notification". I actually commented out the "Reader" checkbox because it is so confusing for users (why is this needed?)

Also, there are two db tables, one for roles, another one for notification_status - which one is used as notification flag?
Posts: 74
Joined: Mon Feb 26, 2007 12:16 am

Re: reader role vs notifications

Postby jmacgreg » Thu Jan 17, 2008 1:26 pm

Hi Gunther,

You can actually control whether users can register as readers (or authors and/or reviewers) from Journal Setup Step 4.1, without needing to comment anything out.

The difference between users requesting notification of new journal content vs. registering as a reader is a little subtle: the journal's editorial staff can email registered readers as a group at any time from their user home, so they can receive other notices, whereas signing up for new-content notifications only will of course limit any emails to that very specific subset. Basically, signing up for notifications allows the user to dictate control over notifications, whereas as a reader they can receive notifications at the 'whim' of the editorial staff.

In my experience with other editors, they have found it handy to have users enrolled as readers as sort of a 'subscribers' list, even if they are open access. The readers list provides them with a concrete user base that they can communicate with; and it can also provide granting/funding organizations with a handy statistic, if needed. There are many possible reasons for wanting an idea on readership; but this function can be fairly easily ignored as well.

The notification_status table is used to store the Notification checkbox information.

Posts: 4191
Joined: Tue Feb 14, 2006 10:50 am

Return to OJS Technical Support

Who is online

Users browsing this forum: No registered users and 2 guests