# Shared collecting events **URL:** \ **Category:** Office Hours\ **Created:** [June 22, 2026, 10:46pm UTC](https://speciforum.org/t/shared-collecting-events/3781 "2026-06-22T22:46:44Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\ **Post date:** [June 23, 2026, 6:31pm UTC](https://speciforum.org/t/shared-collecting-events/3781/2 "2026-06-23T18:31:13Z")
Hi @acoconis, Thanks for your question! Whenever there is a unique set of coordinates, there must be a corresponding unique Locality. Specify requires that each Collecting Event (CE) be linked to only one Locality, and each Collection Object (CO) can connect to only one CE. Due to this, in cases where each CO has a unique Locality, it is better to use embedded CEs when the events are grouped together for some reason using something like [Collecting Trip (CT)](https://sp7demofish.specifycloud.org/specify/data-model/#collectingtrip). This groups multiple CEs into an expedition or field trip. This can track the trip’s start/end dates, participants, and purpose. If you use [shared CEs](https://speciforum.org/t/shared-vs-embedded-records-configuration/1712), we recommend giving some number or identifier to each so that it can be searched and added to other COs. If you use [embedded CEs](https://speciforum.org/t/shared-vs-embedded-records-configuration/1712), there is no need to assign an identifier, as it is unique to each CO and can be retrieved via query when searching for that CO. --- _[View the full topic](https://speciforum.org/t/shared-collecting-events/3781)._