Discuss

1. Something else happened with the Brown import. Zina Prescendia Young 54895 was overwritten by Abigail Abbot in the database. She is also listed as Male in the DB.
2. Meeting with Kathleen tomorrow at 1pm at IATH. Anything I should bring up?

To Do

• Continue thinking about equivalence classes of identities
  • Write things down, type them out
  • What are some other examples?
    • Circuses
    • Marriages
    • Citation graph: equivalence knob = institution level
      • With equvalence classes as institutions (corps or schools), they are evolving nodes with people that come and go from the institution, cite within the institution and across institutions
      • With equivalence classes as departments (within institutions), we can see how the smaller units inter-cite and interact as people move and cite.
      • There are some interesting metrics to be had here. Such as which departments/institutions are the most similar across time (cosine similarity)
    • Enron data: departments
    • Others? Can be real or fabricated.
    • Snac data?
  • What happens when these things don’t define equivalence classes?
    • With binary marriages as nodes, and the EC collecting marriages to a particular man (or woman), it’s easy to see this is an equivalence class
      • As time goes on, is it still an equivalence class? Worthy seemed to not want to define it as the same class. Its identity (definition = marriages to person X) stays the same across time, but its content (marriages included in the class) changes as time goes on. What can we gather from this?
    • What about the citation graph, when people can be in multiple institutions (affiliated with UVA and Google, for example). The institutions aren’t realy equivalence classes because they overlap some (without being equal). Do we define it in a different way here? Do we relax some of the restraints of equivalence classes?
  • What about special cases when we’re looking at binary relations to build our equivalence class, and we have issues with transitivity. (I didn’t completely follow the example). But say we have A <--> B <--> C and they are an equivalence class if we look at them in the right order, A <--> B and B <--> C, but if we look at them differently, say A ??? C, they don’t appear to be in an equivalence class together.
    • I took from this (which Worthy suggested isn’t the right meaning) to consider if we collapse all nodes (binary relations) down to their equivalence classes and relations between classes, then consider how those change over time as opposed to doing the computation on the original graph over time, and computing the equivalence classes at each step from the graph itself.
      • That is, doing the simpler EC only computation vs the more complex overall-graph computations and overlaying the EC boundaries after computing
      • Overlay the EC boundaries and then compute vs compute and then overlay the EC boundaries
      • There is interesting computational questions here as well
    • The important point is to note, I think, how we are constructing and defining our equivalence classes (or whatever we call them). If we construct them based on pre-defined binary relations, we need to be careful to define them properly or to relax the transitivity property to ensure we capture the classes we’re intending to capture.
• Continue reading papers, make notes, be ready to share on Tuesday afternoon
• Start building these networks to do some of these metrics, specifically betweenness and closeness centrality
  • What are the computational challenges along the way?
• Start writing!
• Force directed graph ported from SNAC over to mormon db. Can I just use a SQL api, like I have been, to create the nodes/edges the way I have been using neo4j for snac?
• Don’t get distracted too much by the data entry or Mormon example specifically. Go for dissertation!

Todo

• Email Luther a link to the schema document pointing to nauvoo_data_test.
• Something to show Rick Turley by June 15
• Rewrite some of the queries on the polyandry questions from Jill’s DB
• Rerun the gephi graphs with the updated database now
  • Force directed graphs (try with the SNAC D3 visualization)
    • Before July 1, 44 (death of Smith)
    • 44 through Dec 9, 45 (how BY adds to the list)
    • Dec 10, 45 through March 46 (after the temple)
  • For all the Anointed Quorum (53-75 names)
  • For the Quorum of the 12
  • For the first 200 polygamous unions
  • For June
    • Sealings (no civil marriages), for the list of people Kathleen provides and all the people they are sealed to.
• Data Entry Page
  • when showing the marriages on the page, list the number of children of that marriage (it should be just another query for the number of people who have that marriage as their biological parent).
• Email Shayne about the nauvoo data dump from a month ago

Notes

• Kathleen would like a few changes to the data entry page
  • She would like to be able to “hide” the rest of the marriage data (Type, Spouse, and Date would always show up, then the rest would be able to be hidden – be able to be collapsed under that)
  • Fixing Brown or scrolling a different way. There is a lot of scrolling up and down to enter the $x$th marriage and having to come back up to see Brown.
• Interesting queries (research questions)
  • List of all mother-daughter pairs that enter the same marriage/sealing
    • (General: any pairs of nodes in the flow diagram that have multiple paths of different lengths connecting them)
  • How many marriages have people who are $X$ years apart in their ages
    • Go for all the marriages, calculate the number of years between the oldest and youngest wife, and show that as a distribution
      • Could do this for all, for a subset (AQ, etc), and slider for threshhold
• Intersting questions
  • Did JS seal people through their wives in the lack of an adoption sealing?
  • What happened to JS’s wives? How were they parcelled out?

To Do

• See Wunderlist
  • Small changes to the data entry page
  • Timestamps on the database for merging BYU data
    • We could do a diff of their last db dump and the current one to get what changed
  • Check on tuition payment next week
• Starting Monday
  • Continue getting organized
  • Reread papers, go over Bruno’s course notes, email Bruno
  • Continue thinking about:
    • equivalence classes,
    • sliding window of identity definition (what gets considered to be an equivalence class),
    • sliding window of time,
    • continuous-time evolving networks.

Agenda

• Questions on funding (see Wunderlist)
• Any new news about the updated database from Shayne? (Getting MSSQL into Postgres)?
• Two weeks I’ll be out over the summer, if possible
  • Likely June 13-21
  • June 28-July 4 (ASP)
