We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 4229 - Subscriptions: Subscription access based on journal roles
Subscriptions: Subscription access based on journal roles
Status: NEW
Product: OJS
Classification: Unclassified
Component: Subscriptions
3.1
Other Linux
: P3 enhancement
Assigned To: Michael Felczak
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-01 09:30 PDT by Michael Felczak
Modified: 2013-05-29 15:45 PDT (History)
7 users (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Felczak 2009-05-01 09:30:21 PDT
Under Subscription Policies, JM/SM should have the option to grant permanent subscription access to any of the following:

- Journal Managers
- Subscription Managers
- Editors
- Section Editors
- Layout Editors
- Copyeditors
- Proofreaders
- Authors who have published with the journal
Comment 1 Michael Felczak 2009-05-01 09:36:48 PDT
Courtesy of:
http://pkp.sfu.ca/support/forum/viewtopic.php?f=2&t=4455
Comment 2 Alec Smecher 2009-05-01 09:37:02 PDT
FYI, most of those are already assumed to have subscription access. IMO there's no point in even optionally denying access to JMs, Editors, and possibly others, since they have enough access to read content anyway.
Comment 3 Michael Felczak 2009-05-01 09:41:53 PDT
Yup, good point. We really only need the last one as an explicit option under Subscription Policies.
Comment 4 James MacGregor 2009-05-01 09:50:48 PDT
Just a thought: what about the option to be able to grant permanent subscription access to any user regardless of role -- for example, in the case where a user was a journal manager but has retired, but still should have access to content as a courtesy.
Comment 5 Alec Smecher 2009-05-01 09:54:08 PDT
James, what about simply creating a good old subscription for that user? I dunno if we want to maintain too many boundary cases in the code. I can see the general usefulness of an option to grant authors subscription access, however.
Comment 6 James MacGregor 2009-05-01 09:59:59 PDT
What about a 'perpetual' option in the create subscription date section? Just creating a normal subscription would suffice, but then you'd have to update it. I'm almost thinking of this as a sort of 'founder's' subscription, or one for large donors, etc. However, now that I think about it, if you think this might be a good idea this is probably a new bug.
Comment 7 Michael Felczak 2009-05-01 10:23:26 PDT
I agree a standard subscription should suffice for these cases (i.e. for founder's). And yes, to ensure that the subscription never expires, we could have an option for this purpose, such that either the start/end dates are used or the subscription never expires.

This additional option would also be useful for institutional subscriptions that should never expire. For example, a single, non-expiring institutional subscription could be created for partner institutions or developing nations, etc. and IP ranges added/removed based on institutions added/removed from the qualifying criteria.
Comment 8 Michael Felczak 2009-05-01 11:34:37 PDT
Filed subscription non-expiry option as Bug 4230.
Comment 9 James MacGregor 2011-06-16 10:00:51 PDT
The author-access aspect of this just came up with a hosted journal of ours, and I thought I'd throw in a further/finer-grained suggestion: allow submitting authors to be able to access their own submission article galleys if logged in (so basically a selective subscription to that one article). 

There's one possible issue wrt submitting authors submitting articles on behalf of someone else. 

Another option would be to allow author access to that entire issue. I know that in the print world, most journals mail out a gratis copy or two of the issue an author appears in.