Instructions to authors
Click here to view the following page as a Word Document.
To save to disk: 'Right Click' and select 'Save target as'.
Title: Please keep to less than 10 words. Use a colon if you want a subtitle.
Full papers: Friday 12th March 2004 max (4000 words)
Abstracts for concise papers: Friday 12th March 2004 (paper max 2000)
Accepted papers final version: Wednesday 12th May 2004
One page text for posters: Wednesday 12th May 2003
1st Author
First author's affiliation
1st line of address
2nd line of address
1st author's email address
2nd Author
Institution if different
3rd Author
Institution if different
ABSTRACT
In this paper, we describe the formatting guidelines for the 2004 NACCQ Proceedings.
The proceedings are the records of the conference. NACCQ hopes to give these
conference artefacts a single, high-quality appearance. To do this, we ask
that authors follow some simple guidelines. Send papers to Samuel Mann smann@tekotago.ac.nz
by March 12 th /May 12 th for review by the editorial panel. See you in Christchurch.
Please note: The abstract is not the start of the introduction. It should
be able to be read independently of the paper, and the paper independently
of it.
Keywords
Guides, instructions, authors kit, conference publications.
1. INTRODUCTION
This year again we are
going for simple. The proceedings will be produced using publishing software,
not MS-Word. Please feel free to use Word to write and submit but be aware
that it will be saved as “text only” before being reformatted.
This means NO WORD-ART, floating pictures, embedded anything, page numbers
or seemingly random page/section styles.
All papers should be high quality original work.
The ‘introduction' should
state the nature of the work, introduce any premises underlying the paper's
content, cite relevant previous similar work (whether by the author(s) or
others) and give the reader some idea of what to expect in the following
sections of the paper. Subsequent sections should be structured according
to the nature of the material. A conclusion or summary section should be
included.
Please remember the theme
for this year's conference is “Change, Progress
and Innovation in Technology”.
Within this theme, three areas will be run:
- Computing
education
- Computing
practice
- Computing
research
It would be good if your paper could make use of these concepts. Perhaps use
them as a starting point for developing the context for your research question.
1.1 Full paper
The paper should be a maximum of 4000 words and no more than eight formatted
pages (all inclusive). Yes I know you don't know how long it will be when formatted,
use last year's formatting as a guide. We will let you know if it is too long.
Keynote and Invited speakers should also follow these guidelines. Papers to
be considered for full paper should be submitted in full by 12 th of March.
Final versions due by 12 th May.
Full papers are double-blind refereed on submission by a review panel and
accepted/modified/rejected. Final versions are reviewed by editorial panel.
They may be rejected at that point.
1.2 Concise paper
We are also accepting “concise papers”.
The paper should be a maximum of 2000 words and no more than four formatted
pages (all inclusive). The abstract of the paper should be sent by 12 th
March.
Concise papers are reviewed on abstract by review panel. The completed papers
are reviewed by editorial panel and may be rejected or returned for modification
at that point.
1.3 Poster and demonstration papers
These follow the same guidelines but are limited to one page total. Guidelines
for the posters themselves are on the NACCQ website.
1.4 Panel papers
If you have been asked to contribute to a panel, you may have also been asked
to contribute a paper. You will have been informed as to the required length
of that paper.
2. SECTIONS
The heading of a section should be in all-capitals. Sections and subsequent
subsections should be numbered accordingly. Please make sure that you are not
using the headings as part of the sentence. It should still make sense without
the headings.
2.1 Subsections
The heading of subsections should have only the initial letters capitalised.
(Note: For subsections and subsubsections, a word like the or a is not capitalised
unless it is the first word of the header.)
2.1.1 Subsubsections
The heading for subsubsections should also have initial letters capitalised.
2.1.1.1 Subsubsubsection
The heading for subsubsubsections should also have initial letters capitalised.
2.1.1.1.1 Subsubsubsubsection
The heading for subsubsubsubsections should still have initial letters capitalised.
Ask yourself though, do I really need five heading levels?
2.2 Numbering and Bullets
There are styles given for numbering and bullet points.
To make a numbered list,
please put an where the number should
go:
a really interesting
point
another really
interesting point.
If you want bulleted points,
please use where the bullets should
go:
a bulleted item
another bulleted
item.
2.3 Title and Authors
The title, authors' names
and affiliations and contact details of the first author. In the interest
of saving space and formatting effort, please only put the institutions for
other authors where from separate departments or institutions. If you want
us to put “Dr” in
front of your name, please include it (assuming you are one of course!).
2.4 References and Citations
Use a standard author-date referencing. See the examples of citations at the
end of this document.
References should be published
materials accessible to the public. Internal technical reports should be
cited only if they are easily accessible (i.e. you can give the address to
obtain the report within your citation) and may be obtained by any reader.
Proprietary information should not be cited. Private communications should
be acknowledged, not referenced (e.g., “[Robertson, personal
communication]”).
2.5 Paragraphs
Please don't put extra paragraph marks between paragraphs. We'll only have
to take them out. To improve readability during writing may we suggest using
styles to add space after paragraphs (as is done here).
• Footnotes
Please don't use footnotes.
• Italics
Please avoid using italics.
If you really must, please indicate words to be italicised with a markup:
such as this .
But please use sparingly.
3. FIGURES/CAPTIONS
Figures may be used to
illustrate points made in the text and must be referred to. You should also
say what it shows, there's not much point in having a graph and saying “the graph clearly shows the results”. Don't let the reader get
it wrong: say “the students were clearly satisfied with the supply of strudel,
this is shown in Figure x”.. Also, just refer to the figure, don't say the
figure above, below, to the right etc, (hint: we move things to make them fit).
Figures should be sent as accompanying gif or jpeg files. It should be called
firstauthorfig1 (replacing firstauthor and x as appropriate). In the text,
as close to the reference as possible, place a marker showing the number, caption
and filename as follows:
[Figure 3. The positive relationship between the student and the learning
experience can be clearly seen. Joycefig3.gif]
While we intend relatively
high quality printing, please keep photographs to a minimum and ensure they
are high contrast. We will be using black and white although colour may be
used for digital representation (the proceedings will also appear on the ‘web).
Please don't use very large graphics that take up more than one page, while
we try to accommodate these, the outcome often looks a bit silly.
4. TABLES
Please send tables tab-delimited, in the text. If it is not obvious how it
should be reconstituted, please also include a word file with the table complete,
and reference the file as per figures. Tables should also have captions as
above.
5. CONCLUSION
Final versions of papers should be sent to smann@tekotago.ac.nz by May 12th
for review and formatting. Please contact Samuel Mann (Otago Polytechnic 03
479 6196) if you have any difficulty with these instructions. Please save your
file with the first author's name and one word identifier (I can get in a real
muddle with 90 something variations on naccq.doc) ie. Joyce_assessment.doc
5.1 Conference
You will be allocated 25
minutes for full papers and 15 minutes for concise papers. This should include
at least 5 minutes for questions. Panel times will vary but you can expect
around six minutes with more substantial discussion. Each venue will have
a Windows computer with PowerPoint and projectors (computer and transparency).
Please let us know as early as possible if you require anything beyond this
(Macintosh?, slide projector? Sound? Internet?…). A draft timetable
should be available in the month before the conference, again, please let us
know of any specific requirements.
This style paper is available
from this website ( http://www.naccq.ac.nz )
5.2 Awards
- Awards will be given at the Conference.
- Best written
full (judged by review panel and keynote speakers).
- Best written
concise paper (judged by review panel and keynote speakers).
- Best presentation
(voted by delegates)
- Best poster
judged by local committee
- CITRUS award
for collaborative research
- Award for
Educational Innovation (any paper or poster)
- Award for
Software Development
One last point. Please, please, please have somebody(s) else read your paper
before you send it in. While all papers are read and edited, we don't really
want to be proof-reading all the papers and may be rejected on these grounds.
6. ACKNOWLEDGMENTS
Our thanks to all authors that follow these instructions. We hope to produce
a quality document with a minimum of stress on all sides. The review committee
is made up of Samuel Mann (Otago Polytechnic), Alison Young (Unitec New Zealand), Noel
Bridgeman (Taranaki), Donald Koh (Unitec New Zealand), Tony Clear (AUT), Barbara Chamberlain
(Taranaki), Clare Atkin (NMIT), Donald Joyce (Unitec New Zealand), Krassie Petrova (AUT),
Janne Ross (CPIT).
7. REFERENCES
Anderson, R.E. (1992) “Social impacts of computing: Codes of professional
ethics”. Social Science Computing Review, 2(2):453-469.
ACM (1999) ACM SIG PROCEEDINGS
template. Accessed March 19, 1999.
System, G.I. and Access,
E.Z. (1998) “I made this one up”.
Proceedings of the NACCQ, Auckland, New Zealand, 4-7 July, pp 18-24.
