Bug 6881 - Make author metadata email requirement (or display) optional
Make author metadata email requirement (or display) optional
Status: NEW
Product: OJS
Classification: Unclassified
Component: General
2.4.x
All All
: P3 normal
Assigned To: PKP Support
: 6959 (view as bug list)
Depends on:
Blocks: 6959
  Show dependency treegraph
 
Reported: 2011-09-09 16:54 PDT by James MacGregor
Modified: 2012-08-09 10:39 PDT (History)
1 user (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 James MacGregor 2011-09-09 16:54:03 PDT
From Alec: Add a new setting to allow/prevent exposure of author emails. This might be best done as an author-level piece of metadata -- e.g. a checkbox beside each author's information on the Metadata Edit page that can be checked to expose the address. This would apply not just to the GS data, but also to the author information page (see Browse By Author), which currently doesn't expose emails. It could also replace the existing Reading Tools setting. For the sake of upgrades, we could default this checkbox to "false" to prevent accidental exposure of emails from before the change was made.

Juan: A new setting? I would rather we make a decision one way or the other, instead of crowding the author form with an extra checkbox.


Alec: Another option: move the GS metadata into a plugin. I have no problem adding extra setup fields when they're in plugin settings pages. Bozana is writing a similar plugin for OpenAire, IIRC.

Juan: I propose we make the field option in the DB schema, but force it on the author form. 

As for exposing the data, I really like the idea of it going in a plugin. With the setting being for all articles and authors (i.e. the Journal decides) 

(for further reference also see Bug 3636)
Comment 1 Alec Smecher 2012-08-09 10:38:58 PDT
Google Scholar would like author emails exposed using "citation_author_email".
Comment 2 Alec Smecher 2012-08-09 10:39:05 PDT
*** Bug 6959 has been marked as a duplicate of this bug. ***