Submissions

Online Submissions

Already have a Username/Password for Journal of Emergency Management?
Go to Login

Need a Username/Password?
Go to Registration

Registration and login are required to submit items online and to check the status of current submissions.

 

Author Guidelines

Manuscript Submission

To submit a manuscript, please go to http://jem.allentrack2.net. Click on "New users should register for a new account". After you register you will be able to click on a link to submit a manuscript, this will forward you to a page with instructions.

Editorial Policy

Journal of Emergency Management (JEM) will consider papers for publication related to research, theory, and current issues in emergency management. Specifically, JEM is positioned as a vehicle for academics and practitioners to share field research. In addition to scientific studies and program descriptions, we will also consider letters to the editor, guest editorials, and book reviews. JEM seeks to promote the accurate, efficient handling of publishable material. Individuals desiring to contribute should not hesitate to make inquiries, even if they are unfamiliar with procedures for writing and submitting manuscripts. The editorial staff is pleased to process and reply to any inquiries received. Our goal is to provide original, relevant, and timely information from diverse sources; to write and publish with absolute integrity; and to serve as effectively as possible the needs of those involved in emergency management. If your research will help us achieve these goals, we would like to hear from you.

Manuscript Submission

To submit a manuscript, please go to http://jem.allentrack2.net. Click on "New users should register for a new account". After you register you will be able to click on a link to submit a manuscript, this will forward you to a page with instructions.

Manuscript Format