• Would like to work on proposing by end of summer
  • Get document ready by June 28 (latest) and propose mid-July (latest)
• Still waiting on Wes for Math requirement
• Got a bill from student accounts, is that taken care of or should I deregister? (Due May 18)
• Go over the notes from the April 17 meeting with all, since they happened after Worthy left

Notes

• Interesting book to look up: Image Processing (textbook) by Rosenfield.
  • Reel-time processing of videos (only have one shot as the reel goes across the head)
• Sounds like these current works are doing joint probabilities and/or using adjacency matrices
  • We could have a big adjacency matrix, where each node is represented (even if it doesn’t exist at this particular time point). Then, as time progresses, nodes that show up will get edges and a weight.
    • What’s missing: Nodes that change identity or merge
• Nodes (something special about them that an adjacency matrix won’t capture)
  • Identity-defining characteristics don’t change OR they change the identity of the node
    • Ie: a merger at a point in time (think back to the circus diagram)
  • Other characteristics do change, though, which need to be captured about the node
  • What about merging nodes?
    • Can’t do adjacency matrix of all nodes that ever existed (as some groups do) because some are connected in a different way
      • ie, a node at one time might be the same identity as two nodes at a previous time who merged
      • Those nodes have a connection (linked identity across time), they are fundamentally connected, although different
  • So, we have an ancestor-like connection
    • It’s not an edge in the graph connecting two+ nodes at a given time, but it’s a connection at an identity level across time.
  • Equivalence Classes of Nodes: we can pick a window of identity to determine equivalence classes of nodes over time.
    • For the circus example, picking identity definition from 1919 will result in only one “type” of node all the way back, since the others merged in. This would show how the relations with “Ringling Bros and Barnum and Bailey” circus’ connections changed over time. However, picking an identity definition from 1881 would show 3 classes over time: Barnum and Bailey (the nodes that merge into this class in the past would be grouped together for all time), Ringling Bros, and then in 1919 something different would happen.
      
    • The Mormon marriages are another story, which we’ve already discussed but using the term “dual” inappropriately.
      • Let’s consider we have the marriage lineage flow, but where each node is only the binary marriages. So, this is the binary marriage diagram, in which there is only one husband and wife per marriage.
      • We can set the identity window to group marriages identified by the man into an equivalence class, so we’d have an equivalence class per man in our database. This defines the patriarchal marriage diagram. All the marriages for a man are grouped together, and we then consider them one node in our network.
      • However, we can also group by woman to get female-oriented equivalence classes and the matriarchal marriage diagram.

To Do

1. Fix the user interface
   • Remove “second annointing” from NMS tab DONE
   • Possibly change “Annointed To” to something else, or remove altogether
   • When a person creates a new item, it sends id=NEW to the save button, but doesn’t get the actual ID back. DONE
     • So, every save it creates a new one
2. Change the database
   • Non-marital Sealings DONE
     • change MarriageProxyID to a FatherProxyID and MotherProxyID and split those out on the data entry page
     • NOTE: there are some in our db, so will need to split them out in the process.
   • I Don’t really understand these
     • Church Status
       • Priesthood Office
     • Quorum/Council (GROUPS)
       • I think these are “ChurchOrganizations” and “ChurchOrganizationMemberships”
       • Want: start/end date (already have there)
   • A person may be a member of a group, and then may have roles in that group. So, see the example below:

       Example data entry page tab 
     
       -
       | Group ___________________
       | Join date __ / __ / ____
       | Leave date __ / __ / ____
       |
       | Roles (optional to add)
       | | Role: ___________________
       | | Start Date __ / __ / ____
       | | End Date   __ / __ / ____
       | | Officiator: ___________________
       | -            
       | | Role: ___________________
       | | Start Date __ / __ / ____
       | | End Date   __ / __ / ____
       | | Officiator: ___________________
       | -
       | ...
       -
       | Group ___________________
       | Join date __ / __ / ____
       | Leave date __ / __ / ____
       |
       | Roles (optional to add)
       | | Role: ___________________
       | | Start Date __ / __ / ____
       | | End Date   __ / __ / ____
       | | Officiator: ___________________
       | -            
       | | Role: ___________________
       | | Start Date __ / __ / ____
       | | End Date   __ / __ / ____
       | | Officiator: ___________________
       | -
       | ...
       -
       ...
       

3. Dates to look at:
   • Could have dates that are not start/end dates, but a “was a ___ at this point in time,” so they were something at this time. So, it would be helpful to have “earliest known” and “latest known” dates, so that this other information could be included until the official dates can be found. For example, Brown lists FD Richards as a HP, but doesn’t say when. So we can put a date that he was a high priest at least by the time Brown was listing entries (1845), but we don’t know when he became a high priest.
     • Idea 1: add 2 more date fields for as early as and as late as.
     • Idea 2: add “<” and “>” to our date formats (this is not as good as the last idea)

TO DO

• Immediately: Add save of the notes in the data entry form to put them somewhere in the database!!!!!
  • For now, combine them and put them in the Private Notes field of the person
  • Have a checkbox to save only notes (so the other data doesn’t get fiddled with)

Notes

• We’d like to see where people live in relation to each other
  • Possibly adding neighbor relations in the marital chords
  • Possibly using a map and plotting the same family/tribe on the map, then showing how they went across the plains (who went in the same wagons and who didn’t
• Marriage flow chart
  • Gets her close to one of her big “gets”
• Affinity groups in a chord
  • Show a chord diagram with members on the left
    • Legend on various definitions of “first generation” and “adoptions” and highlight those individuals
  • The right side has the affinity groups, and chords to the people who participated in these groups
    • Show who participated in each group
    • Ex: neighbors, other affinity groups