Project Catalogues

Oracc projects use metadata catalogues to store consistent, searchable information about the tablets and/or composite texts that they contain. For most projects, the CDLI catalogue will be more than adequate. However, this page documents how to create custom catalogues in Filemaker Pro (a commercial database programme for Macs and PCs), and how to export them to XML for use by Oracc. It assumes that you are already familiar with the basic commands in Filemaker.

Fonts and character sets | P-catalogue | Q-catalogue | Exporting catalogue data | Help with conversion and hosting

Fonts and character sets

Filemaker Pro uses the Unicode (UTF-8) character set. Older, non-Unicode fonts such as Assyrian Dictionary are not compatible with Filemaker, or with Oracc. However, not every Unicode font has all the characters that Assyriologists typically need, so you may want to set Filemaker's default font to DejaVu, which does. To do this:

  1. Open Preferences on the Filemaker Pro menu.
  2. Choose the Fonts tab.
  3. Under "Default font for each input type" select "Roman".
  4. On the "Specify font" menu, choose "DejaVuSerif" or "DejaVuSans".
  5. Click "OK".

If and when you are importing data into Filemaker from another database or file format, ensure that you know which character set that data uses. During the import process, when you reach the dialogue box headed Import Field Mapping, make sure you choose the correct character set, to enable smooth conversion to Unicode (UTF-8).

Exporting data from Filemaker to Oracc is described below.

P-catalogue

The information about tablets is stored in a catalogue that by default has the name [PROJECT-NAME]-P.fp7, e.g., cams-P.fp7. All P-catalogues need to include the following two fields:

id_text
The tablet's P-number. Every tablet in Oracc is identified by a unique 6-digit number prefixed by P. The catalogue is minimally a list of P-numbers, which is why it is called a P-catalogue.
designation
Each p-number is paired with a more comprehensible designation for the tablet. This is usually the publication number (e.g., CTN 4, 027), but may also be a museum number or an excavation number. This serves as a check against mistyping P-numbers.

P-numbers and their matching designations are assigned by the CDLI [http://cdli.ucla.edu]. If your tablet is not yet in the CDLI catalogue [http://www.cdli.ucla.edu/cdlisearch/search/indexi.php], e-mail your project liaison (Niek, Steve, or Eleanor) to find out how to get the P-number and designation.

CDLI-style information

The CDLI catalogue defines a large number of fields, which describe the tablet's publication information, physical characteristics, provenance, dating, current location, and textual content. They are briefy documented here [http://cdli.ucla.edu/methods/cat/cat_doc.html]. We thus strongly recommend that you create your database from an an empty clone of the CDLI database [http://cdli.ucla.edu/downloads.html], even if you only want to use a small subset of the CDLI fields.

Project catalogues that contain only CDLI-defined fields and data are known as 'local' catalogues. To implement a local catalogue in your project, be sure to set the catalog-build policy option to 'local' in your project configuration file.

Non-CDLI information

Your project may well need to catalogue metadata that does not fall within the remit of CDLI: names, for instance, or astronomical dates. You can create fields for this information too, with field names that do not reproduce CDLI names. If you want the contents of the field to be a list of more than one item, separate those items with a comma or a semi-colon; do not use FM Pro's repeating fields facility. Make sure you briefly document what each field is for, and if appropriate constrain its permissible contents with a value list.

Project catalogues that contain some non-CDLI-defined fields and data are known as 'custom' catalogues. To implement a custom catalogue in your project, be sure to set the catalog-build policy option to 'custom' in your project configuration file [#Catalog].

Q-catalogue

If your project uses composite texts, compiled from the contents of two or more tablets, you will almost certainly want to relate your catalogue to Oracc's central Q-catalogue [http://oracc.museum.upenn.edu/qcat/] of composite texts. This will enable you to link manuscripts to compositions. The only information from the Q-catalogue you will need in your catalogue is:

id_composite
The composition's Q-number. Every composite text in the Oracc system is identified by a unique 6-digit number prefixed by Q. The catalogue is minimally a list of Q-numbers, which is why it is called a Q-catalogue.
designation
Each Q-number is paired with a more comprehensible designation for the composition. This is maximally composed of the elements [PERIOD] [PROVENANCE] [COMPOSITION] [SECTION], where relevant e.g., OB Nippur Ura 02 or Maqlu 1.

Q-numbers and their matching designations are assigned by Eleanor Robson for Oracc. If your composition is not yet in the central Q-catalogue, contact her for information.

Exporting catalogue data

To make your catalogue data usable in Oracc, as metadata for your ATF files, you need to export it from Filemaker into UTF-8 XML format. You can do this whenever you update or improve your catalogue data. To do so, follow these instructions.

  1. Ensure that the number of found records is the same as the entire database (in the left-hand panel the Found number and Total number must match).
  2. Choose Export Records... from the File menu.
  3. In the Export Records to File dialogue box, name the exported file in the Save As field (usually the same name as the database, with extension .xml) and choose XML from the Type menu in the bottom centre. Click Save.
  4. In the Specify XML and XSL Options dialogue box, choose FMPXMLRESULT from the Grammar menu. Click Continue...
  5. In the Specify Field Order for Export dialogue box, choose which fields are to be exported (that is, all of them that you want to be publicly searchable). The Output File Character Set menu should already be set to Unicode (UTF-8). Click Export.

You can then upload the resulting XML file to the 00cat/ folder on the Oracc server and rebuild the project (or just the catalogue) to instantly access the new metadata.

Help with conversion and hosting

Converting existing databases to the Oracc/CDLI format can be time-consuming and fiddly. We at Oracc can take care of much of the conversion process for you, including the allocation of P-numbers and Q-numbers. We can also host your Filemaker database on a password-protected server, so that it can be accessed by several researchers simultaneously, wherever they are in the world. For more information about help with database conversion or hosting, please email osc at oracc dot org.

23 Jul 2014 osc at oracc dot org

Eleanor Robson

Eleanor Robson, 'Project Catalogues', Oracc: The Open Richly Annotated Cuneiform Corpus, Oracc, 2014 [http://oracc.museum.upenn.edu/doc/help/managingprojects/catalogues/]

 
Back to top ^^
 

Released under a Creative Commons Attribution Share-Alike license 3.0, 2014. [http://www.facebook.com/opencuneiform] [http://oracc.blogspot.com] [http://www.twitter.com/oracctivity]
Oracc uses cookies only to collect Google Analytics data. Read more here; see the stats here [http://www.seethestats.com/site/oracc.museum.upenn.edu]; opt out here.

http://oracc.museum.upenn.edu/doc/help/managingprojects/catalogues/