eventID and parentEventID in occurrence core mapping?

[rukayaj]

I just noticed that parentEventID and eventID fields are present when you add mapping for an occurrence core.

Perhaps this was always here and I just never noticed, but what actually happens if you use these? Does the GBIF UI group occurrences by the eventIDs like it would with an event core dataset?

Also the star schema isn't really applied I guess? Because when you then try to map e.g. a simple multimedia extension it is linked to the occurrenceID, not eventID.

[ManonGros]

Hi @rukayaj, they were always there as far as I know. To answer your questions:

Does the GBIF UI group occurrences by the eventIDs like it would with an event core dataset?

Yes

when you then try to map e.g. a simple multimedia extension it is linked to the occurrenceID

Yes

[rukayaj]

Ok thanks! Then I think it makes most sense to publish this dataset with events as an occurrence dataset, as we want to link our images to the occurrences. Does that sound sensible to you?

[ManonGros]

Yes I think it makes sense.

[rukayaj]

Cool! Thanks for your advice :) then I'll close this

[albenson-usgs]

Just wanted to share an example of an occurrence core with eventIDs so you can see what it looks like https://www.gbif.org/dataset/8a5cbaec-2839-4471-9e1d-98df301095dd. Notice that the events still get grouped and shown on the dataset page even though it's an occurrence core dataset.

[rukayaj]

Very helpful, thanks @albenson-usgs ! I feel like this is quite a well hidden "illegal" dwc move ;)

[dagendresen]

Yes, eventID was present in Darwin Core and the IPT core schema since long before the IPT sampling event core was created (by a process around the EUBON project 2012-2017). The European Nodes started exploring the (then new) sampling event core at the regional nodes meeting in Lisabon in 2016.

The purpose of creating the IPT sampling event core was/is to (1) enable the sampling events to be described (with metadata about them) and for IPT extensions to be able to (2) extend the description of them (with more attributes).

With the IPT Occurrence core, you can refer to Events but you can not describe the Events.

(I do think we should rather than publishing IPT Occurrences as an extension to IPT Event core datasets, we could rather explore publishing the Events in separate independent "sibling datasets" -- and interlinking across with stable persistent PIDs as the eventIDs --- anything less is only creating false hopes and pseudo-usefulness --- simply only displaying the Occurrences grouped by Events in the GBIF portal does NOT really achieve anything fundamentally useful?)

[rukayaj]

Tagging @ymgan as she is interested