Need to display OpenDAP link types

[tchaddad]

Most commonly this would be from ISO records. Solution is similar to https://github.com/Ecotrust/wc-data-registry/issues/112

Half the solution is in the GeoPortal configuration files, and the other half is in the custom Registry UI.

[tchaddad]

Here's a the GeoPortal side of the OpenDAP solution from @eggwhites (05/13/2014):

Steps:

• Create an index in the geoportal’s lucene for the OPeNDAP URL. Instructions for creating an index are found here: https://github.com/Esri/geoportal-server/wiki/Details-of-Lucene-Indexing-in-the-Geoportal ; you’ll update the apiso-indexables.xml (for ISO 19115), the apiso-2-indexables.xml (for ISO 19115-2), and property-meanings.xml a. Note – you can use something like this below to make sure only URL’s that contain “.ncml” are indexed here:

<property meaning="opendap.url" xpath="/gmi:MI_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:containsOperations/srv:SV_OperationMetadata/srv:connectPoint/gmd:CI_OnlineResource/gmd:linkage/gmd:URL[contains(.,'.ncml')]"/>

• Let’s say you’re new index is called ‘opendap.url’ in these files in Step 1 (as shown in example above). Now you will use instructions at https://github.com/Esri/geoportal-server/wiki/Add-Custom-Link-to-a-Search-Result to create a new link in the geoportal user-interface that references the URL in the index.
• Save all updated files, and restart the geoportal service in Tomcat (or restart Tomcat altogether).
• You must reindex the metadata to apply your new opendap.url index. To reindex, just ‘Set as Approved’ a few test records in the geoportal Administration page.
• For these records that have a .ncml url at the xpath you indexed, you should see now an OPeNDAP link on the search result when you find them on the geoportal search page.

[smrgeoinfo]

OpenDAP url's may also show up in //gmd:distributionInformation//gmd:MD_DigitalTransferOptions/gmd:online/gmd:CI_OnlineResource. It would be a good idea to point the index at that xpath as well

[emiliom]

Based on discussions in #117 and my browsing of some targeted ISO metadata on the WCODP, I'm assuming OPeNDAP link types are still not available (or exposed) on the WCODP. @tchaddad (or @fishytodd ), can you confirm this is the case? I want to be 100% sure of where we stand, given that Laura is wrapping up her work and her metadata records, and that according to Todd there will be a nice push around the time of the WCODN meeting to release a number of IOOS-related records. Thanks!

[tchaddad]

Yes the discussion in #117 covered many topics and the bottom line for this one is that there is no problem configuring detection of OPeNDAP in Geoportal (or any other link type). However we ran into a problem displaying the links in the custom UI, due to the fact that Geoportal is not including the custom link labels in its JSON responses. Doing so will apparently require the relevant Geoportal java class source to be recompiled.

My comments on #117 around August 19th cover the gory details, but I just wanted to emphasize here that the problem is not OPeNDAP-specific.

For Laura's purposes, she should certainly plan to include the various links that she wants to include in her records. Her URLs will be detected as the correct relevant type on the backend, because those configuration edits have already been made. On the front end UI, at the very least, they will get labeled with an 'OPEN' link currently, and the custom labels like 'OPeNDAP' will appear once we tackle the high-priority JSON feed fix.

[emiliom]

Thanks for the update and recap, Tanya. Sorry if I wasn't clearer that I do know the issue (or bottleneck) is no longer specific to OPeNDAP. I was coming at this from an OPeNDAP interest, to I guess ask the more general question that you have answered.