Welcome to NatureServe. NatureServe Web Services

n Home?

About NatureServe Web Services
Literature
News Archive

Browse Web Services
Name Search
Get Species Data
Get Ecological Systems
Get Species Location Data
Species Presence Indicator

Technical Resources
Code Samples
Species Schemas
Species Occurrence Schemas
Technical Library

Provide Feedback
Taxonomic Reconciliation
User Registration
Security Administration
Submit User Stories
Contact Us

For NatureServe Data Providers
EO Service
Support Resources

 

Security Feedback

Your comments and questions help us to improve our service.  Any information you provide is confidential and will not be shared with any other organization or individuals.

Attribute Sets:

On the prototype Element Occurrence dataset configuration screen, we currently allow you to select a pre-determined subset of attributes that may be delivered with non-sensitive data, and a different attribute subset for sensitive data. The choices now shown in the drop-down menu for this selection are as follows:

  • None
  • Basic
  • Comprehensive
  • Unrestricted

A survey was conducted in September requesting your input on which EO attribute fields may / may not be delivered with datasets consisting of non-precise data (such as quad / mapsheet or more general). The survey also asked for more information about the use of "sensitive data" flags in your program. The results of this survey are now being reviewed. Based on the survey responses, we will recommend a subset of EO attributes for the Basic and Comprehensive options. This will provide you with the flexibility to control the amount of tabular data that is released for either sensitive or non-sensitive data to different groups of users. Selecting None would indicate that you do not want any attributes released with the dataset for the given user/group. Selecting Unrestricted would indicate that you are comfortable releasing all attributes with the dataset for the given user/group. The complete EO schema definition outlining which attributes will be included in Internet Data Delivery products is still under development, so the exact list represented by the Unrestricted option is not yet finalized.

If you have a general recommendation about the kind of options now represented in the security administration tool for controling the release of tabular attribute data to users, please provide your comments.

Spatial Data Resolution:

On the prototype Element Occurrence dataset configuration screen, we currently allow you to select indicate the finest spatial scale at which the user may view spatial data for non-sensitive entities, and to select a different spatial scale for sensitive entities. The choices now shown on the drop-down menu for this selection is as follows:

  • None
  • County
  • USGS Quad Equiv.
  • Generalized/Fuzzed EO Polygon
  • Precise EO Polygon

In order to maximize the usability of the Internet Data Delivery system for our multi-jurisdicational clients, we are strongly recommending that we provide a discrete set of spatial resolution options for representing Element Occurrence location information. For the Generalized/Fuzzed EO Polygon option, what is your recommendation for the spatial resolution that is appropriate to provide as an intermediate option between Precise EO Polygon locations and the generalized USGS Quad (or Canadian equivalent)?

Is there another spatial resolution option that you would recommend we include?

Other:

Are there any security scenarios you can think of for your program that cannot be expressed as data access policies using the administration tools as illustrated in the prototype screens? Think about your current data delivery mechanisms and the way you control access to your data, and then think about the options that the security administration tool allows you to configure for users and user groups when answering this question.


 

Email:
Comments:




 



 

Copyright © 2006
NatureServe
 
Sitemap www.natureserve.org Contact Us Acknowledgements

Copyright © 2007. NatureServe.

NatureServe.org d Contact Usd Site Mapd Acknowledgements