content
; most events that enter the system also have a variety of other fields, especially typeId
, startedOn
, endedOn
, properties
, and subjectEntityIds
.eventTypes
value in metadata typecontent
fields that would benefit from a shorter, summarized textstartedOn
or endedOn
are populated, event will not display on any Timeline viewstartedOn
or endedOn
are populated, event will not display on timelinecontent
fields that can be split into multiple events"sourceEventIds": [{ "ID123456789", "ID987654321"}]
content
fieldcontent
field, automatically extracted and identified through the product's physical quantity extraction service"measures": [{ "typeId": "String", "value": Float}]
Measures are separate from Quantities in that they are specifically defined by "type"
For example, some measurements in "inches" indicate the size of the hole (a specific definition) and thus are put into themeasures
field with the labelholeSize
Other "inches" that are not hole sizes (an unspecified definition) could exist inquantities
with the unit valuein
content
field, generally extracted through WellLine's algorithms"quantities": [{ "unit": "String", "value": Float}]
Quantities are separate from Measures in that they are not specifically defined by "type"
For example, some measurements in "inches" indicate the size of the hole (a specific definition) and thus are put into themeasures
field with the labelholeSize
Other "inches" that are not hole sizes (an unspecified definition) could exist inquantities
with the unit valuein
"properties": [{ "name": "String", "value": "String"}]
"subjectEntityIds": [{ "entityType.String"}]
content
fieldcontent
field"referenceEntityIds": [{ "entityType.String"}]
1{"id": "depthTVD", "name": "Depth TVD meters", "units": "m", "description": "Total vertical depth, in meters"}2{"id": "depthMD", "name": "Depth MD meters", "units": "m", "description": "Measured depth, in meters"}Copied!
1{"id": "geology", "name": "Geology", "description": "Grouping for geologic entities", "groupId": "all"}2{"id": "problem", "name": "Problem", "description": "Grouping for problems", "groupId": "all"}3{"id": "well problem", "name": "Well Problem", "description": "Grouping for problems with a well", "groupId": "problem"}Copied!
1{"id": "lithology", "name": "Lithology", "description": "Lithology", "groupId": "geology"}2{"id": "problem_ballooning", "name": "Ballooning Problem", "description": "A ballooning problem at a wellsite", "groupId": "well problem"}Copied!
1{"id": "drilling", "name": "Drilling", "description": "An event group from a Public Dataset.", "groupId": "all"}2{"id": "formation evaluation", "name": "Formation Evaluation", "description": "An event group from a Public Dataset.", "groupId": "all"}3{"id": "interruption", "name": "Interruption", "description": "An event group from a Public Dataset.", "groupId": "all"}Copied!
typeId
field of events.1{"id": "drilling - circulating conditioning", "name": "Circulating & Conditioning", "description": "An event from a Public Dataset.", "groupId": "drilling"}2{"id": "formation evaluation - circulating conditioning", "name": "Circulating & Conditioning", "description": "An event from a Public Dataset.", "groupId": "formation evaluation"}Copied!
{
}
).string
type fields that should be surrounded by quotes. The notable exceptions are "startedAt", "endedAt", and "importance".summary
and content
fields.