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

Thu Mar 1 07:43:17 EST 2012

On Mar 1, 2012, at 7:08 AM, Kenneth S. Casey wrote:

> In these cases when the user already knows the data, they can just go straight to their access method of choice... FTP, HTTP, Hyrax, TDS, Live Access Server, ArcGIS Server... whatever happens to be available and appropriate to the particular dataset.  One of the key features of the landing page, in addition to describing what the data set is, is to clearly identify the available access methods.
> 
> -Ken
> 

In some remote sensing cases, like Level 2 scenes, it is not possible or useful to drop the user straight into the FTP|Hyrax|TDS|LAS|ArcGIS server.  They need to be at a point where they can execute a space-time query for the specific scenes of interest.  This could be done with a "granule-level" OpenSearch Description Document, or other links that take you to a search engine with a dataset identifier passed as context.  Can this count as "access"?

> 
> On Feb 29, 2012, at 5:03 PM, Mark A. Parsons wrote:
> 
>> Remember this is just for the citation. So the typical use case is someone reading a paper who then wants to follow up on a reference. The user who already knows about the data may have multiple means of access including direct machine access, but that's a different situation than someonen following up a reference.
>> 
>> Cheers,
>> 
>> -m. 
>> On 29 Feb 2012, at 2:59 PM, Bruce Barkstrom wrote:
>> 
>>> 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/
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 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/
> <facebook.png><RSS.png>
> 
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-preserve

--
Dr. Christopher Lynnes, NASA/GSFC, Code 610.2, 301-614-5185