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

New Class - Operation #217

Open
5 tasks
stansmith907 opened this issue Jun 12, 2019 · 4 comments · May be fixed by #322
Open
5 tasks

New Class - Operation #217

stansmith907 opened this issue Jun 12, 2019 · 4 comments · May be fixed by #322

Comments

@stansmith907
Copy link
Contributor

stansmith907 commented Jun 12, 2019

Class Definition: operation
"designations for the operation used to acquire the dataset"
See: ISO MI_Operation

Rules:

  • optional

Element Definitions:

  • operationId: ( character ) "a unique mdJSON system identifier for the operation" default: UUID
  • description: ( character ) "description of the mission on which the platform observations are made and the objectives of that mission"
  • citation: { citation } "identification of the mission"
  • identifier: { identifier } "unique identification of the operation"
  • status: ( MD_ProgressCode ) "status of the data acquisition"
  • operationType: ( MI_OperationTypeCode ) "collection technique for the operation"
  • objective: [ objectiveId ] "object(s) or area(s) of interest to be sensed"
  • parentOperation: ( operationId ) "heritage of the operation"
  • childOperation: [ operationId ] "sub-missions that make up part of a larger mission"
  • plan: ( planId ) "plan satisfied by the operation"
  • platform: [ platformId ] "platform (or platforms) used in the operation"
  • significantEvent: [ eventId ] "record of an event occurring during an operation"

Rules:

  • operationId: required
  • identifier: required
  • status: required
  • parentOperation: required

mdJson:

{
   "acquisition": [
      {
         "operation": [
            {
               "operationId": "operation ID",
               "description": "operation description",
               "citation": { },
               "identifier": { },
               "status": "MD_ProgressCode",
               "operationType": "MI_OperationTypeCode",
               "objective": ["objectiveId"],
               "parentOperation": "operationId",
               "childOperation": ["operationId"],
               "plan": "planId",
               "platform": ["platformId"],
               "significantEvent": ["eventId"]
            }
         ]
      }
   ]
}
@jwaspin
Copy link
Contributor

jwaspin commented Apr 9, 2024

@dwalt or @hmaier-fws Is platform supposed to be the platform class or is it just a string for the id?
Similar question for significantEvent but I'm not sure what the corresponding class would be.

@dwalt
Copy link
Collaborator

dwalt commented Apr 10, 2024

@jwaspin Platform is a class. Operation is the parent class referencing one or more Platforms associated with an Operation.

@hmaier-fws
Copy link
Contributor

Changed definition of operationId to:
operationId: ( character ) "a unique mdJSON system identifier for the operation" default: UUID

@jwaspin
Copy link
Contributor

jwaspin commented May 6, 2024

@dwalt @hmaier-fws This says that parentOperation is required. Is that accurate? Isn't there a point at which there is a root/top-level operation that doesn't have a parent?

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

Successfully merging a pull request may close this issue.

4 participants