Columbia
Escutcheon Columbia University Libraries Digital Program
Eresources: RTI Migration

          Path: Digital Library Projects  :  EresourcesRTI Migration : Specs & Mockups

Selector Review Page Spec ( 8/17/2004)

See also: Selector Review Page Sample Mockups

Each "Selector Review Page" has the following components: Filename, Header, Banner, Server-side include, Body, Footer.  Specifications for each section follow. Selector review pages should be uploaded to SWIFT at: /www/data/cu/libraries/inside/working/rti_review/

NB: Unless otherwise indicated, tags & indicators are always deleted before outputting source data; the first-occuring subfield code in each field is deleted; subsequent subfield codes are replaced by spaces.


1. Filename. The filename is derived from the 001 of the corresponding incoming CLIO record. For example:

CLIO 001 = "1671254"
More Info Page filename = "1671254.html"

2. Body.  The Body section is composed of two parts:

  1. A boilerplate paragraph, as follows:

    Elements in "red" below reflect bibliographic data elements in CLIO for which selectors may recommend additions or changes via the CLIO / Eresource Update Form. This type of form would be re-generated for all E-Reference resources each time CLIO records are extracted for use in the LWEB Eresources application (probably weekly).

  2. A set of displays derived from data elements in the corresponding CLIO record.  The full set of possible data elements is listed in the table below. Note that not all data elements will occur in each record; in such cases, no display text or label is generated. Some data elements may occur more than once; detailed instructions on handling these are found in the table below.  Mockups of displays formulated more or less according to these specs are linked from the Specifications and Mockups page.
Element
Name
  Bibliographic Data
CLIO
Field
CLIO ID
 
  • Get CLIO 001 (NR)
001
CU URL
 
  • Get each 856 (R) subfields $u and $z
  • Output the content of each 856 $u and $z on a new line, preceding any $z an an en-dash '–'
  • Convert each $u into a URL using the text of the URL as the anchor
856 $u
Title
 
  • Get CLIO 245 (NR) subfields $a, $b, $f, $n, $p content (only)
  • Format as single paragraph
  • Replace $b subfield code with space-colon-space if not already present in the data
  • Output as bold
245
Alternate
Title(s)
 
  • Get each CLIO 246 (R) with IND1 = 1 or 3 (only), subfields $a, $b, $f, $n, $p content (only)
  • Output each repeated 246 content on new line
246
Menu
Caption
 
  • Get CLIO 969 (NR)
  • Output content
969
Description
 
  • Get CLIO 520 (R) field content
  • Format each repetition of 520 as single paragraph
520
Subject Keywords
 
  • Get CLIO 653 (*NR) field content
  • Format all repetitions of subfield |a into a single paragraph
  • Replace all subfield codes $a after the first with ", " (i.e., comma, space)
653
LC Subject Headings
 
  • Get each CLIO 600 (R), 610 (R), 630 (R), 650 (R), 651 (R)
  • Replace all subfield codes except $a with an en-dash '–'
  • Output each repeated 650 or 651 on a new line
600,610, 630, 650, 651
LC Subject Category
 
  • Get each CLIO 050 (R) $a
  • Translate each 050 $a into text using the display equivalents at:
    [to come]
050
Selector Subject Categories
 
  • Get each CLIO 967 $a
  • Translate each code into text using the display equivalents at:
    [to come]
967
Resource
Type(s):
 
  • Get each CLIO 966 field, subfield $a;
  • Translate each code into text using the following display equivalents:
    ar = "Archival resource"
    bi = "Biography"
    bc = Book Collection
    ct = "Catalog"
    di = "Dictionary"
    dr = "Directory"
    en = "Encyclopedia"
    ft = "Full-text resource"
    im = "Image collection"
    ia = "Indexing & abstracting service (Check CLIO to locate indexed publications)" [NB: URL to CLIO included]
    jc = "Journal collection"
    ma = "Maps, atlases, etc"
    nw = "News & current events"
    nu = "Numeric database"
    sg = "Subject guide"
    sr = "Sound recordings"
    wb = "Website"
  • Begin the display text for each code on a new line
966
Coverage, Updates
 
  • Get each CLIO 362 (R) field, subfield $a only; Get CLIO 310 (NR) field, subfield $a (only)
  • Precede each field's content after the first with a space, en-dash ("–"), space
  • Format as a single paragraph
362
Contributors, Sponsors, Providers
 
  • Get each CLIO 110 (NR) and 710 (R) field, subfields $a and $b (only)
  • Output the content of each repeated 110/710 on a new line
110/710
Notes
 
  • Get each CLIO 546 (R) $a and 500 (R) $a present, EXCEPT any 500 field that begins: "$a Title from Web page" [...]
  • Format all 546, 500 fields into a single paragraph, preceding the content of each except the first with a space, en-dash ('&#150'), space.
500, 546
Access Restrictions
 
  • Get each CLIO 506 (R) field, $a (only)
  • Output each repeated 506 on a new line
506

Change log:

  • 8/30/04:  URL -- modified to include $z
  • 8/27/04:  LC Subject Headings -- Added 600, 610, 630
  • 8/27/04:  Contributors, etc. -- Added 110 field

 



3. Footer. The footer consists of: boilerplate code (to be supplied by Dmitri)

 


Columbia Libraries    Digital Program
Last revision: 08/17/04
© Columbia University Libraries