[Go-essp-tech] CIM Quality Examples

[Hans Ramthun]

Hallo Sylvia,

I'll answer at least the first topic:

Am 07.07.2011 17:16, schrieb Sylvia Murphy:
> Hi Martina,
> Thanks for this.  I of course have a bunch of follow up questions for you :)
>
> 1) You mention the internal id.  I see this number in the atom feed title, but not in the XML itself.  Note that I am only slightly familiar with ESG's data side of the house...so, does this ID correspond to a row in the database that points to a particular data collection?  I am just trying to figure you how we connect that id to the actual data link.
'internal_id' is only the id inside the providing GeoNetwork framework 
(or better the id of the background database for this record). It's not 
more then a hint to find this record e.g. also useful with another GN 
service: http://anticyclone.dkrz.de:8088/geonetwork/srv/en/cim.xml?id=1897
It's only to distinguish the exact record. In the output list it could 
be possible that there are a long list of very similar records. Then the 
(additional) internal_id is helpful to find the appropriate record.

Hoping that answers your question.

Cheers
Hans



>
> 2) I am trying to understand what you mean by the granularity of an ESG dataset / publication unit and experiment.  Again I just do see this side of things....
> The current query from the model metadata side displays  all the datasets that have model=x and experiment=y in their TDS.  Is there one QC value for this entire set or are they on the level of the individual datasets in that set (e.g. from a data search.....   project=CMIP5 / IPCC Fifth Assessment Report, model=HadGEM2-ES, Met Office Hadley Centre, experiment=historical, time_frequency=6hr, modeling realm=atmos, ensemble=r1i1p1, version=20101208)
>
> The reason I ask is that if there is one QC value for the entire set, then displaying this information with the model metadata makes sense.  If it is at the level of the search listing above, then it may best be displayed with the data page itself since there is a one to one correspondence.
>
> 3) The primary suggestion I would make is that if there is key information that we need to extract and display or extract to connect to something else, that this should not be buried in a long string.  It should be a stand alone entity.
>
> Lets talk more about this.
>
> Sylvia
> On Jul 7, 2011, at 4:52 AM, Martina Stockhause wrote:
>
>>   Hi, Sylvia,
>>
>> we offer two preliminary CIM Quality examples to give you a first
>> impression of the quality documents to be harvested by the gateways:
>>
>> http://anticyclone.dkrz.de:8088/geonetwork/srv/en/atom.latestCIM
>> internal_ids=1896,1897
>>
>> A few explanations where to find the core information:
>>
>> - Quality information will be provided on ESG dataset / publication unit
>> level and experiment level. The example with internal_id=1897 is a
>> dataset and the internal_id=1896 is the related experiment.
>>
>> - pass/fail information: "pass" with pass=0 (failed) pass=1 (passed).
>> The examples haven't completed QC L2 and therefore are pass=0.
>> Interesting are more the pass=1 documents. Therefore I suggest to
>> publish them by AtomFeed only for QC status changes and therefore a pass=1.
>>
>> - QC Level: "nameOfMeasure" or "measureIdentification/code" (string
>> includes "2" or "3"). These are examples for QC L2.
>>
>> - DRS_ID: I did not find an exclusive tag for that, therefore it is part
>> of "evaluationMethodDescription", e.g.
>> dataset_id=cmip5.output1.IPSL.IPSL-CM5A-LR.amip4K.3hr.atmos.3hr.r1i1p1.v20110429
>> or part of the "title". I would not suggest to use the "title". We keep
>> the version because for QC L3 it is important to assign only a specific
>> version of a dataset the QC level 3.
>>
>>
>> Status and expected changes:
>> - Hans and I were handed over Bryan's QC tool for CIM quality document
>> creation. We still need a bit of development and discussion about the
>> application with Bryan, before we can use it. Therefore the CIM document
>> might change (CIM schema v1.5 should be stable, but semantics might change).
>> - The field for the DRS_ID might change. "measureIdentification/code"
>> and "pass" will remain. We can give you distinct
>> "measureIdentification/code" values for QC L2 and QC L3 when we are ready.
>> - Address of AtomFeed might change.
>> - Schema location for validation will be added, document_id etc. with
>> the use of Bryan's QC tool.
>>
>> If you need more information or have suggestions for changes, please let
>> us know.
>>
>> Best wishes,
>> Martina and Hans
>>
>> _______________________________________________
>> GO-ESSP-TECH mailing list
>> GO-ESSP-TECH at ucar.edu
>> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
> ***********************************
> Sylvia Murphy
> NESII/CIRES/NOAA Earth System Research Laboratory
> 325 Broadway, Boulder CO 80305
> Email: sylvia.murphy at noaa.gov
> Phone: 303-497-7753
> Fax: 303-497-7649
>
>
>
>
>
>
>
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech


-- 
Hans Ramthun
Tel.: +49 (0)40 460 094 - 112
Deutsches Klimarechenzentrum - DKRZ
Abteilung Datenmanagement     http://www.dkrz.de/
Bundesstr. 45a
D-20146 Hamburg              Germany

„Only he who knows his destination finds the way.“ (Laozi)