ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
PriorityTransferred to ES-DOC?TypeIssueSourceWork Will AffectDurationWhich TrackerWhich NumberComment
2
1na, simulation name search existed in esg onlyFeatureChange the code that connects the model metadata to the data to use the experiment name and not the simulation name because the latter is not a controlled vocabulary in the questionnaire. This should improve the robustness of the model metadata to data connection and has the potential for reducing long-term maintenance of this piece of code. Charlotte PascoeCMIP5~weekJira2494
3
1na, es-doc portal will not have access to dataFeatureBe able to search on netCDF forcing attributes to find model simulations subject to a particular kind of forcing. Discussion have already begun on this issue and it has been determined that the forcing attributes that Gavin is interested in are in fact mandatory for CMIP5.Gavin SchmidtCMIP5~monthJira2477May have dependency on new search. Certs coordinated and all gateways on 1.3.2.
4
1na, the es-doc portal will not have access to the dataFeatureForcings and RIP. There are different sets of forcings that are
applied in a set of experiments under the historicalMisc category,
for example. These are distinguished by the "p" value in the RIP,
but otherwise not distinguished in the ESG. You can of course read
the netCDF headers to get details on which p-value corresponds to which
set of forcings, but not otherwise. Curator could add this metadata so
that users could get at the forcings without downloading/reading actual
files.		BaljiCMIP5Need to find out what the user wants from this, a model simulation document or data files?
5
yesFeatureHarvest and display the following individual attributes for automated generation from CESM: SimulationNumberOfProcessingElements, PlatformDescription, MachineDescription. These will all show up under the technical properties tab in the display.CESMCESM~dayJira2711
6
2yesFeatureHarvest and display component attributes that describe fields in either the questionnaire or CESM output. These attributes contain information such as a shortname, longname, units, standard name and whether the fields are imported, exported, or internal to the component.
CESM/CMIP5CESM/CMIP5~weekJira2710
7
2already a ticket in es-docFeatureHarvest and display ensemble information: Some simulations are ensemble runs of a base simulation. These will have a unique section in the questionnaire output. We currently only have a mock-up of what this might look like. The ensemble section seems to have its own name, longname, description, contact information, type (e.g. changed the initial conditions), RIP value, and a list of all other ensemble members.
Metafor TelcoCMIP5~week or ~monthJira2712
8
NA, this ticket refers to RDF and the need to pre-define attributes for the harvester. It is not applicable to the plugin.FeatureHarvest and display dynamic type attributes whether from the questionnaire output (how a model was modified for a particular simulation) or from CESM output (custom attributes).CESM/CMIP5CESM/CMIP5~week or ~monthJira2705
9
NA, this ticket refers to the gateway software only.FeatureRefactor Inputs: This affects the Inputs Tab in the display. Harvest and display 3 new properties (InputBindingDescription, InputRequirementDescription, and InputComponentProperty); remove the current input description that is displayed at the root of every input tree and redirect it instead to the new InputBindingDescription located in the tree; alphabetize the Inputs, and harvest and display inputs that are files and not components.Charlotte PascoeCMIP5~weekJira2708
10
already a ticket in es-doc for harvesting simulation attributesFeatureHarvest and display the new attribute SimulationDescription present in the questionnaire output. This will be displayed with other simulation properties under the Basic Properties Tab.Charlotte PascoeCMIP5~dayJira2447
11
already a ticket in es-doc for harvesting component level informationFeatureHarvest and display comment fields for component properties: In the questionnaire, users are allowed to make comments on component properties in addition to selecting or specifying the value of the component property. These are put into the output as a separate field that will need to get assigned to their own unique attribute. In order to harvest these properties, we will need to coordinate with Metafor for a new file specifying these new properties.Charlotte PascoeCMIP5~weekJira2407
12
yesFeatureBe able to annotate metadata: This would be to comment on an particular attribute and have that comment be federated.Gavin Schmidt, others might want updates to QC info, etc.All users~monthJira2684If annotations are to be visible to anyone, then we should approach this with caution. -vb/rs
13
yesFeatureConformance information collected by the questionnaire is insufficient: In the conformance section of the questionnaire allow and encourage users to describe what was done in their simulation beyond just how it conformed to the experimental requirements.Gavin SchmidtCMIP5Metafor996
14
already a ticket in es-doc for simulation comparisonFeatureBe able to difference two model simulations and display only things that are different. Gavin SchmidtAll users~monthJira2479
15
na refers to gateway software onlyFeatureChange the color of the current component in the component navigation tree from black to something more noticeable.
Dean WilliamsAll users~dayJira2395
16
na refers to gateway software onlyFeatureAdd an attribution to the Earth System Curator project and its sponsors in the model metadata display section of the ESG-CET gateway.Cecelia DeLucaAll users~dayJira2380
17
na refers to gateway software onlyFeatureCreate a horizontal breadcrumb trail across the top of the display that indicates where one is in the component hierarchy.Karl TaylorAll users~monthJira2396
18
3yesFeatureCreate a dynamic attribute comparison table such that a user can select a given number of simulations and given number of attributes and see the values across those selections. Table that enables someone to search on RIP, select simulations, and display forcings for each.Gavin and others in various demonstrations. Karl for forcings.
All users~monthJira1461
19
2na the es-doc portal will not have access to the dataFeatureForcings and RIP. There are different sets of forcings that are applied in a set of experiments under the historicalMisc category, but otherwise not distinguished in the metadata. You can of course read the NetCDF headers to get details on which p-value corresponds to which set of forcings, but not otherwise. Curator could harvest this data metadata so that users could get at the forcings without downloading/reading actual files. Design is needed here about what users want to see.This can be merged with #16 from Gavin... -vb
20
na the es-doc portal will not have access to the dataWhat happens if all the metadata is not filled in? You can still see the data, but you won't see the metadata. The restriction that metadata must be completed was relaxed. Make sure failure is graceful, maybe.Ron Stouffer comment.METAFOR issue
21
created ticket for a) validation, b) QCMETAFOR issueIs the only validation in the questionnaire itself? Ron gets different validation responses from the questionnaire at different times and does not trust it. Has difficulty getting conformance issues into the questionnaire. Actions: That it is clear how to get info into the questionnaire, someone is looking at the outputs, and the validation is run in batch mode.
Ron StoufferMETAFOR issue
22
na refers to gateway data search onlyFeatureThe first page on search is confusing for a scientist. Looking for variable from a specific set of experiments. Select datasets, then select variable, then would see all variables. Create an example, getting started, or help box.Ron Stouffer
23
yesFeatureReplace Simulation with Documentation on Search. Vet on this first.Karl Taylor
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63