search

ioos / registry

Getting data services registered in the IOOS Service Registry
http://ioos.github.io/registry/
2 stars 7 forks source link

end-time metadata for ongoing operational datasets #32

Open jcothran opened 10 years ago

jcothran commented 10 years ago

For the ISO WAF metadata entries I'm currently providing, I've been adding a script to daily regenerate the WAF files using ncISO, but the only reason for this is so that the 'end-time' type metadata reflects the ongoing nature of ongoing forecast models and in-situ data.

Is there a shorthand valid way(works with @rsignell-usgs catalog search with time extents) of denoting a dataset as ongoing by say leaving the endtime element empty? Would be nice to cut out this daily processing chore with a better one-time metadata listing.

amilan17 commented 10 years ago

Jeremy,

The way to represent this in ISO is like this:

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

http://www.ngdc.noaa.gov/metadata/emma ~~~~~~~

On Wed, Jun 25, 2014 at 2:13 PM, Jeremy Cothran notifications@github.com wrote:

For the ISO WAF metadata entries I'm currently providing, I've been adding a script to daily regenerate the WAF files using ncISO, but the only reason for this is so that the 'end-time' type metadata reflects the ongoing nature of ongoing forecast models and in-situ data.

Is there a shorthand valid way(works with @rsignell-usgs https://github.com/rsignell-usgs catalog search with time extents) of denoting a dataset as ongoing by say leaving the endtime element empty? Would be nice to cut out this daily processing chore with a better one-time metadata listing.

— Reply to this email directly or view it on GitHub https://github.com/ioos/registry/issues/32.

rsignell-usgs commented 10 years ago

@amilan17 , didn't we have some issue with indeterminatePosition="now", like CO-OPS SOS is using it, but when we try to use a time-constrained search using CSW, we don't find the dataset? I think this was unfortunately a phone conversation we had. Does this ring a bell?

amilan17 commented 10 years ago

yeah..... kind of remember...

On Jun 26, 2014, at 5:19 AM, Rich Signell notifications@github.com wrote:

@amilan17 , didn't we have some issue with indeterminatePosition="now", like CO-OPS SOS is using it, but when we try to use a time-constrained search using CSW, we don't find the dataset? I think this was unfortunately a phone conversation we had. Does this ring a bell?

— Reply to this email directly or view it on GitHub.

jcothran commented 10 years ago

@amilan17 thanks for the example

@rsignell-usgs if this is the standard, will it be ok if I provide SECOORA metadata for ongoing datasets using this convention for your catalog search testbed purposes?

dpsnowden commented 10 years ago

My $0.02....

@jcothran are you contemplating altering your metadata generation script to change the ISO documents that are automatically generated by ncISO to include the indeterminate position instead of an explicit date string? If you're going to get in to the hand (or script) editing of ISO doucments then I agree with you that we should use the standard as it's intended.

If this introduces another issue in that Geoportal does not know how to index and query this ISO standard element correctly, then we'll have to think of another way to fix that part. So...what next?

@amilan17 couldn't tell from your last comment what you intend to do next? Anything? Do you have an idea of how to test @rsignell-usgs issue/bug?

@rsignell-usgs Let's assume Geoportal has a bug or needs this enhancement/new feature. Where do we turn to get that addressed? The OSGeo working group or direct to ESRI?

amilan17 commented 10 years ago

This record in Geoportal has an end time of 'now'.

http://ngdc.noaa.gov/geoportal/rest/document?id={7415FDE4-58B5-4DB7-A1AB-5973EE94D66B}

Perhaps we can use this for testing (again?)

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

http://www.ngdc.noaa.gov/metadata/emma ~~~~~~~

On Fri, Jun 27, 2014 at 11:00 AM, Derrick Snowden notifications@github.com wrote:

My $0.02....

@jcothran https://github.com/jcothran are you contemplating altering your metadata generation script to change the ISO documents that are automatically generated by ncISO to include the indeterminate position instead of an explicit date string? If you're going to get in to the hand (or script) editing of ISO doucments then I agree with you that we should use the standard as it's intended.

If this introduces another issue in that Geoportal does not know how to index and query this ISO standard element correctly, then we'll have to think of another way to fix that part. So...what next?

@amilan17 https://github.com/amilan17 couldn't tell from your last comment what you intend to do next? Anything? Do you have an idea of how to test @rsignell-usgs https://github.com/rsignell-usgs issue/bug?

@rsignell-usgs https://github.com/rsignell-usgs Let's assume Geoportal has a bug or needs this enhancement/new feature. Where do we turn to get that addressed? The OSGeo working group or direct to ESRI?

— Reply to this email directly or view it on GitHub https://github.com/ioos/registry/issues/32#issuecomment-47374348.