5.2 topics for discussion

Development Beta Testing
1
  1. How should we handle multi-layer citations?
  2. What is the best way to store citation urls and access timestamps?
  3. Should conflicting evidence be stored as multiple events or maybe use attributes or some other method?
  4. How do we want to model ships? As places or a new object type?
    [previous comment]
  5. Would time dependent facts be useful? If so, should they be distinct from attributes?

GEDCOM related

There is also the bigger question. How close do we want to keep to the Gedcom standard?

  1. Do we want to support the Gedcom non-event structure?
  2. Do we want to introduce a persona concept (Gedcom ALIA tags)?

The answers to these questions could affect the best practices that we recommend.

We probably want to start several topics to discuss these.

1 Like
2

Quick reaction, just thinking loud:

  1. Expand the source object with properties that currently exist in citations, like date and volume page. And allow each source object to reference another one as its container, of which it’s a part, or a sub source, and as something that it’s derived from, so that a transcription can reference the source/page from which it’s derived. FamilySearch does this on-line, and also supports this in GedcomX.
  2. In the source object, which is sort of the source and citation merged. I call it source, because there is already a top level SOUR object in GEDCOM 5.5.1 and 7,
  3. I’d love to mark a particular event as verified, so that, when I merge a person from my own tree with the same person imported from another, and the merged person has two such events, like two births, I still know which one I checked,
  4. Ships can be places, enclosed by a sea, or an ocean, whatever you like,
  5. No. Facts and events should be treated as similar, where facts may exist without a date, just like events already can. RootsMagic does that, and we should allow them as substructures of persons, families, places, etc., meaning that facts and events are represented by the same object, which can be either embeded or shared. This makes exporting (to GEDCOM) easier too,
  6. What’s that?
  7. Yes, please.
3

Another quick thought about 4.

Ship, etc is too granular. I have people who were born on a train, for example and I continually hear of people who were born in a car.

I propose an entry “In Transit” with types ‘ship’ , ‘car’, ‘aircraft’, ‘train’, etc.

The notes can elaborate, then.

Brian