A. Selection & Sorting

1. Select for output all MMF records that are considered to be ejournals
   
   
2. Create separate subsets for all items in the same subject category, i.e., having the same:
   
   Classification_Mapping_Table --> classification_mapping_ID
   
   
3. [For items having more than one associated subject category (i.e., multiple "classification_mapping_IDs" created from multiple 050/090 fields in CLIO or input manually), create an identical entry in each corresponding subject category group, so that the item is found in each appropriate subject locations -- to come]
   
   
4. Generate single output page for each subject subset, with entries on each page sorted alphabetically by the Title Element (see B below), and subsorted by Publisher (i.e., Name-->Name element with role="pub"???)
   
   
5. Generate a single citation for each ejournal record, except see Detailed Record processing (section X below)
   

B. Data Element Definitions

C. Schematic List Output

<DL> <DT>["Subhead"]         <DD>["Link"+ "Title"] — ["Imprint"] — ["ISSN"]                  <BR>Bookmark as: [Link + "Link text"] — ["CLIO Backlink"]                  <BR><BR>         <DD>["Link"+ "Title"] — ["Imprint"] — ["ISSN"]                 <BR>Bookmark as: [Link + "Link text"] — ["CLIO Backlink"]                 <BR><BR>         <DD>["Link"+ "Title"] — ["Imprint"] — ["ISSN"]                <BR>Bookmark as: [Link + "Link text"] — ["CLIO Backlink"]                <BR><BR>      [Etc.] </DL>

D. Markup Specification

1. <DL><DT><DD> notation is used for the list, as shown in the schematic above
2. <H3></H3> is used for the Subhead, which occurs once at the beginning of each page
3. <B></B> is used for the Title Element.
4. If "Imprint" or "ISSN"element is present (i.e., is non-null), precede with space, em-dash (i.e.,   &#151 ), space; if element is not present, do not insert corresponding em-dash
5. Insert eye-legible anchor & link for Resolver-Type URL
6. Insert CLIO Backlink

E. Page Layout

• Insert headers, footers, etc. per instructions in "boilerplate.html"
  
  
• Enclose content of each page in a single table with the following attributes:
  
  
  • ROWS="1"
  • COLS="1"
  • WIDTH="640"
  • BORDER="0"
  • CELLSPACING="0"
  • CELLPADDING="2"
  • CLASS="lmargin5"

e.g.,

<TABLE ROWS="1" COLS="1" WIDTH="640"BORDER="0" CELLSPACING="0" CELLPADDING="2" CLASS="lmargin5">
<TR>
<TD>
[Page content]
</TD>
</TR>
</TABLE>

F. Special Processing for Records Having Multiple URLs

Records that meet the requirements for inclusion in this output set having more than one URL (Part_Presentation.url) are handled as exceptions, as follows:

• As indicated in Section B above, the "Link" element is constructed from the CLIO Record Key (MMF cu001), e.g.,
  
  <A HREF="detail/ank2942.html">Title</A>
  
  
• The presence of multiple URLs must also trigger the creation a file that includes the corresponding "Detail Record", e.g.,
  
  /ejournals/names/detail/ank2942.html
  
  
• Specifications for creating "Detail record" record pages are in a separate document.
  

G.  File Names, Directories, Shells & File Management

[to come]

H. Sample Output

• Mockup of output for Subject Listings
• Mockup of output for "Detail Pages"

I. Revision Log

7/10/2001:  Spec changed to add "class=lmargin5" to framing table spec. (Needs fixing?)
7/10/2001:  Spec changed to add "Subhead" & "Backlink" specs