Super-glossary Map Files

Map files are very simple and have the following schematic structure:

add|cut|fix|map|new	entry|sense	SIGNATURE	=> 	SIGNATURE

add|cut|fix|map|new

When an entry or sense in the source is not in the base, a new item is generated. You can change this to add to indicate that the item should be added to the base. To identify this source item with a different base item, you can change the new to map. In this case, the target for the mapping must be specified by giving the special sequence => followed by the base item with which to identify the new source item.

entry|sense

Primarily intended to make the map file more human-readable, this identifies the new item as either a glossary entry or a sense belonging to an entry.

SIGNATURE

Signatures are a core concept of the Oracc lemmatizer, but the super-glossary tools use only a limited subset of the information that can be in a signature. Signatures in super-glossaries either have the form CF[GW]POS or CF[GW//SENSE]POS'EPOS.

Signature Components

CF
Citation Form
GW
Guide Word
SENSE
Sense
POS
Part of Speech
EPOS
Effective Part of Speech--the POS appropriate to the SENSE

Mapping and fixing

Mapping and fixing both enable an item in the source glossary to be treated as a different item in the base glossary. The two share the same structure in which the right hand side is an arrow made up of an equals sign and a right angle bracket (=>), surrounded by spaces, and followed by the base item to which the source item corresponds. The difference between map and fix is that map should be used when the difference between the source and base is a matter of style or approach between the source and base. By contrast, fix is an assertion that there is an error in the source glossary which could be fixed. These can be reported to the project manager. Examples of map and fix are:

fix entry akī[as]PRP => akī[like]PRP
map entry akī[as]PRP => akī[like]PRP

Omitting items in the source from the merge

Items which should not be added to the base glossary may be specified using cut:

cut entry akī[as]PRP

Comments in map files

Comments may be entered in the map files by adding lines beginning with the # character (pound sign/hash mark):

map entry akī[as]PRP => akī[like]PRP
# correct GW to align with base glossary

PSU handling

PSUs (Phrasal Semantic Units) are checked and entered into the map file by super-compare just like any other word, and they can be mapped and fixed in the expected manner.

If a PSU has an add action, the parts of the PSU are automatically imported from the source glossary into the base glossary. The super-glossary tools check the parts to ensure that they are either already in the base glossary or are being added from the source glossary that is being mapped. This means that as long as the components of a PSU are being mapped in from the source glossary or are already known, no special action need be taken.

It may be, however, that a component of a PSU in the source glossary is not being mapped in from the source, and does not align with an entry in the base glossary either. In this case, the parts for the PSU can be given in the map file, at the end of the add line, in the following format:

add [SIGNATURE] @parts [PARTS]

See the sample map file for a example.

Sample map file

map entry akī[as]PRP => akī[like]PRP
add entry arkānu[later]AV
add entry bēl āli[city ruler]N @parts bēlu[lord]N ālu[city]N
new entry dabābu[claim]V
new sense eṭēru[pay//paying]V'V
 
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/superglossaries/mapfiles/