Yale APIS records have no sequential record number suitable for use as a record control
number.  Because of the desirability of having a unique, stable, derivable number based 
on record content, a number constructed from the Yale Filemaker Pro "PIN" element was used
as the basis for the APIS number to use as an APIS ID. The conversion spec for the numeric 
portion of the ID (i.e., the portion of the identifier that follows "yale.apis.") follows:

The designations "fol" and "qua" are ignored; all internal spaces are removed.

Examples:

For details of the conversion scripts used, see 001.pdf

#2 DDBDP Link creation

Some Yale records as exported include a link to the corresponding DDBDP record in the form:

<a href="http://www.perseus.tufts.edu/cgi-bin/papytext?series=P.Yale&lookup=1.74">

This reflects the older syntax for DDBDP linking, and for APIS has been converted into a cu510_dd reference such as:

cu510_dd | 1 | P.Yale:1:74

This is processed by the APIS interface into a new-style DDBDP link such as:

http://www.perseus.tufts.edu/cgi-bin/ptext?doc=Perseus:abo:pap,P.Yale:1:74

    SUMMARY:  Create two CU data elements from Yale LAN element:


    a) Move the entire contents of Yale LAN field to cu545, e.g.,


        LAN   "Egyptian\Coptic"
    to:
        cu546 "Egyptian\Coptic"

    b) Scan field for first occurrence of one of the language names listed in the first 
       column below, and create an cuLCODE field with the corresponding equivalent code. 
       (NB: No matter how many languages are recorded in the original field, only one 
       cuLCODE will be used.)

#4 Title Statement (cu245ab) Creation

NB: Yale records lack a Title element; a title must be constructed from the Genre element if present.

1. Create cu245ab title statement by combining two Yale fields:
   
   GEN "Contract"
   DTE "Roman-Byzantine [RD]"
   
         into a single cu245ab field, inserting comma+space ahead of Yale DTE data if present,.as follows:
   
   "cu245ab | 1 | Contract, Roman-Byzantine [RD]"
   
   
2. If there is no GEN field, create substitute title with content "Uncertain genre" as follows:
   
   "cu245ab | 1 | Uncertain genre"
   

       Yale image links as received were combined into a single 
       "ThumbImb" field, e.g.,

        <img src="/papyrimg/T4512565.JPG" alt="[2016 (A)]">
        <A HREF="/papyrimg/S4512565.JPG">Screen</A>
        <A HREF="/papyrimg/Z4512565.JPG">Zoom</A>
        <img src="/papyrimg/T4512566.JPG" alt="[2016 (B)]">
        <A HREF="/papyrimg/S4512566.JPG">Screen</A>
        <A HREF="/papyrimg/Z4512566.JPG">Zoom 


These were converted to the cu APIS Interface Format as:

part_view_CAPTION | 1 | [2016 (A)]
presentation_RESOLUTION | 1 | 1 | thumbnail
presentation_ADDRESS | 1 | 1 | http://inky.library.yale.edu/papyrimg/T4512565.JPG	
presentation_RESOLUTION | 1 | 2 | Screen	
presentation_ADDRESS | 1 | 2 | http://inky.library.yale.edu/papyrimg/S4512565.JPG	
presentation_RESOLUTION | 1 | 3 | Zoom	
presentation_ADDRESS | 1 | 3 | http://inky.library.yale.edu/papyrimg/Z4512565.JPG	
part_view_CAPTION | 2 | [2016 (B)]	
presentation_RESOLUTION | 2 | 1 | thumbnail	
presentation_ADDRESS | 2 | 1 | http://inky.library.yale.edu/papyrimg/T4512566.JPG	
presentation_RESOLUTION | 2 | 2 | Screen	
presentation_ADDRESS | 2 | 2 | http://inky.library.yale.edu/papyrimg/S4512566.JPG	
presentation_RESOLUTION | 2 | 3 | Zoom	
presentation_ADDRESS | 2 | 3 | http://inky.library.yale.edu/papyrimg/Z4512566.JPG

#6: Creation of cu655 field

Most Yale records have no form-type genre headings, e.g., "papyri", "wood tablets".  This data is instead found in the COL field, e.g.,

Paper, 90 x 49 mm, (A) 6 lines, no margins, (B) 4 (?) lines, no margins

Create a new "cu655" field from the content of the Yale COL field as follows:

#7:  cuDate1 / cuDate2

Because there are no normalized date fields in the Yale records, it is necessary to create cuDate1 and cuDate2 fields by detailed scanning & evaluation of the Yale DTE field, e.g.,

In some cases date fields were manually assigned, something that would also be required in any subsequent reload from a new Yale file.  See also: detailed (FileMaker Pro) scripts for Yale date conversions.