[Esip-documentation] [thredds] information on related files

[Sean Gordon]

From: Esip-documentation <esip-documentation-bounces at lists.esipfed.org> on behalf of David Neufeld via Esip-documentation <esip-documentation at lists.esipfed.org>
Reply-To: David Neufeld <david.neufeld at noaa.gov>
Date: Wednesday, September 19, 2018 at 9:46 AM
To: "Armstrong, Edward M (398G)" <Edward.M.Armstrong at jpl.nasa.gov>
Cc: "netcdf-java at unidata.ucar.edu" <netcdf-java at unidata.ucar.edu>, THREDDS community <thredds at unidata.ucar.edu>, "netcdfgroup at unidata.ucar.edu" <netcdfgroup at unidata.ucar.edu>, ESIP Documentation LIst <esip-documentation at lists.esipfed.org>, Johannes Karstensen <jkarstensen at geomar.de>
Subject: Re: [Esip-documentation] [thredds] information on related files

Hi Ed,

I agree, your suggestion probably makes more sense.

Dave


On Wed, Sep 19, 2018 at 9:32 AM, Armstrong, Edward M (398G) <Edward.M.Armstrong at jpl.nasa.gov<mailto:Edward.M.Armstrong at jpl.nasa.gov>> wrote:
Hi:
I would recommend the ACDD attribute “references”:

references

Published or web-based references that describe the data or methods used to produce it. Recommend URIs (such as a URL or DOI) for papers or other references. This attribute is defined in the CF conventions.


In CF global attributes there is also a “comment” attribute where such info could be placed in a generic sense.

I have often thought of this use case too and its an area where ACDD or CF could be improved.

The metadata_link could point to an ISO 19115 record where multiple citations could point to other datasets cleanly.


From: Esip-documentation <esip-documentation-bounces at lists.esipfed.org<mailto:esip-documentation-bounces at lists.esipfed.org>> on behalf of David Neufeld via Esip-documentation <esip-documentation at lists.esipfed.org<mailto:esip-documentation at lists.esipfed.org>>
Reply-To: David Neufeld <david.neufeld at noaa.gov<mailto:david.neufeld at noaa.gov>>
Date: Wednesday, September 19, 2018 at 8:18 AM
To: Nan Galbraith <ngalbraith at whoi.edu<mailto:ngalbraith at whoi.edu>>
Cc: "netcdf-java at unidata.ucar.edu<mailto:netcdf-java at unidata.ucar.edu>" <netcdf-java at unidata.ucar.edu<mailto:netcdf-java at unidata.ucar.edu>>, Johannes Karstensen <jkarstensen at geomar.de<mailto:jkarstensen at geomar.de>>, THREDDS community <thredds at unidata.ucar.edu<mailto:thredds at unidata.ucar.edu>>, "netcdfgroup at unidata.ucar.edu<mailto:netcdfgroup at unidata.ucar.edu>" <netcdfgroup at unidata.ucar.edu<mailto:netcdfgroup at unidata.ucar.edu>>, ESIP Documentation LIst <esip-documentation at lists.esipfed.org<mailto:esip-documentation at lists.esipfed.org>>
Subject: Re: [Esip-documentation] [thredds] information on related files

Hi Nan,

I'd recommend using a 'metadata_link' attribute.

http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3#Additional_Metadata:_metadata_link_attribute

-Dave


On Wed, Sep 19, 2018 at 8:56 AM, Nan Galbraith <ngalbraith at whoi.edu<mailto:ngalbraith at whoi.edu>> wrote:
Hi ESIP, NetCDF, and THREDDS folks -

First, I'm sorry for the cross posting. I have a hard time figuring
out which NetCDF list does what; there are 'best practices' threads
on several lists, interspersed with install and development threads.

The OceanSITES project would like to find the most useful way to
provide a link within a NetCDF file to an external dataset.

> Another piece I am missing ... is an optional field, that link to a
> data DOI. Why? Here's an example: We operate an OceanSITES site off
> the Cape Verdes and the sediment trap data is ... not included in an
> netcdf file but processed and stored elsewhere
> https://doi.pangaea.de/10.1594/PANGAEA.863969

Does THREDDS have a standard way to provide links to related or
co-located data? Is this something we discussed as part of ESIP's
ACDD recommendations? I've been searching through my store
of old messages, and haven't come up with anything.

Thanks very much for any advice on this!

- Nan Galbraith


--
*******************************************************
* Nan Galbraith        Information Systems Specialist *
* Upper Ocean Processes Group            Mail Stop 29 *
* Woods Hole Oceanographic Institution                *
* Woods Hole, MA 02543                 (508) 289-2444 *
*******************************************************


_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


thredds mailing list
thredds at unidata.ucar.edu<mailto:thredds at unidata.ucar.edu>
For list information or to unsubscribe,  visit: http://www.unidata.ucar.edu/mailing_lists/



--
David Neufeld
Senior Associate Scientist
CIRES
Software Engineering Support Branch
Data Stewardship Division
NOAA National Centers for Environmental Information (NCEI)
Ph. 303-497-6507

Note:
The opinions expressed in this email are those of the author. They do not necessarily reflect the official views or policies of the University of Colorado, NOAA, Department of Commerce, or the US Government.



--
David Neufeld
Senior Associate Scientist
CIRES
Software Engineering Support Branch
Data Stewardship Division
NOAA National Centers for Environmental Information (NCEI)
Ph. 303-497-6507

Note:
The opinions expressed in this email are those of the author. They do not necessarily reflect the official views or policies of the University of Colorado, NOAA, Department of Commerce, or the US Government.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-documentation/attachments/20180924/ee8adfea/attachment-0001.html>