Expose webservices (like WaterOneFlow) as links in dataset results

[SRGDamia1]

Just as links to "display files" and "metadata xml" files are separately listed on right of each search result.

Also make those webservices a "collection" in the resources.

[SRGDamia1]

Right now the standard metadata does not include links to the webservices. Both we might be able to just assume that if it's a parsed display file then it is available as a web service via the individual CZO's Hydroserver.

[--- Commented from Asana.com
#commenter Sara Damiano
---[aa]

[SRGDamia1]

As the display file is parsed, add a link to the web service link to the metadata.

[--- Commented from Asana.com
#commenter Sara Damiano
---[aa]

[SRGDamia1]

If the web service links were readily found at search.criticalzone.org then they would be a great example for the BiG-CZ tools/iPython notebooks.

[--- Commented from Asana.com
#commenter Sara Damiano
---[aa]

[SRGDamia1]

These services would be exposed as "link types" for each metadata record. Web services should be recorded at a granular level, such as CUAHSI WaterOneFlow and OGC WMS, not as a lumped "Data Web Service". An outcome of this is that any given metadata record on search.criticalzone.org may have several link types, including: "Display Files", "CZO Dataset" "WaterOneFlow", "WMS", and so on.

[--- Commented from Asana.com
#commenter Emilio Mayorga
---[aa]