|
![]() |
Style Sheet
Please note: The Journal welcomes inquiries as to all issues. There are several problems which confront an e-journal in particular which we have not solved. You will notice that some of the materials in the June issue do not conform to the following standards, because of many unforeseen problems which arose. However, it is our intention to enforce these standards in future editions.
All submissions must be in hard-copy and in disk copy. Disks should be clearly marked as to platform (IBM, MAC, etc.) to word processor used, and have on the label the author's name and address, including email. This information also should be included within a "README" file upon the disk. The README should also include a brief explanation of any and all files included upon the disk and/or a "tree" showing how the files relate to each other. Email requests as to our interests in particular submissions are welcome: barlowj@pacificu.edu and will be forwarded to the appropriate editor. Please indicate clearly whether you intend your submission for publication in the "Articles" section of the Journal, or as a "Work-in-Progress" as explained below.
Length: Hard-copy submissions should be no more than forty pages in length, double-spaced, including all notes and references.
HTML Formatting: If you wish to do your own HTML formatting, please inquire as to our ability to handle work done with a specific editor upon our server (MAC) before proceeding. In general, we prize clarity and organization of content over creative displays of formatting and technology, though we recognize the importance of graphic presentation within an electronic format. It is our goal to keep this journal accessible to the widest possible electronic audience while maintaining high professional standards. We reserve the right to reformat HTML materials according to our standards. Our standard font is "Arial" size 3. If you format in Arial 3 we will be able to maintain most of your lay-out in preparing your submission.
Notes and citations should follow the Chicago style. The submission should include notes and bibliography files formatted as individual documents rather than as one long document.
Anchors: If the text includes anchors or links to external sites, these should be included if at all possible in the bibliography or in an additional "Resources" file rather than imbedded in the text itself. While this may not be the optimum use of hypertext it will keep our readers from becoming lost on the web before they have finished reading in our site. You are responsible for testing addresses which are included in your file; we cannot search the web for 404s. This has proven to be a very serious problem for us, please take great care in testing your links!
Graphics: We encourage appropriate graphics to be included in submissions. However, these must be graphics to which you have clear rights of use. Legal responsibility for your work resides with you.
Abstracts: Each author must provide a one-paragraph (c. one hundred words) abstract of their submission. The abstract will lead off published pieces and will also be used in indexing and archiving the piece.
Notes for Reviewers: We are interested in reviewing any and all works related to the fields of history and computing. If there is a particular work, either published or electronic, which you wish to review, we encourage you to contact the appropriate editor. We will link your review both to your email address so that you might provide additional information to interested parties, and to any commercial sites maintained by the publisher.
ARTICLES: We understand a submission for the "Articles" section of the Journal to be finished pieces equivalent to those which one would submit to hard-copy professional journals in the fields of history or computing. They will be peer-reviewed by our editorial board with additional consultation where necessary. We will be pleased to provide letters useful for academic or other promotion processes testifying as to our support of your piece, and where possible we will comment upon audience response.
WORKS-IN-PROGRESS: We believe that an important function of a journal such as this is to provide a community of discourse for scholars who may be working in a relatively new field with little local support. We understand a submission to the "Works-in-Progress" section to be those for which the author genuinely invites thoughtful criticism. These might be viewed as a stage in the production of a more finished published piece, they might well be future conference papers, or any other piece for which the author seeks a peer response. Submissions for this section must be carefully proof-read and edited. They will be peer reviewed for inclusion in this section.
Published at Pacific University
Copyright American Association for History and Computing