[Go-essp-tech] ESG Federation Gateways - Institute and Model Names

[Estanislao Gonzalez]

Hi Eric,

As a workaround it will do :-)
My only concern was that you might be expecting to harvest this 
information (institute-model) from the CIM later on. This would have 
implied that the harvesting gateways uses one repository for this 
vocabulary (CIM) and the publishing gateway another (TDS). Although both 
should be the same, this could cause problems.

And indeed the SQL command will not work because of the constraints and 
have therefore to be manually rearranged (it would be nice if you could 
change them so they would work out-of-the-box)

Thanks,
Estani

Am 15.03.2011 19:48, schrieb Eric Nienhouse:
> Thank you Estani,
>
> Comments below.
>
> -Eric
>
> Estanislao Gonzalez wrote:
>> Hi Eric,
>>
>> "Included in the FAQ are instructions to correct this problem." Does 
>> this imply that this is the proposed solution to this problem? I hope 
>> it's just a work around, manually updating the DB is very error prone.
> This is a work-around solution and is short term focused.  This 
> approach will support consistency across the federation in the near 
> term.  Ultimately this process will be automated and should not 
> require any manual DB updates.
>> Why is that data not being harvested at all if it's available? This 
>> somehow encourages DB admins to name the models, and we might end up 
>> with model named differently in each gateway... IMHO this shouldn't 
>> be even possible.
> The metadata exchange mechanism does not harvest model or institute 
> instances currently and assumes these entities have been pre-populated 
> in the triple store.  Manually entering these values into the database 
> resolves this issue as a work-around.
>
> The model names are defined in the published Thredds catalogs, which 
> should adhere to the CMIP5 best practices naming conventions.  Though 
> a DB administrator can arbitrarily name a model in the database, only 
> those model names that match the Thredds values (via case insensitive 
> comparison) will be shown in the Search Categories UI.
>>
>> And by the way, the SQL commands order is wrong, at least for PCMDI. 
>> Apparently it should be metadata.resource -> curator.model_component 
>> -> curator.model
> Thanks for noting this.  Are you getting errors when running the SQL 
> commands as they are found in the documentation?  We'll look into it 
> and get this corrected asap.
>>
>> Thanks,
>> Estani
>>
>> Am 15.03.2011 13:59, schrieb Eric Nienhouse:
>>> Hi All,
>>>
>>> It has been noted that DRS Institute and Model are not correctly
>>> appearing in ESG Federation gateway "Search Categories" listings.  Two
>>> issues have been identified:
>>>
>>> 1)  The DRS "Institute" field may not appear in a gateway's "Search
>>> Categories" listing.
>>> 2)  The DRS "Model" field may have a "model_" pre-pended to the name.
>>>
>>> Below is a link to an FAQ which provides background on these issues.
>>> Included in the FAQ are instructions to correct this problem.  In order
>>> to do so, you will need to create new records in the gateway database
>>> related to the missing institutes and incorrect model names.
>>>
>>>    https://wiki.ucar.edu/display/esgcet/FAQ
>>>
>>> Please let us know if you need any assistance applying these changes to
>>> your gateway.  We recommend you make a reliable backup of your gateway
>>> database prior to doing so.
>>>
>>> Best Regards,
>>>
>>> -The Gateway Development Team
>>>
>>>
>>>
>>> _______________________________________________
>>> GO-ESSP-TECH mailing list
>>> GO-ESSP-TECH at ucar.edu
>>> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
>>
>>
>
>


-- 
Estanislao Gonzalez

Max-Planck-Institut für Meteorologie (MPI-M)
Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre
Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany

Phone:   +49 (40) 46 00 94-126
E-Mail:  estanislao.gonzalez at zmaw.de