[pycsw-devel] Links Question

[dan at inlet.geol.sc.edu]

Ok, I now get what you guys are saying.
What is the tag in that snippet that pycsw uses to add the service entry?
Part of the section is valid, but missing the protocol.

Thanks for the info, I want to get full use from the catalog.

Dan


> Exactly, Dan. ncISO is not generating a gmd:protocol entry for that
> viewer.
> It is not included in the ncISO XSLT. Feel free to add one to your copy of
> the XSLT (UnidataDD2MI.xsl). But again, there's no valid gmd:protocol
> entry
> for such a viewer, really, so it would seem a moot point to me.
> Cheers,
> John
>
> On Mon, Sep 22, 2014 at 9:21 AM, Dan Ramage <dan at inlet.geol.sc.edu> wrote:
>
>> I think I am confused, the URL that is used for this None entry is only
>> found in the section I posted below. I didn't see any <gmd:protocol>
>> entries that had that URL.
>> The ISO record in question is here:
>> http://neptune.baruch.sc.edu/xenia/waf/ncsu_meas/thredds_dodsC_fmrc_sabgom_
>> SABGOM_Forecast_Model_Run_Collection_best.ncd_META.xml
>>
>> On 9/22/14 3:15 PM, "Tom Kralidis" <tomkralidis at gmail.com> wrote:
>>
>> >
>> >gmd:protocol is the actual element which triggers clients into binding
>> >against
>> >a given resource, which is usually based on a codelist item for
>> >consistency.
>> >
>> >gmd:name serves as more of a text label of a given link as opposed to
>> >something a machine can action against.
>> >
>> >Using gmd:protocol will yield huge value in many downstream tools like
>> >pycsw.  And given tools are looking for gmd:protocol, this prevents
>> >them from guessing what the link is.
>> >
>> >..Tom
>> >
>> >On Mon, 22 Sep 2014, Dan Ramage wrote:
>> >
>> >> Date: Mon, 22 Sep 2014 15:12:26 -0400
>> >> From: Dan Ramage <dan at inlet.geol.sc.edu>
>> >> To: Tom Kralidis <tomkralidis at gmail.com>
>> >> Cc: "pycsw-devel at lists.osgeo.org" <pycsw-devel at lists.osgeo.org>
>> >> Subject: Re: [pycsw-devel] Links Question
>> >>
>> >> What's the reasoning for not using the Viewer Information string?
>> >>
>> >> Dan
>> >>
>> >> On 9/22/14 3:06 PM, "Tom Kralidis" <tomkralidis at gmail.com> wrote:
>> >>
>> >>>
>> >>> This should be fixed in the upsteam ncISO tools at this point:
>> >>>
>> >>> https://github.com/ethanrd/threddsIso/issues/2
>> >>>
>> >>> https://github.com/Unidata/threddsIso/pull/1
>> >>>
>> >>> This should alleviate this issue for ncISO based outputs.
>> >>>
>> >>> ..Tom
>> >>>
>> >>> On Mon, 22 Sep 2014, Dan Ramage wrote:
>> >>>
>> >>>> Date: Mon, 22 Sep 2014 14:56:48 -0400
>> >>>> From: Dan Ramage <dan at inlet.geol.sc.edu>
>> >>>> To: "pycsw-devel at lists.osgeo.org" <pycsw-devel at lists.osgeo.org>
>> >>>> Subject: [pycsw-devel] Links Question
>> >>>>
>> >>>> I've gotten most of my services issues sorted out via ncISO and
>> using
>> >>>> an xsl
>> >>>> file that handles the transforms correctly from Thredds endpoints.
>> >>>> However I still have an entry of "None" with a link that only
>> appears
>> >>>> in the
>> >>>> following metadata section:
>> >>>>               <gmd:distributorTransferOptions>
>> >>>>                  <gmd:MD_DigitalTransferOptions>
>> >>>>                     <gmd:onLine>
>> >>>>                        <gmd:CI_OnlineResource>
>> >>>>                           <gmd:linkage>
>> >>>>
>> >>>>
>> >>>>
>> >>>><gmd:URL>
>> http://www.ncdc.noaa.gov/oa/wct/wct-jnlp-beta.php?singlefile=h
>> >>>>tt
>> >>>> p:/
>> >>>>
>> >>>>
>> >>>>/
>> omgsrv1.meas.ncsu.edu:8080/thredds/dodsC/fmrc/sabgom/SABGOM_Forecast_M
>> >>>>od
>> >>>> el_
>> >>>> Run_Collection_best.ncd</gmd:URL>
>> >>>>                           </gmd:linkage>
>> >>>>                           <gmd:name>
>> >>>>                              <gco:CharacterString>Viewer
>> >>>> Information</gco:CharacterString>
>> >>>>                           </gmd:name>
>> >>>>                           <gmd:description>
>> >>>>                              <gco:CharacterString>This URL provides
>> an
>> >>>> NCDC
>> >>>> climate and weather toolkit view of an OPeNDAP
>> >>>> resource.</gco:CharacterString>
>> >>>>                           </gmd:description>
>> >>>>                           <gmd:function>
>> >>>>                              <gmd:CI_OnLineFunctionCode
>> >>>>
>> >>>>
>> >>>>codeList="
>> http://www.ngdc.noaa.gov/metadata/published/xsd/schema/resour
>> >>>>ce
>> >>>> s/C
>> >>>> odelist/gmxCodelists.xml#CI_PresentationFormCode"
>> >>>>
>> >>>> codeListValue="mapDigital">mapDigital</gmd:CI_OnLineFunctionCode>
>> >>>>                           </gmd:function>
>> >>>>                        </gmd:CI_OnlineResource>
>> >>>>                     </gmd:onLine>
>> >>>>                  </gmd:MD_DigitalTransferOptions>
>> >>>>               </gmd:distributorTransferOptions>
>> >>>>
>> >>>> Should this be picked up at all? There is a similar section above
>> it
>> >>>>as
>> >>>> well
>> >>>> that is a gmd:name http. I am not sure if this one is getting
>> handled
>> >>>> since
>> >>>> I do have an http entry in the links or if that was from a
>> >>>>gmd:protocol
>> >>>> section.
>> >>>>
>> >>>>
>> >>>> Dan
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>
>> >>
>> >>
>>
>>
>> _______________________________________________
>> pycsw-devel mailing list
>> pycsw-devel at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pycsw-devel
>>
>