PKP Bugzilla – Bug 4508
allow Journal Managers to make ghost 'roles'
Last modified: 2013-03-12 15:46:05 PDT
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.
Allow for Journal Managers to create non-user user accounts for the purposes of enrolling people who are associated with the journal, but who don't have an email; or don't want to enroll; or don't want to get email; or never had email to begin with.
-- When creating a new user, JMs only (ie., not new self-registrants) should be able to bypass the mandatory email requirement eg. by checking off a box that states "this is a non-active (no email) account);
-- This should also be an option in the User Import plugin, and in the Issues & Articles plugin (I'll note that there's a difference here between user-level information and article metadata information, respectively).
-- If a user doesn't have an email, any email link (eg. the email button on their biography page, accessible from the Masthead; or the Email Author link from the RST) should be disabled or nonexistent.
This will still allow JMs to 'enroll' inactive users for populating the Masthead etc. (& will still encourage filling in user information if these users become active at a later date). It will also make back issue importing easier (esp. in the case where authors from way back didn't have email information to begin with). The current workaround is to add a garbage email address, but I don't think this is the best way to go about it.
This may have been filed somewhere, but for the life of me I can't find a record of it.
(Courtesy of http://pkp.sfu.ca/support/forum/viewtopic.php?f=2&t=4682&p=18218#p18218 and others)
One option that might be simpler to implement at first, would be to allow a role to be just a static text field. Fill it the way you like it. No need for user accounts altogether.
I haven't look at the tables yet, but I guess that a simple flag indicating the user is a ghost in the "roles" table and a new table with just IDs and Names columns would suffice to do the work. For the interface, just a button to add a "Ghost Role", and then just render each user of the page according to the flag mentioned above.
Created attachment 2110 [details]
unified diff against OJS 2.2.3
Jason, what about simply letting the email field be optional? We'd need to check a few places to make sure that blank emails are handled properly, but using "none" is anglocentric.
Jason's attachment doesn't seem to work for me. The first user created with an email address of "none" proceeds as expected, but additional ones return an error of "The selected email address is already in use by another user." (I needed to apply the diff by hand, and may have made a mistake doing so. Let me know if that looks to be the case.)
Scheduling against 2.3.5. This one continues to be fairly highly requested.
Could we have the option to link to a static page with the information for the Editorial Team. We have cases where the editorial team changes every year - especially with student journals.