Olive E. (Cooper) Northup 1889–1971

Result: NO PARENTS. Like her sister's, the entry is indexed under her as a PARENT and gives only "Olive E Mitchell / Spouse Everette E Northup / Child Sadie May Northup". The hint on [G.698] said an SS application "names both parents in full"; for this record it does not, and the expectation was the catalog's own. ONE REAL GAIN: SHE IS INDEXED "OLIVE E MITCHELL" IN A FEDERAL RECORD, which corrects this file's own first account of where the Mitchell surname came from - see the body. AND ONE FALSE GAIN, MADE AND WITHDRAWN THE SAME HOUR. The panel's "Misses Olive EDNA Mitchell" (Nebraska) was read as giving her middle name, and middle: was changed from "E." to "Edna". IT WAS WRONG AND IS REVERTED - see the nebraska search row below for what the record actually says.

Result: JUDGED NOT HER, AND THE CHANGE IS REVERTED. Three things say so. (1) THE NEWSPAPER DOES NOT SAY "OLIVE EDNA". The record's own source url carries the search terms "Misses_Olive_and_Edna_Mitchell" - the page reads "Misses Olive AND Edna Mitchell", TWO GIRLS. The index concatenated them into one name and dropped the "and". (2) THE DATE IS WRONG FOR HER: 12 January 1922, Neligh, Nebraska. Our Olive had been Mrs. Northup since August 1909 ([J.581]) and had at least four children by 1922; she was not a "Miss Mitchell". (3) EVERY SUGGESTED RECORD ON THE PAGE TRACKS SOMEONE ELSE - Edna M. Mitchell of Nebraska, who became EDNA M. SCHWARTING, with her own birth index, marriage index, death index and Find a Grave entries. That is the Edna of the pair, and she is no relation. THIS COLLECTION CARRIES ANCESTRY'S AI WARNING, like the marriage index that misdated her wedding by a week - and this file had already written that warning down before making this mistake on the same kind of source. IT ALSO CLEARS THE KANSAS "Edna M Mitchell" hit on the same panel, which is the same woman and is judged not her without opening it.

Result: PARSED -> [G.698]. Full dates and places, her cemetery, her husband's forenames, EIGHT children with memorial ids, and - the most useful line - her birthplace as GLADE, PHILLIPS COUNTY, KANSAS, the same village as her sister's. This file was a stub with a bare "1889" four hours earlier.

Result: Not in this collection, and the reason is almost certainly coverage rather than absence. The collection describes itself as "county marriage records from various counties in Kansas", sourced from "Various Kansas County District Courts and Kansas State Historical Society" - and unlike the Kansas probate collection 9065, which publishes a browse menu of its 44 counties, this one publishes no county list at all, so the exclusion cannot be read off a menu. What the four runs establish between them is that no Phillips County row surfaced in any of them, including a 1909 control that returned seven other counties. The record itself should exist. The FamilySearch wiki for Phillips County gives marriage records beginning 1872 and states "There is no known history of courthouse disasters in this county"; an August 1909 marriage falls well inside that. The wiki also says the probate judge holds the county's marriage records, which matches [J.581] exactly - the couple were married by "Probate Judge Cole". So this is a courthouse request rather than a search. See t1.

Result: (a) is a weak null and is recorded as one: a tight four-field query against an index, not a statement about what the county's volumes contain. (b) is not run, and is not a null. FamilySearch had signed this session out overnight and the catalog redirected to a sign-in page; Claude enters no credentials. The catalog check is the one test that would settle whether the Phillips County marriage volumes are filmed and open, and it is the cheapest thing still unrun on this question. It needs the maintainer to sign in.