{"schema_version":"1.0","id":"Glasgow-4024","alternate_ids":[],"catalogue_id":"glasgow-4024","name":"James Glasgow","canonical_url":"https://glasgow.phenotype.dev/people/glasgow-4024.html","json_url":"https://glasgow.phenotype.dev/people/glasgow-4024.json","network_url":"https://glasgow.phenotype.dev/people/glasgow-4024.network.json","wikitree_url":"https://www.wikitree.com/wiki/Glasgow-4024","vitals":{"birth":{"date":"c. 1813 (estimated)","place":"Cookstown (estimated)","status":"estimated"},"death":{"date":null,"place":null,"status":null}},"identity":{"gender":"Male","occupations":[],"locations":["Cookstown (estimated)","Cookstown"],"aliases":[],"research_clusters":["Descendants of James Glasgow (c.1700)"]},"relationships":{"parents":[],"spouses":[],"children":[],"siblings":[]},"claims":[{"id":"C-696fd90375d4","type":"recorded_occurrence","subject_ids":["Glasgow-4024"],"claim":"James Glasgow was recorded in Cookstown (1831).","status":"unknown","status_label":"Probate index","evidence_ids":["E-696fd90375d4"],"notes":"Probate residence: Cookstown, County Tyrone","provenance":"mapped_record"}],"evidence":[{"id":"E-696fd90375d4","claim_ids":["C-696fd90375d4"],"record_type":"Probate residence: Cookstown, County Tyrone","date":"1831","place":"Cookstown","subjects":["Glasgow-4024"],"assertion":"The residence supports the local cluster but no profile match is secure.","evidence_status":"unassessed","source_quality":"derivative","independence_group":"SRC-39c12b12085a","source":{"title":"PRONI Names, Pre-1858 Wills and Admons: James Glasgow, Cookstown, County Tyrone, 1831","repository":null,"reference":"c14200450d9de118","url":"https://apps.proni.gov.uk/ProniNames_IE/SearchPage.aspx"},"provenance":"explicit"}],"open_questions":[],"research_leads":[],"source_summary":[{"title":"PRONI Names, Pre-1858 Wills and Admons: James Glasgow, Cookstown, County Tyrone, 1831","url":"https://apps.proni.gov.uk/ProniNames_IE/SearchPage.aspx","source_quality":"derivative","independence_group":"SRC-39c12b12085a","provenance":"explicit"}],"warnings":[],"provenance":{"tree":"WikiTree One-Tree export","mapped_records":"Glasgow Surname Project map dataset","profile_capture":"Public WikiTree profile evidence capture","relationship_assessments":"Controlled local relationship hypothesis register","research_findings":"Durable research/<profile-or-catalogue-ID>/findings.md case file"},"research_findings":[{"profile_id":"Glasgow-4024","updated":null,"source_path":"research/Glasgow-4024/findings.md","sections":[{"title":"Conclusion","category":"conclusion","markdown":"Created unconnected on 20 August 2026 from the St Luran's burial transcript. The record identifies James Glasgow, residence Cookstown, buried 13 March 1831, aged 40. A PRONI pre-1858 wills and administrations index entry independently names James Glasgow of Cookstown in 1831. The same name, residence, and year strongly identify the two entries as the same man, but neither supplies family relationships."},{"title":"Identity links","category":"assessment","markdown":"| Profile | Distinction |\n|---|---|\n| [Glasgow-1024](https://www.wikitree.com/wiki/Glasgow-1024) | Proposed father of adults born in the 1740s–1750s; not age 40 in 1831 |\n| [Glasgow-3444](https://www.wikitree.com/wiki/Glasgow-3444) | Reports 1776–1866 |\n| [Glasgow-3986](https://www.wikitree.com/wiki/Glasgow-3986) | Larne/St Cedma's man, reportedly born about 1773 |\n| [Glasgow-2988](https://www.wikitree.com/wiki/Glasgow-2988) | Earlier Kildress candidate |\n\nReciprocal exclusion notes were saved on Glasgow-3444, Glasgow-3986, and Glasgow-2988. Glasgow-1024 was not edited because its live update remains on hold pending Glasgow-3305 research.\n\nWikiTree also recorded rejected matches with Glasgow-2439, Glasgow-3095, and Glasgow-1483 during creation."}]}],"similar_people":[{"id":"Glasgow-1623","name":"James Glasgow","catalogue_id":"glasgow-1623","html_url":"/people/glasgow-1623.html","birth_year":1813,"death_year":null,"birth_place":"Portglenone, County Antrim, Ireland, United Kingdom","death_place":null,"score":48,"classification":"similar person","match_reasons":["same first and last name (+18)","same birth year (+30)"],"conflicts":[],"matching_children":[],"child_name_overlap":[],"parent_comparison":"No shared parent is indexed"},{"id":"Glasgow-212","name":"James Robert Glasgow","catalogue_id":"glasgow-212","html_url":"/people/glasgow-212.html","birth_year":1823,"death_year":1903,"birth_place":"Cookstown, County Tyrone, Ireland, United Kingdom","death_place":"Gortin, Derryloran, Cookstown, County Tyrone, Ireland, United Kingdom","score":48,"classification":"similar person","match_reasons":["same first and last name (+18)","birth years within 10 (+10)","shared recorded place (+20)"],"conflicts":[],"matching_children":[],"child_name_overlap":[],"parent_comparison":"No shared parent is indexed"}],"potential_parentage":{"children_recorded":[],"earliest_dated_son":null,"earliest_dated_daughter":null,"second_dated_son":null,"second_dated_daughter":null,"third_dated_son":null,"third_dated_daughter":null,"naming_controls":{"matches":0,"mismatches":0,"factor":1.0,"details":[]},"candidates":[],"method":"Automated leads use birth surnames—not married surnames—as parental eligibility, role-specific biological age limits, bounded and approximate-date uncertainty, household chronology, specific time-aware localities, mapped distance, tenancy succession, migration destinations and sex-aware Scottish naming positions across generations. People already attached as the subject's parents stay in the identity summary and are excluded from this alternative-candidate list, regardless of relationship confidence. The main calibration uses clues available on disconnected profiles; existing parent and sibling links are retained as comparison context rather than treated as transferable evidence. Common ordered names and grandparent-to-child echoes receive a small non-zero weight, so a John or James match can support several independent criteria without producing a lead alone. Rare names, repeated bearers and bundles across otherwise distinct branches receive substantially more weight according to catalogue frequency. An exact migration place is weighted by its rarity and repetition across both branches; a shared destination country is worth only one point. Extra weight is added only when at least three independent clue types converge: naming, locality, specific migration, household chronology or collateral networks. Sparse profiles retain a clearly labelled chronology-only fallback instead of disappearing. Countries, states, counties and research clusters do not count as a shared locality, and fallback, broad representative or kin-inferred coordinates are excluded from distance scoring. Shared descendant profiles are removed before branch-name comparison. A candidate already recorded as a parent-in-law is excluded. A confident or independently supported parent is treated as settled; uncertain and unassessed attachments remain open to alternative comparison. A different linked parent, an uncle/aunt or grandparent path, and a matching existing child profile prevent an alternative from being classified as a strong direct-parent lead until the underlying tree conflict or duplicate is resolved. Familiar forms such as Bessie are normalised. Surname remains an eligibility filter worth zero points.","warning":"Naming customs, shared farms and occupations are circumstantial. Children, spouses and collateral relatives may be missing, and tree-derived family networks are not independent evidence. Scores rank research leads; they do not prove parentage."}}