data access server
DESCRIPTION
Data Access Server. The Water Cooler Session. Mark Servilla & Duane Costa 17/18 February 2009. Background. LTER Network Data Access Policy Approved 6 April 2005 by LTER Coordinating Committee Issues addressed: Release of LTER data products (along with metadata) - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/1.jpg)
Data Access Server
Mark Servilla & Duane Costa
17/18 February 2009
The Water Cooler Session
![Page 2: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/2.jpg)
Background LTER Network Data Access Policy
– Approved 6 April 2005 by LTER Coordinating Committee
– Issues addressed:• Release of LTER data products (along with metadata)• User registration for accessing data, includes
– Obtaining Name, Affiliation, Email Address, and Full Contact Information
– Must accept User Agreement (General and/or Restricted)
– Provide statement of intended use of data• License agreements specifying conditions for data use
![Page 3: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/3.jpg)
Data Access Server
![Page 4: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/4.jpg)
DAS Service Goals LTER Data Access Policy compliant service
– Registration
– Authentication
– Auditing
– Notification
– Reporting
Low impact on site Information Managers/ Administrators– Minimal replacement of data URL paths
– Administrative interface for proxy URL to real URL mapping
![Page 5: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/5.jpg)
DAS Software Stack
![Page 6: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/6.jpg)
User Registration & Authentication
Separate user table for registration specific information, including statement of intended use (all users)
Authentication– LTER LDAP
– Local pass-phrase challenge for non-LTER users
Supports “cookies” for automatic login By-pass for 3rd party applications (e.g. Kepler) Filter for “search bots” or “web spiders”
![Page 7: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/7.jpg)
Data URLs
Arctic LTER
North Inlet LTER
Georgia Coastal Ecosystem LTER
![Page 8: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/8.jpg)
URL Heads and URL Tails
Arctic LTER
North Inlet LTER
Georgia Coastal Ecosystem LTER
![Page 9: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/9.jpg)
DAS Proxy URLs
Arctic LTER
North Inlet LTER
Georgia Coastal Ecosystem LTER
![Page 10: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/10.jpg)
Generalized Use Case
Step 1: User selects DAS proxy URL located in metadata document
![Page 11: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/11.jpg)
Generalized Use Case
Step 1: User selects DAS proxy URL located in metadata document
Step 2: DAS service verifies user has authenticated and has accepted LTER Data Access Policy
![Page 12: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/12.jpg)
Generalized Use Case Step 3: DAS uses document ID to obtain
EML document for notification content– Contacts, Creators, and Metadata Providers
![Page 13: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/13.jpg)
Generalized Use Case
Step 4: DAS uses document ID to obtain EML document for the data 'entity' name
![Page 14: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/14.jpg)
Generalized Use Case
Step 5: DAS sends email notification to data owner and data user
![Page 15: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/15.jpg)
Generalized Use Case
Step 5: DAS sends email notification to data owner and data user
Step 6: DAS records access in audit log
![Page 16: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/16.jpg)
Generalize Use Case
Step 7: DAS uses document ID to determine the LTER site
![Page 17: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/17.jpg)
Generalize Use Case
Step 7: DAS uses document ID to determine the LTER site
Step 8: DAS selects the URLHead value entered by the LTER site
![Page 18: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/18.jpg)
Generalize Use Case
Step 9: DAS appends URLTail value from the proxy URL to the URLHead to re-form the original data URL
+
![Page 19: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/19.jpg)
Generalize Use Case
Step 9: DAS appends URLTail value from the proxy URL to the URLHead to re-form the original data URL
Step 10: DAS uses original data URL to obtain data and pass-through to user
+
![Page 20: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/20.jpg)
DAS Administration
![Page 21: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/21.jpg)
DAS Administration
![Page 22: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/22.jpg)
DAS Audit Report
![Page 23: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/23.jpg)
DAS Audit Report
![Page 24: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/24.jpg)
Email Notifications
Data Owner Email
Data User Email
![Page 25: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/25.jpg)
Information about DAS
General Information and Status– http://intranet.lternet.edu/im/forum/200
Project Plan– http://urban.lternet.edu/viewvc/trunk/projects/DAS/docs/DAS-
ProjectPlan.pdf?view=co&root=NIS
Project Management– http://fire.lternet.edu/dotproject/index.php?m=projects&a=
view&project_id=44
Project Bugzilla– http://fire.lternet.edu/cgi-bin/bugzilla/buglist.cgi?query_format=specific&
order=relevance+desc&bug_status=__open__&product= Data+Access+Server&content=
![Page 26: Data Access Server](https://reader035.vdocuments.us/reader035/viewer/2022062322/56814d19550346895dba52e6/html5/thumbnails/26.jpg)
Thank you!