370 likes | 405 Views
Scientific Communication CITS7200. Lecture 8 Publishing. Types of publication. Conference papers Journal Articles Book Chapters All part of the Australian Government audit administered by DEST. Conference publications. Common refereed venue for CS and SE Fast turnaround
E N D
Scientific Communication CITS7200 Lecture 8 Publishing
Types of publication • Conference papers • Journal Articles • Book Chapters All part of the Australian Government audit administered by DEST
Conference publications • Common refereed venue for CS and SE • Fast turnaround • National and international • Counted in UWA output audit
Choosing the conference • Costs (registration, travel, accommodation) • Venue • Size • Prestige • Degree of specialisation • Attendees
Unrefereed conferences (e.g. Yanchep) • Refereed abstracts • Refereed full papers (e.g. ACSC) • Oral Presentation • Poster Presentation
Camera-ready copy • Template usage
ACSC2003, Adelaide January • Electronic submission of papers is preferred (in postscript, pdf or Microsoft word formats). • Confirmation of receipt will be given, in the case of a postscript submission, once the file has been successfully printed. Submitted papers (and camera-ready copy for accepted papers) will be required to conform to the formatting guidelines of the series Conferences in Research and Practice in Information Technology. A sample Word style file, LaTeX style file and LaTeX document are available. • Authors are reminded that a 10 page limit applies to all submissions. Papers exceeding 10 pages in length may be rejected. • Papers will be judged on originality, significance, correctness and clarity. The contribution of the paper should be clearly explained in both general and technical terms. Any paper should not be submitted to more than one of the conferences in ACSW. Papers must include the author's name, affiliation, address, E-mail address, a 200-word abstract and 3 to 6 keywords identifying the subject area.
DICTA2003, Sydney December • Prospective authors are invited to submit their full papers electronically at the conference web site (http://www.tip.csiro.au/dicta2003 ) before 11 August 2003. • Papers are limited to a maximum of eight (8) pages. Authors of accepted papers, or at least one of them, should be registered and are expected to present their work at the conference. • The conference proceedings will be available at the conference in paper and CD forms. Papers will also be available on the web. • Authors of best papers will be invited to submit revised versions of their papers to be considered for publication in a special issue of the Image and Vision Computing journal published by Elsevier.
Journal publications • Types of articles • Full length articles: typically 5000 words, a series of experiments • Short notes: typically 2000 words, one or two stand-alone experiments • Generally, one solid paper is better than two or three short notes • Articles in journals are better than chapters in books
Choosing your journal • Choose a good quality, high prestige, international journal for maximum exposure • Journal of the ACS is JRPIT – Journal of Research and Practice in Information Technology
Quality is often measured by a journal’s Impact Factor, which is a measure of the average number of citations made to articles published in the journal • B = 1998 citations to articles published in 1996-7 • C = number of articles published in 1996-7 • 1998 Impact = B/C
Seek advice on where to publish • Review recent issues to see if your topic matches contents • Examine the references section in your paper for common journals • Check time-to-publish
Submitting a paper • Follow instructions • Use correct format or template • Provide correct number of copies • Include required info in covering letter
People involved: • Managing Editor (deals with administration) • Editor (selects reviewers; makes final decision on acceptance) • Reviewers (experts in the paper topic)
Reviewing • Is the paper too long? • Is the paper well organised? • Are the design and analysis sound? • Do the conclusions follow from the results? • Has the author cited all relevant references? • Are all the tables and figures necessary? • Are the title and abstract fully descriptive of the text?
JRPIT reviews • Technical content (1-5) • Originality (1-5) • Writing quality (1-5) • Appropriate to JRPIT (1-5) • Overall assessment (1-5) • Comments to authors • Comments to editor
Possible recommendations: • Accept with few or no revisions • Accept provided that revisions are carried out according to the reviewers’ (and/or editor’s) specific comments • Reject but allow re-submission after major revision • Reject
Revising your paper • Check the time limit • Write a cover letter addressing ALL reviewers’ comments • Don’t attack the reviewer or the editor • Don’t be intimidated by either • Stand up for your viewpoint if you think you are right
Re-submitting your paper • Follow instructions carefully • Proof-read carefully • Generate high-quality laser copies • Date your work
unmatched parentheses, • wrong fonts, • misspelt words, • repeated words, • missing punctuation, especially commas, • incorrect hyphenation, • a widow header or word, • O for 0, l for 1, etc. • bad line breaks in mathematical equations, • incorrect formatting, • missing symbols, • errors in numbers in tables, and • incorrect citation numbers
Proofs • Unless using a typesetting template, galley proofs arrive shortly before publication • Cross-check carefully • Return within 24 hours! • Indicate precise changes in cover letter and on proofs using correct mark-up
Rejection • Acceptance rate is usually below 33% • Everyone gets rejected • Wait before trying again • Don’t be discouraged • Re-submit to another journal within a month
Good practice • Keep • a copy of your manuscript • a re-print • all reviewers’ and editor’s comments • Make sure you have all info for audit • Don’t give up • Start now • Make downloads available through web
Posters • Same amount of material as a ten-minute talk • Different from a talk or a paper • Visual presentation designed to stimulate discussion
Contents • Introduction and motivation • Outline of materials and methods • Results • Conclusions
A good poster is • readable • legible • well organized • succinct
Layout and design crucial • Check space constraints • Usually landscape with 1-2m2 , but sometimes portrait
Title, in sentence capitalisation Name — School of Computer Science & Software Engineering, The University of Western Australia Introduction Results Conclusions Literature cited (a) Materials and methods Acknowledgments (a) For further information (a)
Usually about 20% text, 40% graphics and 40% space • Must have right angles, straight lines, perfect spacing between entities • Plan your layout on paper first
Design • Use strong colour contrast • Muted colours best for background, strong colours for borders • Related background colours will unify the poster • Use light background with dark photos, dark background with light photos • Use neutral (grey) background to emphasize colour, and white to reduce colour impact
Images and graphs preferable to tables • Use professional tools • Guillotine • Spray adhesive • Design for reading
Sans serif fonts easiest to read • Section headings in Helvetica, Boldface, 36pt • Supporting text Helvetica, 24pt • Should be readable from 1m