[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Load balancing
- To: <liblicense-l@lists.yale.edu>
- Subject: Re: Load balancing
- From: "Sally Morris \(ALPSP\)" <chief-exec@alpsp.org>
- Date: Sun, 21 Nov 2004 16:15:39 EST
- Reply-to: liblicense-l@lists.yale.edu
- Sender: owner-liblicense-l@lists.yale.edu
It is standard practice to ask authors to certify that the paper has not
simultaneously been submitted to any other journal.
Sally Morris, Chief Executive
Association of Learned and Professional Society Publishers
E-mail: chief-exec@alpsp.org
----- Original Message ----- From: "Phil Davis" <pmd8@cornell.edu>
To: <liblicense-l@lists.yale.edu>
Sent: Friday, November 19, 2004 5:21 PM
Subject: Re: Load balancing
Sally (and other publishers on this list) Does your organization have mechanisms in place to make sure that articles are only considered in one journal at any one time? And, based on your experience as a publisher, what other process controls were set up to prevent article duplication? Chuck has raised a very important issue dealing with process control. While I'm sure that no other publisher wants to recreate what I've discovered in Emerald/MCB UP, a constructive discussion about what publishers can do to prevent a reoccurrence of this phenomenon has been missing. Emerald has publicly apologized for their actions but provide no details that things have changed in-house. --Phil Davis
- Prev by Date: RE: DATABASES: Google Scholar
- Next by Date: Re: Load balancing
- Previous by thread: Re: Load balancing
- Next by thread: Re: Load balancing
- Index(es):