Journal of Water Engineering and Management accept proposals for
Special Issues thrice in a year. The closing dates are 31st March, 31st
July and the 30th November each year. This guidelines will help you to
understand the duties and responsibility of a Guest Editor and the process
of publishing a Special Issue in JWEAM.
Being a Guest Editor, you need to publish a Special Issue which requires
to manage and develop good rapport with Co-Editors, Authors, Reviewers,
publisher and Editor-in-Chief of JWEAM. All Guest Editors should have
sufficient experience and sound publishing record.
Developing Proposal: Your proposal should include:
- Abstract
- Justification for publication of the Special Issue
- Relevance and suitability for JWEAM
- Timeline for each publication stage
- List of probable contributors including email addresses
- CV of the proposed Guest Editors, including editorial experience.
Special Issues may be the result of an open call for papers or from a
conference proceedings. Proposal may be mailed to Editor-in-Chief at
<eic@jweam.in> who will later circulate the proposal among the Editorial
team for their evaluation and feedback. Once your proposal is approved,
publication may take one to two years after the submission deadline. This
duration may change depending on your progress, and that of other
Special Issues in the pipeline. A JWEAM Editor will be assigned to provide
all kind of help and support on your Special Issue.
Later you will be requested to draft a ‘Call for Papers’ and sent by email it
to Editor-in-Chief<eic@jweam.in> for approval by Managing Editor and
Publisher. Once approved, your ‘Call for Paper’ will be added to the
JWEAM website and circulated among journal network. This point onward,
you need to begin promotion of your Special Issue. Once the Special
Issue is published, pdf copies of the Special Issue will be made available
to up to contributors endorsed by the Guest Editors.
Process
The Guest Editor(s) will have full responsibility for processing the
manuscript including identifying reviewers and corresponding with
reviewers and authors. We can offer advice as and when required. Please
note that when your proposal is approved, we are giving you the authority
to develop a Special Issue under the auspices of JWEAM. Your all work
must reflect the JWEAM logo and its name. To conform to JWEAM policy,
submissions must include a completed submission checklist (available on
the JWEAM website), and papers must be checked for plagiarism before it
is sent for review. Papers should be sent for review to at least two people,
using a double-blind peer review process.
Guest Editor (s) is expected to acknowledge receipt of all the papers the
same day, or the next working day, and let authors know the first
decision (reject/out for review/revise before review) within a week of
submission. You should aim to have the first decision to authors within
two months. Guest Editors should send the copies of papers they have
conditionally accepted to JWEAM Editors for reviewing the papers prior to
formal acceptance. This is an editorial procedure we follow in our review
of all manuscripts that reach an advanced stage in the review process at
JWEAM. As such, please note that papers cannot be accepted without the
JWEAM Editors’ approval. Please take this into account in your
communications to authors, and do not write final acceptance letters until
the JWEAM Editorial team has provided feedback. The authors will be sent
electronic notification that their proofs are ready and will have 3 days to
reply to the publication team with corrections. When the accepted papers
are received by our publication team, we may ask for Copyright Transfer
form. The JWEAM takes manuscript publication charges.
Note
The Special Issues normally contain fifteen to twenty papers along with
editorial remark from the Guest Editors (which may be full length paper).
This means that you must secure 50-60 submissions to get a good
number of quality papers to constitute a full issue.
If you have any queries, please contact Editor-in Chief <eic@jweam.in>.