-
Notifications
You must be signed in to change notification settings - Fork 5
Moravian Lives Database structure
(last reviewed October 17, 2017)
MySQL database from which the Moravian Lives API (http://moravianlives.org) draws for information and visualization about Moravian people and places, predicated on references in lebenslaufe, memoirs, and obituaries. The database was originally compiled by Trausti Dagson in 2015 and has been augmented since that time by several contributors.
- bak_20160429_persondocuments
- bak_20160429_personplaces
- bak_20160429_persons
- datasource
- documentplaces
- documents
- lebenslauf_original
- memoirs
- original_persons_bak
- original_places_bak
- persondocuments
- personplaces
- persons
- places
(there are also tables in the existing database that run the WordPress instance for the Moravian Lives website)
- table ID
- person ID (from bak_20160429_persons table)
- document ID (which table does this draw from?)
- table ID
- person ID (from bak_20160429_persons?)
- place ID (from bak_20160429_persons?)
- relation (b/d for place of birth/death)
- table ID
- ll_ID (lebenslaufe ID) - varchar
- ll_idnum (lebenslaufe ID) - integer
- page (number of lebenslaufe pages?) - integer
- surname_literal - varchar
- surname - varchar
- language - varchar
- firstname - varchar
- birthplace (where does this field draw from?)- integer
- ll_birthplace (from lebenslauf) varchar
- deathplace - integer (where does this field draw from?)- integer
- ll_deathplace 9from lebenslauf) varchar
- birth_year - 4 figure integer
- birth_month - 2 figure integer
- birth_day - 1-2 figure integer
- ll_birth - integer: date in month.day.year format
- death_year - 4 figure integer
- death_month - 2 figure integer
- death_day - 1-2 figure integer
- ll_death - integer: date in month.day.year format
- gender - integer: male="0", female="1"
- ownhand - integer: ?="0", ?="1" //not sure what this code means. Is "0" no and "1" yes? (e.g., 1="written by person")
- system_group1 - varchar: one letter (what does lettering system stand for?)
- former_surname_literal - varchar: name as different from name at time of death (from lebenslauf?)
- former_surname - varchar: (seems synonymous with former_surname_literal; surnames numbered if multiple marriages)
- familystatus - varchar: "verheiratet" or blank
- partner_name - varchar
- comment - text: looks like an archive record (in German)
- remove - varchar (appears to be blank)
- reference - varchar (appears to be blank)
- metadata - text: ("NULL)
- source - integer: (this field draws from datasource table)
- ID - (Actually location ID as well as table ID)
- name - varchar (three choices: 1="Herrnhut", 2="Bethlehem", 3="London")
- table ID? - integer (not unique - each ID used twice to differentiate birth and death place)
- person ID - integer (not unique - each ID used four times but unclear why)
- place ID - integer (where does this field draw from?)
- relation - varchar (b/d for place of birth/death - how does this connect to "document place?" - is it place referred to in document?)
- table ID
- ll_ID (lebenslaufe ID) - varchar
- ll_idnum (lebenslaufe ID) - integer
- page (number of lebenslaufe pages?) - integer
- surname_literal - varchar
- surname - varchar
- language - varchar
- firstname - varchar
- birthplace (where does this field draw from?)- integer
- ll_birthplace (from lebenslauf) varchar
- deathplace - integer (where does this field draw from?)- integer
- ll_deathplace 9from lebenslauf) varchar
- birth_year - 4 figure integer
- birth_month - 2 figure integer
- birth_day - 1-2 figure integer
- ll_birth - integer: date in month.day.year format
- death_year - 4 figure integer
- death_month - 2 figure integer
- death_day - 1-2 figure integer
- ll_death - integer: date in month.day.year format
- gender - integer: male="0", female="1"
- ownhand - integer: ?="0", ?="1" //not sure what this code means. Is "0" no and "1" yes? (e.g., 1="written by person")
- birthname - varchar
- birthname_literal - varchar (needs explanation)
- system_group1 - varchar: one letter (what does lettering system stand for?)
- former_surname_literal - varchar: name as different from name at time of death (from lebenslauf?)
- former_surname - varchar: (seems synonymous with former_surname_literal; surnames numbered if multiple marriages)
- familystatus - varchar: "verheiratet" or blank
- partner_name - varchar
- comment - text: (in German)
- remove - varchar (appears to be blank)
- reference - varchar (appears to be blank)
- metadata - text: ("NULL)
- source - integer: (this field draws from datasource table)
- doc_text = text (looks like placeholder field)
- docimages = text (looks like placeholder field)
(the purpose of this table is unclear, unless it is a check against an original list from Herrnut) 31 columns labeled "COL" - varchar but beneath those columns are listed
- id (appears to be shelfmark)
- idnum (number)
- page (number of pages)
- surname_literal
- surname
- language
- firstname
- birthplace
- birthplace_en
- birthcountry
- birthcountry_en
- deathplace
- deathplace_en
- deathcountry
- deathcountry_en
- birth (date format month.date.year if all information is known)
- death (date format month.date.year if all information is known)
- gender (in German)
- ownhand (in German)
- birthname
- birthname_literal
- system_group1 (lettering system)
- former_surname_literal (what is the difference between surname and surname_literal?)
- former_surname
- locked_up
- familystatus (in German)
- spouse_name
- comment (in German)
- edition
- remove
- reference
(could this be from the Bethlehem Archives? - all fields varchar)
- AutoID
- ReferenceNr
- SourceCollection
- FirstName
- LastNameNormal
- LastNameExac
- FormerLastNames
- PlaceBirth
- Coutnry/RegionBirth
- DateBirth
- NotesRemarks
- DateDeath
- Country/RegionDeath
- MaritalStatus
- NamePartner
- Gender
- Size
- DescriptionLog
- Language
- Translation
- Script
- EditingDate
- table ID
- ll_ID (lebenslaufe ID) - varchar
- ll_idnum (lebenslaufe ID) - integer
- page (number of lebenslaufe pages?) - integer
- surname_literal - varchar
- surname - varchar
- language - varchar
- firstname - varchar
- birthplace (where does this field draw from?)- integer
- deathplace - integer (where does this field draw from?)- integer
- birth_year - 4 figure integer
- birth_month - 2 figure integer
- birth_day - 1-2 figure integer
- ll_birth - integer: date in month.day.year format
- death_year - 4 figure integer
- death_month - 2 figure integer
- death_day - 1-2 figure integer
- ll_death - integer: date in month.day.year format
- gender - integer: male="0", female="1"
- ownhand - integer: ?="0", ?="1" //not sure what this code means. Is "0" no and "1" yes? (e.g., 1="written by person")
- birthname - varchar (what is the difference between birthname and birthname_literal?)
- birthname_literal - varchar
- system_group1 - varchar: one letter (what does lettering system stand for?)
- former_surname_literal - varchar: name as different from name at time of death (from lebenslauf?)
- former_surname - varchar: (seems synonymous with former_surname_literal; surnames numbered if multiple marriages)
- familystatus - varchar: "verheiratet" or blank
- spouse_name - varchar
- comment - text: looks like an archive record (in German)
- remove - varchar (appears to be blank)
- reference - varchar (appears to be blank)
- Table ID - integer
- name - varchar
- name_en - varchar
- area - varchar
- area_en - varchar
- lat - double
- lng - double
- google_id - varchar
- google_address - varchar
- google_address_data - blog
- google_location_type - varchar
- google_name - varchar
(this is a sequential list with all fields apparently in order; perhaps dictated by document ID?)
- Table ID
- person ID
- document ID
- Table ID - integer
- person ID - integer (not unique - each ID used four times but unclear why)
- place ID - integer (which table does this draw from?)
- relation varchar (b/d for place of birth/death - how does this connect to "document place?" - is it place referred to in document?)
- table ID
- ll_ID (lebenslaufe ID) - varchar
- ll_idnum (lebenslaufe ID) - integer
- page (number of lebenslaufe pages?) - integer
- surname_literal - varchar
- surname - varchar
- language - varchar
- firstname - varchar
- birthplace (where does this field draw from?)- integer
- ll_birthplace (from lebenslauf) varchar
- deathplace - integer (where does this field draw from?)- integer
- ll_deathplace 9from lebenslauf) varchar
- birth_year - 4 figure integer
- birth_month - 2 figure integer
- birth_day - 1-2 figure integer
- ll_birth - integer: date in month.day.year format
- death_year - 4 figure integer
- death_month - 2 figure integer
- death_day - 1-2 figure integer
- ll_death - integer: date in month.day.year format
- gender - integer: male="0", female="1"
- ownhand - integer: ?="0", ?="1" //not sure what this code means. Is "0" no and "1" yes? (e.g., 1="written by person")
- birthname - varchar (what is the difference between birthname and birthname_literal?)
- birthname_literal - varchar
- system_group1 - varchar: one letter (what does lettering system stand for?)
- former_surname_literal - varchar: name as different from name at time of death (from lebenslauf?)
- former_surname - varchar: (seems synonymous with former_surname_literal; surnames numbered if multiple marriages)
- familystatus - varchar: "verheiratet" or blank
- partner_name - varchar
- comment - text: looks like an archive record (in German)
- remove - varchar (appears to be blank)
- reference - varchar (appears to be blank)
- metadata - text: ("NULL)
- source - integer: (this field draws from datasource table)
- Table ID - integer
- name - varchar
- name_en - varchar
- name_ll - varchar (placename from lebenslauf)
- area - varchar
- area_en - varchar
- area_ll - varchar (areaname from lebenslauf)
- lat - double
- lng - double
- google_id - varchar
- google_address - varchar
- google_address_data - blog
- google_location_type - varchar
- google_name - varchar
- commentary - text
- notfound int