International Conference on Information Systems for Crisis Response and Management Publications Format
|First author’s name Affiliation e-mail address||Second author’s name Affiliation e-mail address|
|Third author’s name Affiliation e-mail address|
In this document we describe the formatting requirements for the Proceedings of the ISCRAM2006 Conference for the following types of papers: full papers, research in progress papers, and case study reports – see the CFP for more information on these paper types. Note: position papers for Workshops can be submitted as unformatted 3-5 single page papers, yet we encourage authors to consider using this template as well for their position papers. Please review this document carefully. You can use this document as a template and copy/paste your paper content here (this might be the best or easiest way). Please be sure to adhere to the formatting requirements as this will ultimately be your camera-ready version, and a PDF format will be generated directly from your submitted final Word version. You can save a copy of this and delete what you are not going to use in the way of text and titles. The other option is to create a “document template” file (.dot) and it will become a style you can use for any word document. In that case you would remove all the text so it can be applied to an existing document.
Please note several limitations on length: (1) your abstract should be no more than 150 words, as the abstract will also be used for the conference program, (2) your entire paper should be no more than 5,000 words (full papers) or 2,500 words for research in progress papers and case study reports, including all materials and sections such as figures, tables, and references.
Guides, instructions, length, conference publications.
The accepted papers and the panel statements of the conferenceare published in the Proceedings. We wish to give the proceedings a consistent, high-quality appearance. We therefore ask that authors follow some basic guidelines. In essence, you should format your paper exactly like this document. The easiest way to use this template is to download it from the ISCRAM conference webpage and replace the content with your own material. The template file contains specially formatted styles (e.g., Normal, Heading, Bullet, Table Text, References, Title, Author, Affiliation) that will reduce the work in formatting your final submission.
Please adhere to the “letter” paper size only (hopefully Word or other word processors can help you with it). If you cannot do so, please contact the program chair for assistance. All final publications will be formatted and displayed in letter paper size. We are using left, right, top, and bottom margins of one inch. In addition, everything is left justified so it is easier to be read on a screen and text should be single spaced so that it is also easier to review on a screen. Beware, especially when using this template on a Macintosh, Word may change these dimensions in unexpected ways.
Prepare your submissions on a word processor or typesetter. Please note that page layout may change slightly depending upon the printer you have specified.
Title and Authors
Your paper’s title should be in Arial 18-point bold. Authors’ names should be in Times New Roman 12-point bold, and affiliations in Times New Roman 12-point
To position names and addresses, use a table with invisible borders, as in this document. Alternatively, if only one address is needed, use a centered tab stop to center all names and the address text; for two addresses, use two centered tab stops, and so on. If the single row cannot hold all authors’ information (for example, a paper has 4 or more authors), you can have another row under the first row.
Abstract and Keywords
Every submission should begin with an abstract of no more than 150 words, followed by a set of keywords. The abstract should be a concise statement of the problem, approach, and conclusions of the work described. It should clearly state the paper’s contribution to the field.
Normal or Body Text
Please use a 10-point Times New Roman font or, if it is unavailable, another proportional font with serifs, as close as possible in appearance to Times New Roman 10-point. On a Macintosh, use the font named Times and not Times New Roman. Please use sans-serif or non-proportional fonts only for special purposes, such as headings or source code text. Two blank spaces between sentences is preferred (but not enforced) for reading ease.
References and Citations
If you use EndNote, select “Information Systems Journal” style. In the text, cite by authors’ last names followed by the year of publication – list all authors’ last names for the first time, then use “et al.” for subsequent citations if there are more than two authors. If multiple articles are cited at the same time, order them alphabetically by the first author’s last name and separate the citations by semicolons. If the same author(s) has/have more than one articles being cited, use chronicle order and separate the year of publication of the articles by commas. For example: (Agarwal and Karahanna, 2000; Ajzen, 1988, 1991; Zhang, Benbasat, Carey, Davis, Galletta and Strong, 2002). Later in the paper, you may cite some of them again, along with others, as follows: (Agarwal and Karahanna, 2000; Ghani, Supnick and Rooney, 1991; Shneiderman, 1998; Tractinsky, 1997; Zhang et al., 2002). See examples on the references corresponding to these citations at the end of this document. Within this template file, use the References style for the text of your citations.
Your references should comprise only published materials accessible to the public. Proprietary information may not be cited.
The heading of a section should be in Arial 9-point bold, all in capitals (Heading 1 Style in this template file). Sections should not be numbered.
Headings of subsections should be in Arial 9-point bold with initial letters capitalized (Heading 2). (Note: for sub-sections and sub-subsections, a word like the or of is not capitalized unless it is the first word of the heading.)
Headings for sub-subsections should be in Arial 9-point italic with initial letters capitalized (Heading 3). Please do not go any further into another layer/level.
Place figures and tables close to the relevant text (or where they are referenced in the text).
Captions should be Times New Roman 9-point bold (Caption Style in this template file). They should be numbered (e.g., “Table 1” or “Figure 2”), centered and placed beneath the figure or table. Please note that the words “Figure” and “Table” should be spelled out (e.g., “Figure” rather than “Fig.”) wherever they occur.
The proceedings will be made available online, thus color figures are possible. However, you are advised to refrain from using colors to deliver important information in your figures – not everyone has access to color printers.
Occasionally MS Word generates larger-than-necessary PDF files when images inserted into the document are manipulated in MS Word. To minimize this problem, use an image editing tool to resize the image at the appropriate printing resolution (usually 300 dpi), and then insert the image into Word using Insert | Picture | From File…
As indicated in Figure 1, using tables to hold places can work very well in Word. If you want to copy a figure from another application (such as PowerPoint) and then paste to the place where you want your figure to be, make sure that (1) the figure stays in the position, and (2) it does not take up too much space. You can ensure the former by double clicking the figure, then go to “Layout” tab, and select “In line with text.” To ensure the latter, use “Paste Special,” then select “Picture.” You can resize the figure to your desired size once it is pasted.
Inserting a table in the text can work well. See Table 1 below. The text of tables will format better if you use the special Table Text style (in this template file). If you do not use this style, then you may want to adjust the vertical spacing of the text in the tables. (In Word, use Format | Paragraph… and then the Line and Page Breaks tab. Generally, text in each field of a table will look better if it has equal amounts of spacing above and below it, as in Table 1.)
LANGUAGE, STYLE AND CONTENT
With regard to spelling and punctuation, you may use any dialect of English (e.g., British, Canadian, US, etc.) provided this is done consistently. Hyphenation is optional. Since this year the meeting is in the US it would be nice to the US dictionary but we will not enforce that.
To ensure suitability for an international audience, please pay attention to the following:
- Write in a straightforward style.
- Try to avoid long or complex sentence structures.
- Briefly define or explain all technical terms that may be unfamiliar to readers.
- Explain all acronyms the first time they are used in your text – e.g., “Digital Library (DL).”
- Explain local references (e.g., not everyone knows all city names in a particular country).
- Be careful with the use of gender-specific pronouns (he, she) and other gendered words (chairman, manpower, man-months). Use inclusive language that is gender-neutral (e.g., she or he, they, s/he, chair, staff, staff-hours, person-years).
|Treatment 1||Treatment 2|
|Table 1. A Very Nice Table|
Page Numbering, Headers and Footers
Please submit your final version with the pre-defined header and footer. Insert your name (only the first author’s last name, and use “et al.” after that if the paper has more than one author) and a short title of your paper in the header. Leave the footer untouched. Page numbering is already part of this template and should be left in that format.
It is important that you write for the general audience. It is also important that your work is presented in a professional fashion, which is what this guideline is intended to help you with. By adhering to the guideline, you also help the conference organizers tremendously in reducing our workload and ensuring impressive presentation of your conference paper. We thank you very much for your cooperation and look forward to receiving your nice looking, camera-ready version!
We thank all authors, program and local committee members, and volunteers for their hard work and contributions to the ISCRAM2006 conference. The layout of this format was originally adapted by Bartel Van de Walle for the ISCRAM2005 conference in Brussels from a workshop document template created by Ping Zhang. Thank you Ping for your kind permission to use your template. Slight changes have been made by Murray Turoff for ISCRAM 06 in Newark NJ. The references cited in this paper are included for illustrative purposes only.
- Agarwal, R. and Karahanna, E. (2000) Time Flies when You’re having Fun: Cognitive Absorption and Beliefs about Information Technology Usage, MIS Quarterly, 24, 4, 665-694.
- Ajzen, I. (1988) Attitudes, personality, and behavior, The Dorsey Press, Chicago.
- Ajzen, I. (1991) The theory of planned behavior, Organizational Behavior & Human Decision Processes, 50, 2, 179-211.
- Ghani, J. A., Supnick, R. and Rooney, P. (1991) The experience of flow in computer-mediated and in face-to-face groups, Proceedings of the Twelfth International Conference on Information Systems, New York, NY.
- Shneiderman, B. (1998) Designing the User Interface – Strategies for Effective Human-Computer Interaction, Addison-Wesley.
- Tractinsky, N. (1997) Aesthetics and Apparent Usability: Empirically Assessing Cultural and Methodological Issues, Proceedings of the CHI 97, Atlanta, GA.
- Zhang, P., Benbasat, I., Carey, J., Davis, F., Galletta, D. and Strong, D. (2002) Human-Computer Interaction Research in the MIS Discipline, Communications of the AIS, 9, 20, 334-355.