APIS Documentation

What kind of documentation is needed for APIS in light of the APISMigration?

Existing documentation

Columbia currently provides the following "Metadata Guidelines":

http://www.columbia.edu/cu/libraries/inside/projects/apis/guidelines.html

They also provide a Word template (for MARC records? -- need a copy?) which is accompanied by the following documentation:

1) when opening the template click "enable macros."

2) after completing a record, try saving it by its apis number with extension “.if” as “Text Only”: e.g. nyu.apis.31.if.  If this fails, the “.doc” extension may be kept.

Required fields are in bold type.
___________________________


cu001 = apis id

cu090 = object inventory number

cu245ab = title 

cu245f = date (e.g., 7 November, 141 A.D.; V/VIth c. A.D.)

cu300 = physical description of the object (e.g., no. of fragments; dimensions) 

cu500 = description of the text (e.g., recto/verso, direction of writing; number of lines; parallel texts; margins; kolleseis; fabric; comments can be entered in this field)

cu500_t = translation (no hard returns; no use of pipes “|”; the following symbols are OK: *, ?, - , _ , [  ] )

cu510 = publication information (publication no. or unpublished; if published Greek/Latin document, give publication abbreviation in accordance with Duke’s Checklist, http://odyssey.lib.duke.edu/papyrus/texts/clist.html. Greek and Latin literary papyri should be identified in accordance with the publication field in the LDAB--e.g., P. Oxy. 69 4728 or ZPE 164 (2008), p. 29-31.  Editors name can be provided in extended bibliography cu581.)

cu510_dd = DDBDP link (formatted in the way specified at http://www.columbia.edu/cu/libraries/inside/projects/apis/documentation/ddbdp.html)

cu518 = provenance

cu520 = content summary

cu546 = language(s) (e.g. Greek, Coptic, Unknown; repeatable field = up to 3 entries allowed)

cu561 = acquisition information (e.g. year, trench, locus, findspot)

cu581 = publications about (full bibl., secondary bibl., BL citations)

cu590 = conservation and local note (photo ref.; registration/SCA number, if appl.; additional inv. numbers); place where the object is housed.

cu653 = ignore

cu655 = description of material (e.g., papyri, ostraca, parchment, etc.), and text type e.g. account, oath, etc.; repeatable field = up to 5 entries allowed)

cu100a = personal name 

cu100g = additional personal name info. (e.g., patronymic)

cu1004 = personal name abbr. (either = aut for “author” or asn for “associated name”)

cuDateValue |1| (aka dd046) = year in numeric form (e.g. 141 or 500)

cuDateRange |1| (aka dd046) = enter either b (for “beginning date of a range”) or s (for “single date”; thus, if the year is 141 A.D., enter s, and if it is V/VIth c., enter b)

cuDataSchema |1| (aka dd046) = enter either b (for “Before Common Era, BCE” [BC]) or c (for “Common Era, CE” [AD])

cuDateValue |2| = year in numeric form (e.g. 600), note: if cuDateRange |1| = s, then ignore this field

cuDateRange |2| = enter e (for “ending date of range”), note: if cuDateRange |1| = s, then ignore this field

cuDataSchema |2| = enter either b (for “Before Common Era, BCE” [BC]) or c (for “Common Era, CE” [AD]), note: if cuDateRange |1| = s, then ignore this field