Submissions

The deadline for submitting papers is now past (submissions closed on 2010-08-09) but posters and demos can still be submitted up to the deadline of 2010-09-13. Poster and demo submissions don't need to worry about the templates described below; go straight to the online tool at https://www.conftool.net/dcc2010/ and describe your submission.

If your poster submission is accepted you will be required to produce a poster for display at the conference.

Poster Specification

The ideal poster should be designed to attract attention, provide a brief overview of your work and initiate discussion. Posters need to be as simple and as clear as possible with an emphasis on graphics rather than text. Posters should adhear to the fololwing guidelines:-

1. A1 portrait or landscape (approximately 60cm x 80cm).

2. Your poster should be one piece and not made up of separate sections.

3. Finish: Laminate

4. Your poster should include title, author(s) names, affiliations, institutional logos, where appropriate,  and email addresses.

Important Dates

  • 1 September 2010 13 September 2010 - Final date for the submission of abstracts for poster/demos
  • 17 September 2010 - Notification to authors of papers
  • 1 October 2010 - Notification to authors of posters/demos/
  • 31 October Final papers deadline
  • 31 October Final posters deadline

Submission Template

The submission template should be used for Research and Practice papers.

Our template serves both as a means of formatting your submission and as an example of the required layout itself, providing a variety of examples in the complex area of citations and references.

Download the submission template [DOC,124KB] 

All submissions must follow the submission template.

Submit here (https://www.conftool.net/dcc2010/)

About our Submissions Template

The template for papers to be submitted acts as an example as well as a means of formatting a paper's content. The examples it contains do not cover all contingencies but provides a view of the most common usages. The examples begin their span with a reference to the Style used to generate it.


Although the text is 'greeked', it does provide extensive examples of how to cite in the author + date form, the citation year being used as an anchor to the corresponding reference list item. Note that in multiple citations, the order conforms to the order required by the References list, i.e. by author, alphabetical, same author plus others, alphabetical, and year.


The references examples are all prefaced by the type of entry, e.g. journal article, proceedings, book, and so on. Although the list is not exhaustive for sanity's sake, it provides coverage of most types. Editing will pick up any discrepancies beyond these examples, but it is very important that authors place the correct category of reference item in square brackets before each item, even though the References list's order is alphabetical as explained above. This will help editors to ensure formatting is correct. If, for example, the reference is to a message posted to an electronic mailing list, then enter [message posted to e-mail list] before the actual reference and editors will format the item.


Note the example of the footnote. Authors are encouraged to keep their references list clear of references to websites or notes of explanation, and so on. These are best accomplished by footnotes which appear at the bottom of the page in which they are anchored (see example). Note that URLs to websites should be prefaced by an English language title, if only the contents of the website's title tag for readers' ease of reference.


The selection of sub-headings structure has been confined to three levels. Generally speaking most authors seem content with two levels or three at most. Should you need to apply a 4th or 5th level, then it is important to contact us since this involves a complex change in the layout.


If you have any queries about the template or matters which, for the sake of brevity, it does not cover, then please contact ijdc@ukoln.ac.uk. 

The DCC is funded by

Joint Information Systems Committee