|
Entry Compilation Guidelines
Elements of an Entry
HPM uses a Standard Generalized Markup Language (SGML) coding in order
to create defined fields of information. Documents created by independent
contractors must be tagged ASCII files that Gale editors can load
into an SGML Editor with predefined coding.
Our system uses the metaphor of a skeleton—comprised of a head,
body, and foot—to organize and group information. The following instructions
detail how to use the individual fields, what information should be included
within each field, and how information should be structured. Tags are
case sensitive; do not alter lower case letters.
Tagging System
Upon opening the template file, the coding may appear confusing and complicated.
However, a structure does exist to it. This document type can roughly
be divided into three parts: head, body, and foot. The head contains the
name of the entry, the body contains the guts of the entry, and the foot
contains further reading information. Below is a list of tips on keying,
and the codes are outlined in more detail in the tagging explanations
that follow.
Keying Tips
Do not use any word processing codes—including indents, tabs,
italics, bullets, boldface, etc. These will be lost when the files are
converted.
Do not use two spaces between sentences or after punctuation.
Do not alter the tags in any way.
Do not insert a space between tags and the information in them
(e.g., <superscript>3</superscript> NOT <superscript>
3 </superscript>).
Do not move tags around.
Do not make lists, graphs, or tables. If you feel that one of
these elements is essential to the entry, alert the editor in your "Notes"
file and it can be addressed in-house.
Do not type anything outside of the tags.
[Head information]
1. <title></title> = Title of the essay
Enter exactly as it appears in your assignment list.
Capitalize all words of a compound term, i.e., Hula Hoop.
2. <composed.name></composed.name> = Your name/The entire
name of the contributor writing the essay.
[Body of entry]
3.<doc.body>
<para>Paragraph</para>
<head n="1">Header 1</head>
<head n="2">Header 2</head> Headers 2 and 3 are
for use at your own discretion.
<head n="3">Header 3</head>
The body of the entry includes multiple paragraphs, heads, and subheads
as shown.
3a. <para></para> = Paragraph codes.
-Used to mark beginning and end of each text paragraph.
-There will be multiple para codes in a document.
-For italicized words, use <emphasis n= "1"></emphasis>
tags
3b.<head n="1"></head> = 1st level header code
-These are the rubrics included in your templates.
-There will be multiple header codes in a document.
3c. <head n="2"></head> = 2nd level header codes
-Code used for subheads beneath a 1st level header.
-There may be multiple 2nd level subhead codes in a document.
For example, under the Manufacturing header, you might have Creating the
mold and Assembly as 2nd level headers, as shown:
<head n="1">The Manufacturing Process</head>
<head n="2">Creating the mold</head>
<head n="2">Assembley</head>
3d. <head n="3"></head> = 3rd level header codes
-Code used for subheads beneath a 2nd level header.
-There may be multiple 2nd level subhead codes in a document.
For example, under the Creating the mold, you might have Heat molding
and Cold molding headers, as shown:
<head n="2">The Manufacturing Process</head>
<head n="2">Creating the mold</head>
<head n="3">Heat molding</head>
<head n="3">Cold molding</head>
[Foot]
4. <doc.foot><readinggroup><grouptitle>Where to Learn
More</grouptitle>
-Should appear once at the beginning of the resources section. No need
to alter.
-Please see the Science Style Guidelines included in the packet for specific
citations examples.
5. <grouptitle>Books</grouptitle>
<bibcitation><bibcit.composed>
<title></title>
</bibcit.composed></bibcitation> = Book sources for further
reading.
-Italic codes are NOT needed as title code connotes italicization.
-Multiple bibcit tags may appear under the book tag, as shown:
<grouptitle>Books</grouptitle>
<bibcitation><bibcit.composed>Smith, John. <title>How
to Make a Kite.</title> Somecity: Publishing Co., 1999.</bibcit.composed></bibcitation>
6. <grouptitle>Periodicals</grouptitle>
<bibcitation><bibcit.composed>
<title></title>
</bibcit.composed></bibcitation> = Periodical sources for
further reading.
-Italic codes are NOT needed as title code connotes ital.
-Multiple bibcit tags may appear under the periodical tag, as shown:
<grouptitle>Periodicals</grouptitle>
<bibcitation><bibcit.composed>Smith, Jane. "Kite Flying."
<title>Kite Magazine</title> (May/June 1999): 125—128.</bibcit.composed></bibcitation>
<bibcitation><bibcit.composed>"How to Build a Kite."
<title>Kite Magazine</title> 15 (June 1997): 6.</bibcit.composed></bibcitation>
7. <grouptitle>Other</grouptitle>
<bibcitation><bibcit.composed>
<title></title>
</bibcit.composed></bibcitation> = Websites, Videos, Audio
tapes or other sources of information.
<grouptitle>Other</grouptitle>
<bibcitation><bibcit.composed><title>How to Build a
Kite.</title> Videotape. Kite Association, 1994.</bibcit.composed><bibcitation>
<bibcitation><bibcit.composed>Smith, John. "How to build
a kite." <title>Kite Magazine Online</title> 1999 [cited
February 2002]. <http://www.kitemag/howto.com>.</bibcit.composed><bibcitation>
</readinggroup>
[back to Author Information
| back to top]
|
