Services in IOOS Registry cannot always be found in the Catalog or NGDC Geoportal

[robragsdale]

Services submitted and approved, in some cases, do not come up in the NGDC Geoportal or the IOOS catalog (catalog.ioos.us). A NANOOS THREDDS catalog (http://ona.coas.oregonstate.edu:8080/thredds/catalog.xml) in the registry (https://www.ngdc.noaa.gov/docucomp/collectionSource/list?recordSetId=2604647&componentId=&serviceType=&serviceStatus=&serviceUrl=&search=List+Collection+Sources) was not found in the IOOS catalog or NGDC Geoportal (http://www.ngdc.noaa.gov/geoportal/catalog/main/home.page). (example from Emilio Mayorga email (15 Feb 2014).

[amilan17]

The http://ona.coas.oregonstate.edu:8080/thredds/catalog.xml successfully harvests to the test WAF, but not to the production WAF - I suspect that this is an issue with some pipeline configuration under the hood.

[emiliom]

Thanks, Anna (and Rob). One quick question: is the ncISO plugin necessary for successful harvesting into the NGDC GeoPortal? I don't think ncISO is installed on that THREDDS server, though we plan to do so in the next ~ 3 weeks (the Ocean Sciences Meeting will get in the way!); there's even a small-to-tiny chance it'll be installed by Monday.

Either way, can you point me to documentation that describes what happens on your end when ncISO is vs is not installed?

[amilan17]

No. We use our own instance of ncISO for harvesting into Geoportal.

Anna ~~~~~~~~~~~~ Anna.Milan@noaa.gov, 303-497-5099 NOAA/NESDIS/NGDC

One cannot have too much metadata. Start simple and grow from there. ~~~~~~~~~~~~

On Thu, Feb 20, 2014 at 1:36 PM, Emilio Mayorga notifications@github.comwrote:

Thanks, Anna (and Rob). One quick question: is the ncISO plugin necessary for successful harvesting into the NGDC GeoPortal? I don't think ncISO is installed on that THREDDS server, though we plan to do so in the next ~ 3 weeks (the Ocean Sciences Meeting will get in the way!); there's even a small-to-tiny chance it'll be installed by Monday.

Either way, can you point me to documentation that describes what happens on your end when ncISO is vs is not installed?

Reply to this email directly or view it on GitHubhttps://github.com/ioos/system-test/issues/25#issuecomment-35665984 .

[amilan17]

This is a high level work flow diagram of the process...

[emiliom]

Anna, thanks for both comments (about ncISO on your end, and the flow diagram). Very useful.

[amilan17]

This is a more detailed resource that explains how to run ncISO standalone.

http://ngdc.noaa.gov/eds/tds/

Anna ~~~~~~~~~~~~ Anna.Milan@noaa.gov, 303-497-5099 NOAA/NESDIS/NGDC

One cannot have too much metadata. Start simple and grow from there. ~~~~~~~~~~~~

On Thu, Feb 20, 2014 at 11:54 PM, Emilio Mayorga notifications@github.comwrote:

Anna, thanks for both comments (about ncISO on your end, and the flow diagram). Very useful.

Reply to this email directly or view it on GitHubhttps://github.com/ioos/system-test/issues/25#issuecomment-35703668 .

[emiliom]

@amilan17, regarding your comment from 2-20:
The http://ona.coas.oregonstate.edu:8080/thredds/catalog.xml successfully harvests to the test WAF, but not to the production WAF - I suspect that this is an issue with some pipeline configuration under the hood.

Have you been able to learn more about where the problem is (why it's not harvesting to the production WAF)? I couldn't tell if you were saying the "under the hood" problem lies on your (NGDC) end, or the NANOOS/THREDDS end. Thanks!

[dpsnowden]

@robragsdale or @amilan17, is this issue complete? If so please summarize the resolution and close. Hopefully the new documentation on the @ioos/registry page will clarify the problem/solution.