Notes

Note 1

This was not the only database conversion that has taken place. In 1990 Ingres was upgraded from version 5 to 6 which required the database to be recreated and consequently re-loaded. Similarly, in the process of producing volume 2 minor modifications have been made to the structure of the database to improve the organisation of the data and the speed of retrieval.

Note 2

These conventions were devised for the original IDMS/Lasercomposer system. Although it would be possible to introduce newer, more up-to-date codes, for the sake of consistency, and the limitations of time for converting existing data, this possibility is precluded.

Note 3

Under the supervision of Professor M.J. Osborne of La Trobe University.

Note 4

In the end it was decided to abandon establishing links between people and just place the information in the relationship comment table relcomm. The reasons for this are described in footnote 6.

Note 5

Some references could have more than one pattern, and within a pattern a certain amount of variation has to be allowed for.

Note 6

For instance, John Smith II who was the son of a John Smith I, would be confused with another John Smith II, also the son of a different John Smith I. The place and date information would be the same, but the reference details would be different. The relationship matching program was not set up to take this situation into account. The problem did not arise to the same extent with volume 1, and is unlikely in volume 3. Volume 2, covering a small geographical, but comparatively densely populated area, is the only volume where this is likely to be a major problem. It was considered too costly in time for the issue to be resolved at this stage.

 

Note 7

The actual sorting order of fields from the database is as follows:

     namid, 
     islid, 
     towid, 
     towdeme,     
     polis, 
     resrely, 
     permindate, 
     permaxdate, 
     bknum, 
     refchap, 
     reftext, 
     refline, 
     perhomon.
The reference data only includes the primary reference, while the homonym data only takes effect if all the other values are the same. If there is no homonym value, the order will be as loaded from the original data files.

The place order puts all definite places before queried ones, and attested come at the end of the list. In volume 2, if the initial letter of fragmentary demes was known they were placed in their correctly sorted order, otherwise they came after known demes but before tribes.

Note 8

As of April 1994 the LGPN has lost the support of the Oxford based British Academy Data Manager. What this will mean in practical terms of computer support has yet to be ascertained, and it is hoped that no major disruptions will occurr in the foreseeable future.


Email lgpn@classics.ox.ac.uk



Home  

Project  

Publications  

LGPN Online  
Background  
Searches  
Downloads  
Statistics  

Greek names  

Image Archive  

Contact  

 

Classics at Oxford  

University of Oxford  

British Academy 

AHRC