#1 DDBDP Link creation
NB: The APIS Search Interface creates a URL link to the corresponding DDBDP record
in the form:
http://www.perseus.tufts.edu/cgi-bin/ptext?doc=Perseus:abo:pap,[content of cu510_dd]
e.g.,
#2 APIS "Preferred Citation" Note
SUMMARY: Convert
5 [First Editor] "Winter JG-Youtie HC"
6 [Ser_Vol] "PMich VIII"
7 [Pg_No] "520"
8 [Year] "1951"
9 [Photo] "Pl. IX"
10 [SB] "SB XII 11106"
11 [Corrections] "BL VI, 84 corrects date to IV AD"
into a single cu524 field, as follows:
cu524 "Winter JG-Youtie HC, PMich VIII 520, 1951, Pl. IX --
SB XII 11106 -- BL VI, 84 corrects date to IV AD"
#3 Republication Citation
SUMMARY: Convert
[sic] 13 [Rep_Ser] "CPJ II"
[sic] 12 [Rep_editor] "Tcherikover VA - Fuks A"
14 [Rep_Pg_No] "413 (= l. 39-45 only)"
15 [Rep_Year] "1960"
16 [Rep_photo]
17 [Rep_SB]
18 [Rep_corr]
into a single cu510 field, as follows:
cu510 "Tcherikover VA - Fuks A, CPJ II 413 (= l. 39-45 only), 1960"
NB: Order of data in converted cu510 is UMICH 12,13,14,15,16,17,18
#4 Extent statement / Genre
Michigan records are chiefly for Ostraca and Papyri, but other formats such as
wax tablets, wood, wood tables, and "lead" are also present.
SUMMARY:
a) Convert UMICH fields 3, 24 and 61 into a single cu300 field as follows:
3 [Material] "Pap"
24 [Size] "7.2 x 7.6 cm"
61 [Items] "1"
convert to:
cu300 "1 papyrus ; 7.2 x 7.6 cm"
NB: UMICH Field 3 [Material] may contain either "Pap" or "Ost"; convert as follows:
If 3 = "Pap"
If 61 = "1" set cu300 to "1 papyrus ; [insert Field 24 content]"
Else if 61 > "1" set cu300 to "N papyri ; [insert Field 24 content]"
where N is the content of Field 61
Else If 3 = "Ost",
If 61 = "1" set cu300 to "1 ostracon ; [insert Field 24 content]"
Else if 61 > "1" set cu300 to "N ostraca ; [insert Field 24 content]"
where N is the content of Field 61
Else If 3 = "Par",
Change to "Pap" and follow spec under "Pap"
NB: Assumed keying error
Else if 3 = "WT"
Change to "Wax Tablet" and follow spec under "Otherwise" (below)
Otherwise
Set cu300 to [insert Field 3 content] ; [insert Field 24 content]"
NB: Order of data in converted cu300 is UMICH 61, 3, 24
b) Also create a separate cu655 field from UMICH Field 3 [Material] as follows:
If 3 = "Pap" generate cu655 with content "Papyri"
If 3 = "Ost" generate cu655 with content "Ostraca"
If 3 = "WT" generated cu655 with content "Wax Tablet"
For other content, move to cu655 as is.
NB: Original fields with "Par" as content assumed to be typo for "Pap" and corrected as
such.
#5 Language Note, Language Codes
SUMMARY: Create two CU data elements from UMICH 35 [Language]
a) Move the entire contents of UMICH 35 to cu545, e.g.,
35 [Language] "Greek, Demotic Recto, Greek - 7 + 6; Recto, Demotic - 2;
Verso, Demotic - 1"
to:
cu546 "Greek, Demotic; Recto, Greek - 7 + 6; Recto, Demotic - 2;
Verso, Demotic - 1"
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.)
35 [Language] cuLCODE
"Arabic" = "ara"
"Aramaic" = "arc"
"Coptic" = "cop"
"Demotic" = "egy"
"Greek" = "grc"
"Latin" = "lat"
"Hieratic" = "egy"
"Hieroglyphic" = "egy"
e.g., Convert
35 [Language] "Greek, Demotic; Recto, Greek - 7 + 6; Recto, Demotic - 2;
Verso, Demotic - 1"
to:
cuLCODE "grc"
#6 Further Republication Note
SUMMARY: Convert
38 [Further rep] "Tcherikover VA - Fuks A, CPJ II 413, 1960"
47 [Further_rep_corr] "BL VI, 84 corrects date to IV AD"
92 [Further_rep_SB] "SB XII 11106"
to a single cu510, as follows:
cu510 "Tcherikover VA - Fuks A, CPJ II 413, 1960 --
BL VI, 84 corrects date to IV AD -- SB XII 11106"
#7 Title Statement Conversion / cuDate_1 & cuDate_2 Conversion
NB: Some Michigan records lack "Type of text_title" fields; for these, use
INV NO for cu245ab.
a) Create cu245ab title statement by combining two UMICH fields:
23 [Type of text_title] "Memorandum for a Register of Contracts"
40 [Date] "After Oct. 27, 46 A.D."
into a single cu245ab field, as follows:
cu245ab "Memorandum for a Register of Contracts, After Oct. 27, 46 A.D."
NB: Insert comma+space ahead of UMICH 40 data.
b) Create cuDate1 and cuDate2 fields by scanning & evaluating UMICH 40 [Date] field,
as follows:
40 [Date] cuDate_1 cuDate_2
Ist cent. A.D. 1 99
Ist-IInd cent. A.D. 1 199
IInd Cent. A. D. 100 199
Early IInd Cent. A. D. 100 150
1st half of the IInd cent. A.D. 100 150
2nd half of the IInd cent. A.D. 150 200
Latter half of IInd cent. AD 150 200
*Middle or late IInd cent. A.D. 150 200
IInd-IIIrd cent. A.D. 100 299
IInd/IIIrd. cent. A.D. 100 299
IInd or IIIrd cent. A.D. 100 299
IInd or early IIIrd cent. A.D. 100 250
Late IInd/IIIrd cent. A.D. 200 [null]
IIIrd cent. 200 299
(Early) IIIrd cent. A.D. 200 299
IIIrd/IVth cent. A.D. 200 399
IIIrd-IVth cent. A.D.(?) 200 399
IIIrd or IVth Cent. A. D. 200 399
Late IIIrd/early IVth cent. A.D. 250 350
Late IIIrd or early IVth cent. A. D. 250 350
Early 6th cent. A.D.
Late IVth - early Vth cent.
A. D. (between 381 and 431 A.D.) 381 431
IVth cent. A.D. 300 399
IVth/Vth cent. A.D. 300 499
Vth cent. A.D.?
Vth Cent. A. D. 400 499
VIth Cent. A.D. 500
VIth/VIIth cent. A.D. 500 699
VIIth cent. A.D. 600 699
VIIth/VIIIth cent. A.D.
7th or 8th Cent. A. D. 600 799
ca. Sept. 46 A.D. 46 [null]
29-30 A.D. 29 30
14-37 A.D. (reign of Tiberius) 14 37
*25 February - 26 March, 203 A.D. 203
BC Dates
251(?) B.C. -251
*spring of 240 B.C. -240
*ca. 257 B.C.(?) -257
*about 242 B.C. -242
*IInd or Ist cent. B.C. -199 -1
IIIrd cent. B.C -299 -200
IIIrd/IInd cent. B.C. -299 -100
*Asterisk indicates that manual editing was required to convert into normalized format.
See detailed conversion scripts at: FileMakerPro Scripts (Field Calculations) Used to Create
Normalized Date Fields from Michigan APIS Records
#8 Convert multiple names from single UMICH field into multiple CU fields
UMICH "Persons" field NOT INCLUDED IN CONVERTED RECORDS, because a) kludge of many
names stuffed into single field, often > 1 MG in length; b) names usually already
present in Translation or Summary field, hence searchable.
#9 Image Links
NOTE: 2/2001 Michigan changed image
naming scheme and re-sent all image links in APIS Interface Format.
ORIGINAL CONVERSION:
Convert the following original U. Mich fields only: Full Size Front, Full size Back,
FullSizeFrontR1, FullSizeFrontR2, FullSizeBackR1, FullSizeBackR2
For each above field with content, create 1 part_view_CAPTION and 3 presentation_RESOLUTION /
presentation_ADDRESS pairs, as detailed below.
Generate sequence and subsequence numbers as per general CU MMF spec.
NB: There are many redundancies and ambiguities in Michigan image data as received; some
attempt has been made to reduce duplication, but may not be 100% clean. Should be resupplied
in appropriate standard format if reload or update is required.
Specifications
NB: Base address for image links = "http://www.hti.umich.edu/collaboratory/gagos/img/"
1. Create "part_view_CAPTION | 1 | " + [corresponding caption based on umich element name, per list]
SEQ UMICH ELEMENT CAPTION
32 [Full Size Front] "Full size front"
33 [Full size Back] "Full size back"
64 [FullSizeFrontR1] "Full size front R1"
65 [FullSizeFrontR2] "Full size front R2"
66 [FullSizeBackR1] "Full size back R1"
67 [FullSizeBackR2] "Full size back R2"
2. Thumbnail image
2.1. Create "presentation_RESOLUTION | [seq/subseq] | thumbnail"
2.2. Create "presentation_ADDRESS | [seq/subseq] | + [base URL] + [thumbnail image name]"
Where, e.g., Full Size Front = "1571r.bmp"
thumbnail image name = "1571r-th.gif"
3. 50% size image
3.1. Create "presentation_RESOLUTION | [seq/subseq] | 50% size"
3.2. Create "presentation_ADDRESS | [seq/subseq] | + [base URL] + [50% image name]"
Where, e.g., Full Size Front = "1571r.bmp"
50% image name = "1571r-50.jpg"
4. Full size image
4.1. Create "presentation_RESOLUTION | [seq/subseq] | full size"
4.2. Create "presentation_ADDRESS | [seq/subseq] + [base URL] + [full size image name]"
Where, e.g., Full Size Front = "1571r.bmp"
full size image name = "1571r.jpg"
EXAMPLE:
ORIGINAL INPUT:
Full Size Front = 281.bmp
FullSizeFront R2 = 281r.bmp
FullSizeBack R1 = 281v.bmp
MMF OUTPUT:
part_view_CAPTION | 1 | Full size front
presentation_RESOLUTION | 1 | 1 | thumbnail
presentation_ADDRESS | 1 | 1 | http://www.hti.umich.edu/collaboratory/gagos/img/281-tn.gif
presentation_RESOLUTION | 1 | 2 | 50% size
presentation_ADDRESS | 1 | 2 | http://www.hti.umich.edu/collaboratory/gagos/img/281-50.jpg
presentation_RESOLUTION | 1 | 3 | full size
presentation_ADDRESS | 1 | 3 | http://www.hti.umich.edu/collaboratory/gagos/img/281.jpg
part_view_CAPTION | 2 | Full size front R1
presentation_RESOLUTION | 2 | 1 | thumbnail
presentation_ADDRESS | 2 | 1 | http://www.hti.umich.edu/collaboratory/gagos/img/281r-tn.gif
presentation_RESOLUTION | 2 | 2 | 50% size
presentation_ADDRESS | 2 | 2 | http://www.hti.umich.edu/collaboratory/gagos/img/281r-50.jpg
presentation_RESOLUTION | 2 | 3 | full size
presentation_ADDRESS | 2 | 3 | http://www.hti.umich.edu/collaboratory/gagos/img/281r.jpg
part_view_CAPTION | 3 | Full size back R1
presentation_RESOLUTION | 3 | 1 | thumbnail
presentation_ADDRESS | 3 | 1 | http://www.hti.umich.edu/collaboratory/gagos/img/281v-tn.gif
presentation_RESOLUTION | 3 | 2 | 50% size
presentation_ADDRESS | 3 | 2 | http://www.hti.umich.edu/collaboratory/gagos/img/281v-50.jpg
presentation_RESOLUTION | 3 | 3 | full size
presentation_ADDRESS | 3 | 3 | http://www.hti.umich.edu/collaboratory/gagos/img/281v.jpg
|
Digital
Program