Drag-and-Drop Menu

The Drag-and-Drop menu is a way to copy or merge entities within the same genealogy or across genealogies.

Most of these actions are additional to the ones you can find in the menu bar, keyboard shortcuts, toolbar and context menu.

You access the Drag-n-Drop menu by clicking on an entity (individual, family, source, etc.) and dragging it to another one.




Drag-and-Drop menu across different genealogies, of an individual over another individual Drag-and-Drop menu within the same genealogy, of an individual over another individual



The Drag-and-Drop menu has a title, a description and a list of action items.

The description indicates what the Drag-and-Drop move was:

  • On the left hand side is indicated the imported entity you clicked and the originating genealogy
  • On the right hand side is indicated the target entity you dropped it on to, and the corresponding genealogy

The list of action items depends on the move you made and if the genealogies are different or not.

The examples above show action items which are generally organised in 3 sections:

  • Attachment actions depending on the combination of entities involved
  • Copy actions if genealogies are different
  • Merge actions if the genealogies are the same

Access to the menu: the views from which Drag-and-Drop menu is available are the same ones as the ones from which the Context Menu is available. Refer to the Context Menu page for details.

Possible and forbidden drops: when a drop is possible, the mouse cursor shows a square and a "plus" sign with it, indicating the dragged entity will be copied or attached to the one under the cursor. When a drop is not possible, the mouse cursor turns into a forbidden sign.

A drop is forbidden when no relevant action correspond to the move. For instance, it does not make much sense to drop an entity on itself, hence a forbidden sign in that sequence.

Similarly, it does not make sense to drop a Family entity over a Multimedia entity. The other way around makes sense and is possible.

Disabled moves: when a move is likely to create a major inconsistency, Ancestris shows the action as disabled. This is to help you understand that your move has been taken into account but is not allowded. For instance, attach an individual a a parent of another one in a family where both parents are already documented is not possible. You would need to first decide which parents are the right ones and fix the family before doing the move.

Warning moves: when a move is liky to create an inconsistency but is still possble in practice, Ancestris add a warning sign to the action icon, and a tooltip on the action, explaining the reason of the warning. Ancestris shows a warning sign to alert you against potential errors. For instance, adding a child to a family when the person is already a child in another family is only a warning, bacause such situations could exist. Similarly, a person can be a spouse in several families.

Attachment actions

Attachment actions offer possibilities to attach the imported entity to the target entity.

If genealogies are different, the imported entity is first copied to the target genealogy. This copy includes the linked entities, as described below in the Copy actions.

Individual to individual

When attaching an individual to another one, Ancestris offers 4 possible ways to do it:

  • Attach as a parent
  • Attach as a spouse
  • Attach as a sibling
  • Attach as a child

For each possibility, Ancestris offers to use an existing family or to create a new one.

Individual to family or Family to Individual

When attaching an individual to a family, or vice versa, Ancestris offers 2 possible ways to do it:

  • Attach as a spouse
  • Attach as a child

Attribute to Individual or Family

An attribute is an entity which is not a person nor a family (a note, a multimedia object, a source, a repository or a submitter).

When attaching an attribute to a indivudual or a family, Ancestris offers to attach it to the entity itself at a general level, or else to attach it to one of the existing events of that entity.

For instance, it is possible to attach a Source to the Birth event using Drag-and-Drop.

Attribute to Attribute

When attaching an attribute to another attribute, Ancestris offers to simply attach one to the other according to the Gedcom compliance.

For instance, a Repository can be attched to a source, but a source cannot be attached to a repository.


Copy actions across different genealogies

When genealogies are different, Ancestris offers 2 ways to copy the imported entity to the target genealogy.

  • Copy the entity without the linked entities
  • Copy the entity with the linked entities

In the first case, a family would only be copied with the events, but without parents and children ; an individual would be copied without the links to other individuals and without the links to entity sources or to multimedia.

In the second case, a family would be copied with both parents and all children ; an individual would be copied with the relevant Notes, Multimedia and Sources ; sources would be copied with repositories.


Merge actions within the same genealogy

When genealogies are the same, Ancestris offers 3 ways to merge the imported entity to the target entity.

  • Merge the entity adding information only, i.e. without modifying information already documented in the target entity.
  • Merge the entity overwriting possible overlaps, i.e. replacing existing information if any.
  • Merge the entity with the help of the assistant, where you can choose which information to keep in the resulting entity.

If the same unique information exist in both entities, such as a birth date, the information is not copied in the first case, and is overwrttin in the second case. With the assistant, you choose.

If the information is not unique, it is added in the first case, or replaced in the second. This is the case for instance for names : a person ncan have more than one name.