# Shared events and participants reporting **URL:** \ **Category:** Help\ **Created:** [January 20, 2024, 6:36pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712 "2024-01-20T18:36:59Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![drjimbo](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/drjimbo/32/3930_2.png) [@drjimbo](https://gramps.discourse.group/u/drjimbo)\ **Post date:** [January 20, 2024, 6:36pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/1 "2024-01-20T18:36:59Z")
GRAMPS offers ways of sharing events, but the standard reports e.g. [Complete Individual Report](https://www.gramps-project.org/wiki/index.php/Gramps_5.2_Wiki_Manual_-_Reports_-_part_6#Complete_Individual_Report) do not include other participants of these events, which would facilitate understanding of the context. Whilst using event description for bmds is a workaround, why should it be necessary to enter the data twice? With census data this is not reasonable. Has anyone modified the complete individual report to handle shared event participants? 5.1.1 W11 ---
**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:** [January 20, 2024, 11:15pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/2 "2024-01-20T23:15:01Z")
> [@drjimbo](#): > > event description for bmds is a workaround Pardon? What is “bmds”? Ah… Birth, Marriage and Death Records (BMDs). Always have problems with un-introduced acronyms ---
**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:** [January 20, 2024, 11:59pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/3 "2024-01-20T23:59:56Z")
A shared Event would be a bit complicated to include in the report. Take the example of the Marriage [E2815] for the Home Person of the example.gramps tree. There isn’t a natural order for the Roles of the Participants. So any combined list is going to be a mess: ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/6/60028b31b31b4fa4faa9387ea2bfd4c6bb8350d1.png) ---
**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:** [January 21, 2024, 2:18pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/4 "2024-01-21T14:18:18Z")
A contributor just [submitted a patch for the Narrated Website report](https://github.com/gramps-project/gramps/pull/1633) to include Shared Event participants and their roles. ---
**Author:** ![drjimbo](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/drjimbo/32/3930_2.png) [@drjimbo](https://gramps.discourse.group/u/drjimbo)\ **Post date:** [January 21, 2024, 7:35pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/5 "2024-01-21T19:35:43Z")
Complicated or not, if I cannot get the information out in such a report, it begs the question of why enter the data in the first place. Surely, at some point, every user will want a printed report of the data after analysis and verification. A simple list of an individual’s events short changes all the effort taken at data entry. I appreciate that the original report(s) met needs at the time, but perhaps there should be a strategy in place to ensure reporting features keep in step with increased capabilities for data entry. ---
**Author:** ![drjimbo](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/drjimbo/32/3930_2.png) [@drjimbo](https://gramps.discourse.group/u/drjimbo)\ **Post date:** [January 21, 2024, 7:36pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/6 "2024-01-21T19:36:10Z")
Thanks, I’ll have a peep. ---
**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:** [January 21, 2024, 7:52pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/7 "2024-01-21T19:52:48Z")
> [@drjimbo](#): > > Complicated or not, if I cannot get the information out in such a report, My observation that something is ‘complicated’ does not equate to: “cannot be done”. It means: “let’s discuss ways that it can be made less complicated.” With shared Events, the complication is that the Roles are not prioritized. Which means a list of participants is bound to be disordered. The only absolutes are that ‘Primary’ and ‘Family’ roles are the key roles. With children, the order of individuals is by creation order. But the user can manually override. And there is a tool to do mass re-ordering by birth (or its fallback) date. Roles are ordered alphabetically in the pop-up menu for the built-ins followed by the custom Roles. They have no inherent priority, not even for the Primary/Family roles. ---
**Author:** ![GeorgeWilmes](https://avatars.discourse-cdn.com/v4/letter/g/c57346/32.png) [@GeorgeWilmes](https://gramps.discourse.group/u/GeorgeWilmes)\ **Post date:** [January 21, 2024, 8:03pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/8 "2024-01-21T20:03:44Z")
> [@emyoulation](#): > > Roles are ordered alphabetically for the built-ins followed by the custom Roles. They have no inherrent priority, not even for the Primary/Family roles. For what it might be worth, there are these underlying numeric values in eventroletype.py: ``` UNKNOWN = -1 CUSTOM = 0 PRIMARY = 1 CLERGY = 2 CELEBRANT = 3 AIDE = 4 BRIDE = 5 GROOM = 6 WITNESS = 7 FAMILY = 8 INFORMANT = 9 ``` ---
**Author:** ![drjimbo](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/drjimbo/32/3930_2.png) [@drjimbo](https://gramps.discourse.group/u/drjimbo)\ **Post date:** [January 21, 2024, 8:18pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/9 "2024-01-21T20:18:42Z")
I think the important bit is to get the data out as a set in a usable format that can be formatted as the user wishes. If multiple participants in the same role were grouped, that would be a bonus. ---
**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:** [January 21, 2024, 8:38pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/10 "2024-01-21T20:38:15Z")
> [@GeorgeWilmes](#): > > For what it might be worth, there are these underlying numeric values in eventroletype.py: > > > > ```python > UNKNOWN = -1 > CUSTOM = 0 > PRIMARY = 1 > CLERGY = 2 > CELEBRANT = 3 > AIDE = 4 > BRIDE = 5 > GROOM = 6 > WITNESS = 7 > FAMILY = 8 > INFORMANT = 9 > > ``` …and these are the [Association Roles in the GEDCOM7 specification](https://gedcom.io/specifications/FamilySearchGEDCOMv7.html#enumset-ROLE): | Value | Meaning | | --- | --- | | CHIL | Child | | CLERGY | Religious official in event; implies OFFICIATOR | | FATH | Father; implies PARENT | | FRIEND | Friend | | GODP | Godparent or related role in other religions | | HUSB | Husband; implies SPOU | | MOTH | Mother; implies PARENT | | MULTIPLE | A sibling from the same pregnancy (twin, triplet, quadruplet, and so on). A PHRASE can be used to specify the kind of multiple birth. | | NGHBR | Neighbor | | OFFICIATOR | Officiator of the event | | PARENT | Parent | | SPOU | Spouse | | WIFE | Wife; implies SPOU | | WITN | Witness | | OTHER | A value not listed here; should have a PHRASE substructure | ---
**Author:** ![SNoiraud](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/snoiraud/32/72_2.png) [@SNoiraud](https://gramps.discourse.group/u/SNoiraud)\ **Post date:** [January 22, 2024, 11:30am UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/11 "2024-01-22T11:30:39Z")
> [@emyoulation](#): > > A contributor just [submitted a patch for the Narrated Website report](https://github.com/gramps-project/gramps/pull/1633) to include Shared Event participants and their roles. It will not work on a gramps 5.1. This patch is against master. ---
**Author:** ![SNoiraud](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/snoiraud/32/72_2.png) [@SNoiraud](https://gramps.discourse.group/u/SNoiraud)\ **Post date:** [January 22, 2024, 2:08pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/12 "2024-01-22T14:08:31Z")
> [@SNoiraud](#): > > This patch is against master. It does not work on master. ---
**Author:** ![drjimbo](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/drjimbo/32/3930_2.png) [@drjimbo](https://gramps.discourse.group/u/drjimbo)\ **Post date:** [January 23, 2024, 1:16pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/13 "2024-01-23T13:16:42Z")
That’s a pity. Hopefully, it will be fixed by the time v5.2 is released. It’s an important contribution and hopefully will be extended to the complete individual report. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\ **Post date:** [February 22, 2024, 1:17pm UTC](https://gramps.discourse.group/t/shared-events-and-participants-reporting/4712/14 "2024-02-22T13:17:00Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.