{"action":"created","issue":{"url":"https://api.github.com/repos/ioos/catalog/issues/422","labels_url":"https://api.github.com/repos/ioos/catalog/issues/422/labels{/name}","comments_url":"https://api.github.com/repos/ioos/catalog/issues/422/comments","events_url":"https://api.github.com/repos/ioos/catalog/issues/422/events","html_url":"https://github.com/ioos/catalog/issues/422","id":78077706,"number":422,"title":"Document and understand data flow leading to duplicate RA/NDBC stations","user":{"login":"dpsnowden","id":3603125,"avatar_url":"https://avatars.githubusercontent.com/u/3603125?v=3","gravatar_id":"","url":"https://api.github.com/users/dpsnowden","html_url":"https://github.com/dpsnowden","followers_url":"https://api.github.com/users/dpsnowden/followers","following_url":"https://api.github.com/users/dpsnowden/following{/other_user}","gists_url":"https://api.github.com/users/dpsnowden/gists{/gist_id}","starred_url":"https://api.github.com/users/dpsnowden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dpsnowden/subscriptions","organizations_url":"https://api.github.com/users/dpsnowden/orgs","repos_url":"https://api.github.com/users/dpsnowden/repos","events_url":"https://api.github.com/users/dpsnowden/events{/privacy}","received_events_url":"https://api.github.com/users/dpsnowden/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ioos/catalog/labels/data-provider","name":"data-provider","color":"006b75"},{"url":"https://api.github.com/repos/ioos/catalog/labels/monitor","name":"monitor","color":"5319e7"},{"url":"https://api.github.com/repos/ioos/catalog/labels/SOS","name":"SOS","color":"d4c5f9"}],"state":"open","locked":false,"assignee":{"login":"abirger","id":3603740,"avatar_url":"https://avatars.githubusercontent.com/u/3603740?v=3","gravatar_id":"","url":"https://api.github.com/users/abirger","html_url":"https://github.com/abirger","followers_url":"https://api.github.com/users/abirger/followers","following_url":"https://api.github.com/users/abirger/following{/other_user}","gists_url":"https://api.github.com/users/abirger/gists{/gist_id}","starred_url":"https://api.github.com/users/abirger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abirger/subscriptions","organizations_url":"https://api.github.com/users/abirger/orgs","repos_url":"https://api.github.com/users/abirger/repos","events_url":"https://api.github.com/users/abirger/events{/privacy}","received_events_url":"https://api.github.com/users/abirger/received_events","type":"User","site_admin":false},"milestone":null,"comments":5,"created_at":"2015-05-19T13:01:49Z","updated_at":"2015-05-26T19:34:59Z","closed_at":null,"body":"On the [NDBC data set page](http://catalog.ioos.us/datasets/filter/NOAA-NDBC/) you can see duplicate stations from CeNCOOS and AOOS.  For example the station with [WMO ID 46251](http://catalog.ioos.us/datasets/5346986c8c0db36efb591231) shows up as being served by both CeNCOOS and NDBC.  I believe **this is the correct behavior**.  The question is, why don't the other RA's show up this way?  \r\n\r\nSince it is only AOOS and CeNCOOS that exhibit this behavior, I'm guessing it is related to i52N configuration.  What differs between i52N ID handling and ncSOS ID handling?   But, since NANOOS and GCOOS aren't showing up this way, it must be more than just the software.  It probably has more to do with the way @shane-axiom is handling [URN station identifiers](http://ioos.github.io/conventions-for-observing-asset-identifiers/) as part of the ingestion process that is not being done at the other sites.  \r\n\r\nWe need to understand the data flow that led to this behavior and see what we can do to get it implemented everywhere.  It may require a tool at the catalog that provides a summary of asset identifier usage for each collection (aka region).  @emiliom I think you were looking into WMO ID issues, any insight?  @lukecampbell thoughts?\r\n\r\n@abirger or @carmelortiz can you track this or assign it to the appropriate person?"},"comment":{"url":"https://api.github.com/repos/ioos/catalog/issues/comments/105643198","html_url":"https://github.com/ioos/catalog/issues/422#issuecomment-105643198","issue_url":"https://api.github.com/repos/ioos/catalog/issues/422","id":105643198,"user":{"login":"abirger","id":3603740,"avatar_url":"https://avatars.githubusercontent.com/u/3603740?v=3","gravatar_id":"","url":"https://api.github.com/users/abirger","html_url":"https://github.com/abirger","followers_url":"https://api.github.com/users/abirger/followers","following_url":"https://api.github.com/users/abirger/following{/other_user}","gists_url":"https://api.github.com/users/abirger/gists{/gist_id}","starred_url":"https://api.github.com/users/abirger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abirger/subscriptions","organizations_url":"https://api.github.com/users/abirger/orgs","repos_url":"https://api.github.com/users/abirger/repos","events_url":"https://api.github.com/users/abirger/events{/privacy}","received_events_url":"https://api.github.com/users/abirger/received_events","type":"User","site_admin":false},"created_at":"2015-05-26T19:34:58Z","updated_at":"2015-05-26T19:34:58Z","body":"@lukecampbell , Yep, the ghost issue seems to be gone; however, the Catalog definitely does a selective matching of the WMO IDs as @emiliom has mentioned - it only matches datasets for the WMO ID that is a part of the station's URN, but drops the ball if WMO ID is defined in a separate identifier. It looks like a bug, since the Catalog seems to get the right WMO ID in both cases.\r\n\r\nIn regard to the wrong Operator attribution, it seems that the Catalog does not parse this attribute from NDBC at all (while it properly shows there `Oregon Coastal Ocean Observing System`) but takes it from the CeNCOOS ContactList instead (where it is attributed to NDBC)."}}