Ticket #988 (new Task)

Opened 4 years ago

Last modified 3 years ago

how to handle the extra information in component descriptions

Reported by: charlotte Owned by: rupert
Priority: critical Milestone: V1.2 Questionnaire release
Component: WP6 - CMIP5 Questionnaire Version:
Keywords: Cc: sylvia
Requirement:

Description (last modified by sylvia) (diff)

SJM: Some component properties have an extra description tag. We need to determine a way to handle this. Here is hypothetical example: <componentProperty represented="true"> <shortName>NumberOfSurfaceTemperatures?</shortName> <longName>NumberOfSurfaceTemperatures?</longName> <value>9</value> <description>Some extra text the user has put in</description> </componentProperty>

We harvest the attribute NumberOfSurfaceTemperatures? and reference the property hasNumberOfSurfaceTemperatures that was provided in Rupert's metafor.owl file such that

model_component hasNumberOfSurfaceTemperatures 9

I think we are going to need a hasNumberOfSurfaceTemperaturesDescription property created by rupert in the metafor.owl file such that we can say:

model_component hasNumberOfSurfaceTemperaturesDescription Some extra text the user has put in

this will display in ESG then as:

Number of Surface Temperatures Description = Some extra text the user has put in

If every scientific property in the questionnaire can have this description, then we will need to make a new property with description or some other text e.g. Note for every scientific property in the metafor.owl.

Type does not appear in the output from the questionnaire - if a user renames a component the ESG display is not able to say what kind of component it is.  This is further compounded by the fact that the objects in the ESG display do not know the name of their parent they only know the name of the children.  Easy to get disorientated.Need a list of all the pieces of information that are lost in the post processing of the questionnarie.for instance "type" and "additional information" are not in the xml that gets ingested into esg.

Change History

comment:1 Changed 4 years ago by charlotte

  • Cc sylvia added
  • Status changed from new to closed
  • Resolution set to fixed

We (rupert and I) checked out the export xml for the HadGEM2-ES in the example centre of the questionnaire. Type is in the xml output - but is listed at the end of the component.

Additional information is also in the output but is called "description"

Questionnaire to CIM mappings can be found on the wiki page attached to ticket #249

comment:2 Changed 3 years ago by charlotte

ESG needs each "description" to have a unique name.

comment:3 Changed 3 years ago by sylvia

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:4 Changed 3 years ago by sylvia

  • Status changed from reopened to new
  • Description modified (diff)
  • Summary changed from what information is "lost" in the questionnaire translation to CIM xml to how to handle the extra information in component descriptions

I am reopening this ticket because we need to decide how to handle this issue. I am changing the title too to focus on the one issue, how to handle the extra description info.

Note: See TracTickets for help on using tickets.