[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: Phil Davis <pmd8@cornell.edu>
- Date: Fri, 19 Nov 2004 12:21:19 EST
- Reply-to: liblicense-l@lists.yale.edu
- Sender: owner-liblicense-l@lists.yale.edu
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 At 09:46 AM 11/19/2004 -0500, Sally Morris \(ALPSP\) wrote: >When I was an active publisher, we didn't do this for 'load balancing' but >occasionally a paper which was not really suitable for one journal might >be redirected (with the author's agreement) for consideration by another > >Sally Morris, Chief Executive >Association of Learned and Professional Society Publishers >E-mail: chief-exec@alpsp.org > >>Chuck Hamaker wrote (in part): >> >> >>Do some publishers practice load balancing--where content submitted to one >>journal is passed to editors of a different journal who are running short >>on submissions? The incentive to keep publishing schedules especially >>since we all prepay subscriptions could be very strong. I don't know that >>this happens, but then how would we know unless publisher's state their >>policies clearly and provide auditable tracks?
- Prev by Date: Re: scholar.google vs Scirus
- Next by Date: Re: Google Scholar: Any Comments?
- Previous by thread: RE: Load balancing
- Next by thread: Re: Load balancing
- Index(es):