Article Submission Guidelines

File Format:MS Word
Default text Font:  Times New Roman
Default text Font size: 12
Computer output/Queries Font: Courier New
Computer output/Queries Font Size: 10

Word Count
We recommend that you use a guide of 850 words to a page and try to keep an article to a maximum of 4 pages. The word count needs to be reduced accordingly when including any code/tables/images etc.

If you feel a topic can't be covered in 4 pages then we ask that you consider whether it might be appropriate to split the article into two parts to be printed over consecutive issues.

All formats (e.g., italics) are taken directly from your MS Word submission - there is no requirement to follow the typesetting requirements set out by trade publications.

Any images/screenshots/diagrams etc must be supplied as separate files and notes placed in the article as to where they should appear. These files must be supplied in as high a resolution as possible, and preferably as gifs or jpegs.

For the sake of your readership, you should always begin with a summary of what your article intends to discuss/prove/identify and finish with a short conclusion of what was discussed.  Try to group your article by logical sections to ensure that you are not leaping back and forward, which can confuse the readers.  Also, if possible, try to ensure that there is a flow throughout the article.

We ask that before submitting an article you do the following:

  1. Check all instances where Word has put a green or red underline - this means you have either spelt something incorrectly, or your grammar does not make sense. (Although this does normally use UK spelling, so beware the "-ize" ending (US) - in the UK English we use "-ise").
  2. If possible, check any spelling that you are not sure about with the Oxford English Dictionary.
  3. Remove any long sentences - if in doubt it is always better to have 2 short sentences rather than one long one which may confuse readers.  It may sound more impressive as one long sentence, but please remember that readers may give up halfway through!


Other things to watch out for are:

  • Have you left out anything obvious?  Remember, it may be obvious to you but might not be to others (and it may actually make your article harder to read).
  • Accuracy - ensure your content is accurate and double-check any facts. If required seek relevant approvals before submitting an article.
  • Readership - remember that Oracle Scene has a varied readership ranging from senior managers through to technical and applications people.  Try to ensure where possible that the article can be enjoyed by as many people as possible.

Before Submitting an Article
Please check the following have been included in/attached to your submission :

  • Article Title
  • Author Name
  • Author Company
  • Contact Details – these will not be published they are in case we need to contact you
  • About the Author – max 50 word bio
  • Author Photo – supply separately and as high resolution as possible
  • Any Graphic/Image Files
  • Proof of relevant approval(s) where necessary


Editing Policy
AIOUG and the Oracle Connect team reserves the right to edit submitted materials or to use only portions of submitted materials. Edits may be for reasons of technical accuracy or completeness, AIOUG policy, readability, or consistency.

All submitted articles will under go review process by editorial team. Editorial team to determine which articles will be accepted for publication. There are three possible outcomes of the review process:

  1. Your article will be accepted for publication in the next issue. At this point, you will be notified via email to fill out and return a Copyright Permission form in preparation for publication.
  2. There are often too many articles for a given issue so your article may be placed on hold for consideration in a future issue.
  3. Your article is not considered appropriate for our user readership.
  4. Where necessary, articles will be edited to conform to our general style and to English best practice, and APA guidelines (See the following links for reference).

Author Eligibility and Compensation
Authors will not receive any financial compensation for the articles submitted.

Reprint of Articles

AIOUG has no restrictions on reprinting of this paper with other user group journals.

Quick Links

About Us

AIOUG is a non profit organization, provides Oracle technology and database professionals the opportunity to enhance their productivity and influence the quality, usability, and support of Oracle technology. For more details

Stay Connected on:


For general information about the event/conference, including registration, please contact us at:
  This email address is being protected from spambots. You need JavaScript enabled to view it.