Columbia Escutcheon
Special Duke Conversion Processes
          Path:  APIS  :  APIS Documentation  :  Metadata  :  Duke Conversion 
NB: This document is to be used in conjuction with the Duke / APIS Conversion Data Map, which includes requirements for straightforward data conversions. More complex conversions (e.g., those involving multiple fields or data manipulation) are documented below.
  1. Coded Fixed Fields: Dates (cuDate_1, cuDate_2)

    Duke's APIS MARC records include standard 008 fixed field information.  Only three elements are used from this field in the APIS conversion:

       [008] 950223q00010099ua grc d

    IF DATES ARE NOT PRESENT IN AN 046 FIELD (SEE BELOW), GRAB DATES FROM 008 IF POSSIBLE

    NB: 008 Date 1 and Date 2 are from 008/8-11 and 008/12-15,

    .g. "940607q06000799" for 600-799 CE.

    Since In Duke records no 008 date is more than 3 digits so it is safe to grab 008/9-11 and 008/13-15, e.g., 600 & 799 rather than 0600 & 0799.

    Select e
    Locate for substr(oldtag,1,3) = "046"
    IF .NOT. FOUND()
      date1 = substr(cu008,9,3) && Grab 3 digit date1
      date2 = substr(cu008,13,3) && Grab 3 digit date2

      Do repro with date1, 1,"cu008/9-12","cuDate_1"
      Do repro with date2, 1,"cu008/13-15","cuDate_2"
    END


  2. Coded Fixed Fields: Language Code (cuLCode)


    ***** 1. GRAB LANGUAGE CODE FROM 008

    IF len(substr(cu008,36,3)) > 0
      lcode = SUBSTR(cu008,36,3)
      Do repro with lcode, e->hits,"cu008/36-38", "cuLCode"
    ENDIF

  3. BCE Dates

    Convert MARC 046 dates as following:

                             046 |aq|b500|d690

    converts to:

                            cuDate_1 | 1 | -690
                            cuDate_2 | 1 | -500
    etc.

  4. Writing Material / Medium (cu655)

    Scan source MARC 300 field content for specified writing material / medium and generate a single cu655 field as follows:

    300 |a1|fitem :|bpapyrus, twenty-one partly joined fragments ...

    converts to:

    cu655 | 1| Papyri

    NB: The source 300 field is also converted directly to cu300; see Duke Apis general specification.

    Material/medium conversions.
    DO CASE
    	CASE "PAPY"$tem
    		temp_res = "Papyri
    	CASE "OSTRAC"$tem
    		temp_res = "Ostraca
    	CASE "LEAD TABLET"$tem
    		temp_res = "Lead tablets
    	CASE "WOODEN TABLET"$tem
    		temp_res = "Wood tablets"
    	CASE "PARCHMENT"$temp
    		temp_res = "Parchment"
    ENDCASE

    KNOWN PROBLEM: "potsherd" in 300 field; "ostraka" in 655 field; need to change "ostraka" to "ostraca" on conversion.

  5. Data Link to Source Description (cu510_m)

    Grab directory of Duke metadata records from: http://scriptorium.lib.duke.edu/papyrus/records/

    e.g., 100r.html

    Create special cu510_m field as follows:

    cu510_m | 1 | http://www.scriptorium.lib.duke.edu/papyrus/records/1r.html

    Field is used in the APIS Interface to create direct links back to corresponding original Duke description.

  6. Image Links (Holdings, Structural Metadata)

    1. Grab image listings from Duke APIS website: http://scriptorium.lib.duke.edu/papyrus/images/

      Index of -papyrus-images-thumbnails-.htm
      Index of -papyrus-images-72dpi-.htm
      Index of -papyrus-images-150dpi-.htm
      Index of -papyrus-images-300dpi-.htm
      Index of -papyrus-images-600dpi-.htm

    2. Convert from HTML into plain text
    3. Read into dBASE as raw text (SDF, 1 line per record)
    4. Extract data/create new table from image filenames with:

      • normalized form of Duke Inventory Number
      • normalized indication of Recto/Verso
      • resolution (dpi)

    5. Extract table from Duke descriptive metadata file with

      • normalized form of Duke Inventory Number
      • normalized indication of Recto/Verso
      • Duke APIS ID (i.e., cu001)

    6. Match & merge image table with descriptive table extract to create single image/metadata directory correlating Duke images with Duke APIS records.

    7. Manually review & edit output to:

      • make sequences for MMF part/view
      • presentation rows unique (many duplicates because of above processing approach) correctly with corresponding metadata record.

    8. Output text file with image/structural metadata formatted in MMF Interface Format, e.g.,
      cu001 | 1 | duke.apis.32053985
      part_view_CAPTION | 1 | Verso -- bottom
      presentation_RESOLUTION | 1 | 1 | thumbnail
      presentation_MIMETYPE | 1 | 1 | image/gif
      presentation_ADDRESS | 1 | 1 |
      http://scriptorium.lib.duke.edu/papyrus/images/thumbnails/18v-bottom-thumb.gif


Columbia Libraries    Digital Program
Last revision: 04/10/01
© Columbia University