Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create initial draft of the eventType vocabulary #107

Closed
timrobertson100 opened this issue Apr 1, 2022 · 8 comments
Closed

Create initial draft of the eventType vocabulary #107

timrobertson100 opened this issue Apr 1, 2022 · 8 comments

Comments

@timrobertson100
Copy link
Member

There will soon be a proposal to add eventType as a term in Darwin Core, to be used in the event core schema and beyond. This will surely need to accommodate a large variety of concepts but over time an upper taxonomy may be achievable to structure these.

In order to support the GBIF/ALA developments to bring SamplingEvent search and the ongoing work to Diversify the Data Model we're working through a series of exemplar datasets which require this vocabulary.

I suggest we draft what is necessary for these case studies as a start in the form of a simple CSV containing concept, parentConcept, definitionInEnglish. This will be sufficient to quickly bootstrap a vocabulary in the UAT Vocab Server enabling the integration into the pipleines.

@timrobertson100
Copy link
Member Author

CC @charvolant

muttcg added a commit to gbif/dwc-api that referenced this issue Apr 1, 2022
muttcg added a commit to gbif/dwc-api that referenced this issue Apr 1, 2022
@timrobertson100
Copy link
Member Author

timrobertson100 commented Apr 12, 2022

Please see https://registry.gbif-uat.org/vocabulary/EventType/concepts

This was created using

touch /tmp/empty.csv
java -cp vocabulary-importer/target/vocabulary-importer-0.49-SNAPSHOT.jar org.gbif.vocabulary.importer.CliApp \
--vocabularyName "EventType" \
--vocabularyLabelEN "Event Type" \
--vocabularyDefinitionEN "An early draft of a vocabulary for DwC:eventType, developed to support the pilot work on the ALA and GBIF. See https://github.com/gbif/vocabulary/issues/107" \
--conceptsPath "/tmp/eventType.csv" \
--csvDelimiter ";" \
--apiUrl "https://api.gbif-uat.org/v1/" \
--apiUser "trobertson" \
--hiddenLabelsPath "/tmp/empty.csv" \
--apiPassword

and eventType.csv which was provided by @charvolant

@CecSve
Copy link
Collaborator

CecSve commented Jul 12, 2024

Should MediaSample be a concept? It seems more like a BOR than the other concepts and I cannot come up with an example of when an event would happen because of 'media', as I can imagine for bioblitz, expedition etc.

Since the issue is closed, maybe this discussion need to happen elsewhere?

@tucotuco
Copy link

As MediaSample, no, as that indicates an instance of Media, but an Event to capture a MediaSample (such as a camera tap photo, does seems reasonable, but I would cast that as an Event, such as MediaSampling, or MediaCapture.

@CecSve
Copy link
Collaborator

CecSve commented Jul 13, 2024

As MediaSample, no, as that indicates an instance of Media, but an Event to capture a MediaSample (such as a camera tap photo, does seems reasonable, but I would cast that as an Event, such as MediaSampling, or MediaCapture.

Wouldn't deployment make sense for camera traps? Or I could get confused about the filename deployments in a camtrap dp archive. But I was thinking:

├── Event
│ ├── Deployment
│ │ └── MediaSampling/MediaCapture
│ │ └── Video
│ │ └── Audio
│ │ └── Photograph

This would cover various equipment methods that generate a media output used for species detection.

@timrobertson100
Copy link
Member Author

Wouldn't deployment make sense for camera traps?

Yes, and could either reflect the event of setting it/them up allowing configuration information to be attached, or the full duration of the camera(s) while in position ("we deployed cameras for 3 months..."), or both when used in a hierarchy.

MediaCapture sounds like a good name for the type of events that produce audio, video or photograph entities.

@tucotuco
Copy link

This example highlights something interesting to try to be aware of going forward. The hierarchy in the eventType vocabulary must be a hierarchy of eventTypes, not a hierarchy of Events.

So, for example, a MediaCapture Event might have a Deployment parent Event, but that does not mean that a MediaCapture Event is a subtype of Deployment Event. I would consult the Camera Trap people for their understanding of this, but to me the MediaCapture is not a Deployment subtype.

@CecSve
Copy link
Collaborator

CecSve commented Aug 7, 2024

So, for example, a MediaCapture Event might have a Deployment parent Event, but that does not mean that a MediaCapture Event is a subtype of Deployment Event. I would consult the Camera Trap people for their understanding of this, but to me the MediaCapture is not a Deployment subtype.

Yes, that makes sense and is worth asking camtrap people. If I were a publisher coming with camtrap data, I would be unsure which eventType to use in such a case. Currently, the concept Deployment does not have any children that seem to fit. Detection and the child SensorDetection seems like a possible fit, but then MediaSample with the Video or Photograph child (probably more often this) could work as well.

What would be an example of a MediaCapture eventType IRL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants