# Split shared events

**URL:** <https://gramps.discourse.group/t/split-shared-events/5855>\
**Category:** Help\
**Created:** [August 10, 2024, 10:25pm UTC](https://gramps.discourse.group/t/split-shared-events/5855 "2024-08-10T22:25:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![moorob](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/moorob/32/586_2.png) [@moorob](https://gramps.discourse.group/u/moorob)\
**Post date:** [August 10, 2024, 10:25pm UTC](https://gramps.discourse.group/t/split-shared-events/5855/1 "2024-08-10T22:25:08Z")

</div>

Is there a way or addon that will take shared events and convert them to individual events for each person. When I export a gedcom, it only records the primary event and drops the other people sharing event say when working with census records.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [August 11, 2024, 8:33am UTC](https://gramps.discourse.group/t/split-shared-events/5855/2 "2024-08-11T08:33:24Z")

</div>

I need some expansion on your question.

Are you using form data for the Census data? (I have very limited experience with how it stores data.) And what program are you using to import the data?

But an underlying problem is that GEDCOM 5.5.1 doesn’t handle Role data well. It is one of the design flaws that caught a lot of flak over the years. The only option to communicate an event Role is oddly in the Source structure! That’s addressed in GEDCOM7

Note that the GEDCOM Extensions and GedcomforGeneanet addons were written to support [exporting Witness roles](https://sourceforge.net/p/gramps/mailman/gramps-users/thread/1453076354569-4673965.post%40n4.nabble.com/#msg34773952) and Associations respectively. Both targeted Geneanet.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [August 11, 2024, 1:11pm UTC](https://gramps.discourse.group/t/split-shared-events/5855/3 "2024-08-11T13:11:34Z")

</div>

You might also want to read the comment by @Nick-Hall in the Forms development thread by @RenTheRoot about how GEDCOM7 uses the ASSOciation tag to handle Roles that are not Primary or Family.

> [@Plans to Update Forms Addon Over the 2024 Summer](https://gramps.discourse.group/t/plans-to-update-forms-addon-over-the-2024-summer/5274/83):
>
> Yes, clicking a button to generate new conclusion events according to user settings is a good idea. Step 1: enter the transcription and then step 2: generate or regenerate objects. In Gedcom 7.0 it is now possible to have an ASSO tag under an event. This is how they model multiple participants for an event. There is a ROLE tag under the ASSO tag. There are some roles that we are missing. They now have Father, Mother, Parent, Child, Friend, Neighbour, Officiator and Multiple (for multiple …

---

<div class="post-metadata">

**Author:** ![moorob](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/moorob/32/586_2.png) [@moorob](https://gramps.discourse.group/u/moorob)\
**Post date:** [August 11, 2024, 10:19pm UTC](https://gramps.discourse.group/t/split-shared-events/5855/4 "2024-08-11T22:19:31Z")

</div>

What I was asking is for any event that is shared, on export to gedcom, only the primary is exported but not anyone who marked with something else. I was looking for a way to split the shared event into individual event for each person. This would make it easier to send a gedcom to someone else who isn’t using gramps to be able to import without losing events.

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [August 11, 2024, 10:33pm UTC](https://gramps.discourse.group/t/split-shared-events/5855/5 "2024-08-11T22:33:16Z")

</div>

You only need to export the event once under the person/family with the primary role. Participants with a non-primary role can be linked back using ASSO tags.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [August 11, 2024, 10:50pm UTC](https://gramps.discourse.group/t/split-shared-events/5855/6 "2024-08-11T22:50:00Z")

</div>

The only way to duplicate the Events for the GEDCOM export would be (on a disposable back copy of the Tree) to change the Roles to “Primary” for People Events and to “Family” for Families Events.

That’s probably best done with a SuperTool script that adds the non-standard Role to the Event description before changing it.

There’s an example script that splits Residence Events so there’s a Duplicate for each Citation.

> [@Supertool script to separate Residence events](https://gramps.discourse.group/t/supertool-script-to-separate-residence-events/5472):
>
> I decided try Supertool to fix some inaccuracy in my DB. I want separate my Residence events which have multiple citations. Each Residence event should have only 1 citation. And Residence date should be the same as citation date. Places for separate Residences should be the same as for common one. I’ve already found all needed people, events and citations. But I need some help: How create new events and attach citations inside by hande? How detach citation from event by hande? How detach even…

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\
**Post date:** [September 10, 2024, 10:50pm UTC](https://gramps.discourse.group/t/split-shared-events/5855/7 "2024-09-10T22:50:10Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
