[Esip-preserve] DataCite to require "landing pages"

[Bruce Barkstrom]

Any thoughts about lightening the load on the user if
he or she if familiar with the site and has downloaded
other files before?  Why does a user like that need the
full collection of metadata?

Bruce B.

On Wed, Feb 29, 2012 at 3:06 PM, Kenneth S. Casey <kenneth.casey at noaa.gov>wrote:

> Jeff,
>
> On Feb 29, 2012, at 1:57 PM, Dr.Jeff de La Beaujardiere wrote:
>
> Can an ISO 19139 (XML) metadata record serve as a landing page?
> If not, what about HTML produced from the XML using a stylesheet?
>
>
> Sure... that is basically what a lot of portal systems do right now, with
> ISO or FGDC.  We in fact fought the battle with data.gov to get them to
> allow us to have their "one-click to data" policy mean "one-click to the
> landing page", since pointing a user directly to a binary data file is a
> completely stupid thing to do. Without the metadata, the user has no idea
> what they are being "one-clicked" to.  Even if it is a well-structued
> netCDF with lots of internal metadata it is not generally a good idea.
>
> Ken
>
>
> -Jeff DLB
>
> NEW PHONE NUMBER: +1 301 713 7175
> Jeff de La Beaujardière, PhD
> NOAA Data Management Architect (NESDIS/OSD/TPIO)
> 1335 East-West Hwy, Silver Spring MD 20910 USA
>
>
> On 2012-02-22 12:55, Greg Janée wrote:
>
> There are some changes brewing at DataCite regarding DOI requirements. Per
> Joan
>
> Starr:
>
>
> "There is a very strong push within the group for a requirement that all
> DOIs
>
> point to landing pages and not to the object directly. [For submitters that
>
> don't provide their own landing pages] DataCite is going to create canned
>
> landing pages based on the metadata that submitters provide."
>
>
> What constitutes a "landing page"? Again, per Joan:
>
>
> "The landing page typically contains one or more of the following:
>
> +full citation of the data
>
> +statement on access to data (such as a link to the data or usage
> restriction
>
> information)
>
> +associated metadata
>
> +information, software, or context required for unpackaging, reading and
>
> interpreting the data"
>
>
> I'm curious what this group thinks about this requirement. It certainly
> narrows
>
> the scope of applicability for DOIs.
>
>
> -Greg
>
>
> _______________________________________________
>
> Esip-preserve mailing list
>
> Esip-preserve at lists.esipfed.org
>
> http://www.lists.esipfed.org/mailman/listinfo/esip-preserve
>
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-preserve
>
>
>
> [NOTE: The opinions expressed in this email are those of the author alone
> and do not necessarily reflect official NOAA, Department of Commerce, or
> US government policy.]
>
> Kenneth S. Casey, Ph.D.
> Technical Director
> NOAA National Oceanographic Data Center
> 1315 East-West Highway
> Silver Spring MD 20910
> 301-713-3272 ext 133
> http://www.nodc.noaa.gov/
> <http://www.facebook.com/noaa.nodc> <http://www.facebook.com/noaa.nodc>
> <http://www.facebook.com/feeds/page.php?id=178512945559611&format=rss20>
>  <http://www.facebook.com/feeds/page.php?id=178512945559611&format=rss20>
>
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-preserve
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-preserve/attachments/20120229/edb78e55/attachment-0001.html>