Please be sure to turn OFF the track changes feature on all documents before submission. The cover page should indicate the article’s title, the full name, highest pertinent academic degrees, institutional affiliations, and current address of each author, contact information for the author handling all correspondence, telephone number, fax number, and, if the manuscript was orally presented at a meeting, the name of the organization, place, and date it was read. The first use of an uncommon abbreviation should be preceded by the full name. Brief definitions of key terms may be appended to the manuscript and can be presented in parentheses after the term within the article. With the exception of forum articles, book reviews, or letters to the editor, manuscripts should include the following five sections: Abstract, Introduction, Methods, Results, and Discussion. Subheads should be inserted at suitable levels. Style should conform to “Uniform Requirements for Manuscripts Submitted to Biomedical Journals” (available online at http://www.icmje.org).

Figures & Tables

The Journal welcomes illustrations, charts, and photographs to accompany articles. Figures should be titled and numbered consecutively according to the citation in the text. Information presented in figures and tables should be explained in the text. If data have been published previously, an appropriate reference should be included.

Short, descriptive legends should be provided on a separate page. Legends for figures previously published should include a complete reference to the original publication, with the copyright designation. Copies of the publisher's and author's permission to use the figure must be provided. Photographs should include legends and should be numbered consecutively according to the citation in the text and labeled on the back. Tables, photos, and figures must be submitted in the following formats: TIFF, JPEG, or EPS.

Manuscript review

Manuscripts are received with the understanding that they are submitted solely to Journal of Emergency Management and that, apart from abstracts, none of the material contained in the manuscript has been published previously or is under consideration for publication elsewhere. Authors should secure all necessary clearances and approvals prior to submission.

Journal of Emergency Management is a refereed journal. All manuscripts are generally subject to review by at least two members of the editorial advisory board who are noted experts in the appropriate subject area. The Journal reserves the right to make editorial revisions prior to publication.

All manuscripts are acknowledged immediately, and every effort will be made to advise contributors of the status of their submissions within 60 days.

References

References are organized in AMA format; that is, they are to be cited numerically in the text and in consecutive order, including the first three authors followed by et al., and listed at the end of the article in the following format:

Journal articles— 1. Mudd P, Smith JG, Allen AZ, et al.: High ideals and hard cases: The evolution of opioid therapy for cancer pain. Hastings Cent Rep. 1982; 12(2):11-14.

Books— 1. Bayles SP (ed.): Nutritional Supplements and Interactions with Analgesics. Boston: GK Hall & Co., 1978.

Book chapters— 1. Martin RJ, Post SG: Introducing alternative prescribing strategies. In Smith J, Howard RP, and Donaldson P (eds.): The Oncology Management Handbook. Madison, WI: Clearwater Press, 1998, pp. 310-334.

Web sites— Health Care Financing Administration: HCFA Statistics at a glance. Available at: www.hcfa/gov/stats/stahili.htm. Accessed December 27, 2002.

Ethics

Style should conform to “Uniform Requirements for Manuscripts Submitted to Biomedical Journals” prepared by the International Committee of Medical Journal Editors and published in Ann Intern Med 1997; 126: 36-47, and available on the web at http:www.acponline.org/journals/annals/01jan97/unifreqr.htm.

The Journal expects authors to disclose any commercial or financial associations that might pose a conflict of interest in connection with the submitted article. All funding sources supporting the work should be acknowledged on the title page.

All correspondence should be addressed to the Managing Editor, Journal of Emergency Management, 470 Boston Post Road, Weston, MA 02493.

 

Submission Preparation Checklist

As part of the submission process, authors are required to check off their submission's compliance with all of the following items, and submissions may be returned to authors that do not adhere to these guidelines.

  1. The submission has not been previously published, nor is it before another journal for consideration (or an explanation has been provided in Comments to the Editor).
  2. The submission file is in OpenOffice, Microsoft Word, RTF, or WordPerfect document file format.
  3. Where available, URLs for the references have been provided.
  4. The text is single-spaced; uses a 12-point font; employs italics, rather than underlining (except with URL addresses); and all illustrations, figures, and tables are placed within the text at the appropriate points, rather than at the end.
  5. The text adheres to the stylistic and bibliographic requirements outlined in the Author Guidelines, which is found in About the Journal.
  6. If submitting to a peer-reviewed section of the journal, the instructions in Ensuring a Blind Review have been followed.
 

Copyright Notice

Copyright 2007-2014, Weston Medical Publishing, LLC and Journal of Emergnecy Management. All Rights Reserved

 

Privacy Statement

Privacy and User Data Policy

GDPR Update:

The data collected from registered and non-registered users of this journal falls within the scope of the standard functioning of peer-reviewed journals. It includes information that makes communication possible for the editorial process; it is used to informs readers about the authorship and editing of content; it enables collecting aggregated data on readership behaviors, as well as tracking geopolitical and social elements of scholarly communication.

This journal’s editorial team uses this data to guide its work in publishing and improving this journal. Data that will assist in developing this publishing platform may be shared with its developer Public Knowledge Project in an anonymized and aggregated form, with appropriate exceptions such as article metrics. The data will not be sold by this journal or PKP nor will it be used for purposes other than those stated here. The authors published in this journal are responsible for the human subject data that figures in the research reported here.

Those involved in editing this journal seek to be compliant with industry standards for data privacy, including the European Union’s General Data Protection Regulation (GDPR) provision for “data subject rights” that include (a) breach notification; (b) right of access; (c) the right to be forgotten; (d) data portability; and (e) privacy by design. The GDPR also allows for the recognition of “the public interest in the availability of the data,” which has a particular saliency for those involved in maintaining, with the greatest integrity possible, the public record of scholarly publishing.

Requests per item (a) through (e) above should be sent to the journal's mailbox, jem(at)pnpco.com

The names and email addresses entered in this journal site will be used exclusively for the stated purposes of this journal and will not be made available for any other purpose or to any other party.

What Data does this Website Process?

 

The system, based the PKP Open Journal System applications, process personal data as a fundamental part of their operations. Most data is only provided by consent, ie. through manual user registration, though some visitation data (eg. cookies, usage logs) may also be recorded.

 

User Registration Data

 

When a visitor creates a user account in a PKP application, the following personal information is processed and stored (with some minor variation between OMP and OJS, and from version to version):

●   Salutation

●   First name*

●   Middle name

●   Last name*

●   Suffix

●   Username

●   Gender

●   Password (encrypted)

●   Email address*

●   ORCiD ID

●   Website

●   Mailing Address

●   Country

●   Phone

●   Fax

●   Affiliation

●   Biography

●   Registration date

●   Last login date

●   Locales

●   Reviewing interests

●   Role registrations (author, reader, and/or reviewer)

Only the username, first name, last name, email and password fields are required.

 

Storage

 

This information is stored in the application database. Only the user password

is encrypted.

 

Availability and Access

 

This information is available to the user via their User Profile (and, with the exception of the username and dates, can be edited). System administrators, journal managers, and editors can also access and edit this data (except the username and dates) via the application back end. The data can be downloaded by journal managers in XML format. The data is not otherwise publicly available.

 

Erasure

 

This data can be erased by the journal manager using the Merge Users tool, without affecting any editorial records. The erasure is subject to the considerations raised in the section “Scholarly Publishing, Data Privacy, and the Public Interest”, above.

 

Contributor Metadata Information

 

When a manuscript is submitted to a PKP application, contributor information is included. Contributors can be authors, translators, volume editors, and so on. This information is stored as submission metadata and is provided as part of any published manuscript record. The following contributor information is collected:

 

●   Salutation

●   First name*

●   Middle name

●   Last name*

●   Email address*

●   Suffix

●   ORCiD ID

●   Website

●   Country*

●   Affiliation

●   Biography

 

Only the first name, last name, email address and country fields are required.

 

Storage

 

This information is stored in the application database.

 

 

Data Transfer

 

We do not sell or transfer to third parties user information from this system.

 

General Visitor Information

 

PKP applications also collect general visitor usage data, including:

● Cookie information, to manage session history. Cookies are required to maintain a login session in PKP applications.

● Optionally, detailed usage log data, including: IP address; pages visited; date visited; and browser information, in application log files, as part of the Usage Statistics plugin. An anonymization option is available to privatize this information.

● Optionally, country, region and city information, in the metrics database. This data collection requires additional setup and is not enabled by default.

 

Other data may be tracked, either on the server or via third parties:

● Script loads from CDN servers;

● IP address information (including date, browser, etc.) in web server logs (separate from application log files as part of the Usage Statistics plugin).

 

Detailed instructions in limiting the amount of data you collect, and providing consent for the data you collect, can be found below.

 

Storage

Cookies: A cookie (usually titled “OJSSID” or “OMPSID”) is created when first visiting a PKP application and is stored on the visitor’s computer. It is only used to store a session ID, and to facilitate logins. (If the visitor blocks cookies, OJS will still work properly, though they will not be able to log in.)

Usage Statistics log files: As part of the usage statistics framework and plugin, OJS may store detailed application log files in the submission files directory (configured as the files_dir parameter in the OJS config.inc.php file), in a “usageStats” directory.

Geographical data: Filtered usage data, including possibly geographic data, is also stored in the OJS database, in a “metrics” table.

 

Availability and Access

Cookies: These are available via the visitor’s browser settings.

Usage Statistics log files: Only individuals with server file access can access application log files.

Geographical data: Journal Managers can access filtered usage data by using the OJS usage report plugins.

 

Erasure

Cookies: These can be deleted via the visitor browser.

Usage Statistics log files: These can be erased by system administrators with file access.

Geographical data: This can only be erased by deleting records from the database directly, which also typically requires system administrator access.

 

Portions of this privacy statement are copyright by Simon Fraiser University Licensed wth CC4.0-BY.

 

 
This site uses cookies to maintain session information critical to the user's experience and environment on this system. Click "Accept Cookies" to continue.
For more details please visit our privacy statement at: Privacy & GDPR