Trismegistos and LGPN

[tuurma]

LGPN basic data structures (attempt at representation in ERD notation)

• field names in bold, starting with TM_ - new fields to accommodate Trismegistos data
• descriptions in bold, fields using TM data, label of TM field to use;
  • when marked with * suffix, require some processing (e.g. line)
  • when marked with * prefix, it stands for a range of TM fields for names (e.g. given_name, double_name)

[tuurma]

Places

• receive a list of TM places and merge TM.residence_id into LGPN.Places.TM_REF
• upon import, resolve TM.residence_id into LGPN.Places.@xml:id

[tuurma]

Bibliography

What we store in LGPN in Reference.abbr - Details - Line will need to be retrieved from TM.tex_id - publication - line but there is no 1:1 relationship between any of these fields. Atm I assume we'll need to:

• extract a list of distinct values of text abbreviations used in export file and map to LGPN abbreviations
• upon import resolve target against the mapping list; use the remainder of the publication field as details
• likely we'd need to analyze the value in TM.line field, because part of it probably belongs to LGPN.details

[tuurma]

Names

groups of values related to given_name, double_name, triple_name, pseudo1, pseudo2, pseudo3 will be converted to attested forms; type of the original TM section will be preserved in TM_type field and respective ids in TM_VAR and TM_CASE; connection with the TM.ref_id via TM_REFERENCE (and corresponding TM_REF on bibl entry). This should allow us for round trip between TM and LGPN

[tuurma]

Relationships

Each of TM.per_id_father, _mother, etc will be converted to a relation entry. TM id will be preserved in dedicated TM_REF field on relation.

[tuurma]

Floruit/Birth Date

Unlike text dating, which comes both in human readable and normalized y-m-d forms, the floruit field lacks normalization and would be very difficult to automatically map to LGPN named period or year range mechanisms. Is it possible to export normalized dates for floruit field from TM?