Geospatial One Stop Modules Two and Three

Module 2 Inventory/Document existing Federal agency framework datasets and publish metadata to clearinghouse Module 3 Inventory/Document planned acquisition data and publish metadata to clearinghouse

Populating Geospatial One-Stop 1.Posting metadata to designated Geospatial One-Stop server 2.Use FGDC “smart select” option to select those FGDC registered US clearinghouses that contain Framework metadata

Simplifying Data Discovery through Geospatial One-Stop Metadata view options –Standard metadata view for metadata savvy –Abbreviated metadata gleaned from full metadata in abbreviated or question and answer format. Linked to the full metadata and to the data. XML tagged and formated by style sheet –Quick View- “geolibrary” card format Linked to the full metadata and to the data. XML tagged and formated by style sheet

Module 2 Metadata Content Contact Organization Address, City, etc. Telephone, Facsimile /agency website Data Information Data contact (Citation) Title Abstract & Purpose Publication Date Time Period Progress & Maintenance Bounding coordinates Theme Keywords Place Keywords Access Constraints Use Constraints Scale/Resolution Scope, Scale, Resolution Format On-line linkage (data & metadata) Data Access Fees Contact Information URL

Module 2- Existing Data Inventory/Documentation Part 1 All existing federal national coverage framework datasets Part 2 All existing federal regional/ local framework datasets Part 3 State and local framework datasets

Module 2 Existing Federal Data Part 1 Inventory existing metadata and post to clearinghouse includes: –Keywords: framework, theme name, place names –URL (on-line linkage) –Full metadata linked from abbreviated record

Module 2 Existing Federal Data Part 2 Create/ Submit metadata for Federal framework datasets with regional coverage Undocumented data may be documented through web interface template –All non-compliance FGDC metadata will be stamped with a non-compliance flag.

Module 2- Inventory/document State and local framework data sets Part 3 State and local framework metadata posted to a GOS registered clearinghouse, minimal metadata harvested as an index. Harvest state and local metadata from PTI survey or other existing data dictionaries.

Module 3 Metadata Content Contact Organization Address, City, etc. Telephone, Facsimile /agency website Project Information Project Lead Title Project type Time Period: start/end date Status Proposed, Planned, in-work Bounding coordinates Theme Keywords Place Keywords Scope, Scale, Resolution Format Investment Total projected investment % or $ needed Agency partner Timing Estimated start date Estimated completion date

Module 3- Planned Acquisition Data Federal agencies post planned acquisition data information for capital asset projects On-line “clearinghouse” to manage cross- agency information.

Metadata Interface Module 3 Capabilities On-line translator –Agency interacts with on-line metadata table, creating cross-walk between agency’s project tracking application and Module 3 metadata. Creates metatags/ Creates style sheet Creates searchable database –Access records by theme and geography

Additional Capabilities Metadata “stop and go” capability Subscription service / notification –Metadata updates/changes Customer survey: evaluating benefits derived from GOS Participation –Were partners located through GOS –Were partners successful leveraging funds

Metadata Interface non-existing metadata and data acquisition Project Lead Project Information Agency Contact Information Enter Once Enter X

Module 2 and 3 Host Initially hosted at donated site –Host site develops applications –Host site provides administration Records administration Data backup Web statistics Transfer to portal Ultimately hosted on portal

Metadata Access Distributed Pro: –No administrative responsibilities Staffing Con: –Loss of clearinghouse services (down) –Access speed

Metadata Access Pre- Portal Pro –One metadata server for all framework themes- One-Stop –No need for gateway to search multiple clearinghouses for framework datasets –Search intervals could be shorter Con –Multiple metadata files to update

Metadata Access Portal Pro –Contributor posts metadata only to agency’s clearinghouse – one metadata to update –Periodic portal “crawling” / up-to-date metadata Con –Metadata for metadata > Metadata must be tagged to indicate GOS Metadata in html format

Scope of Agency steward roles Metadata Contact: Inventory framework datasets Document framework data sets –Review metadata content –Create metadata for undocumented data National coverage Regional coverage Register agency clearinghouse as FGDC clearinghouse node Report completion to module lead

Scope of agency steward roles: GOS Theme Leads Communicate with agency Planned Acquisition Data reporting requirements Review GOS metadata assets to assure agency’s cooperation. Outreach- communicate agencies benefit in GOS participation.

Project Needs Framework agency metadata contacts –BLM: Bob Ader and Nancy von Meyer Interim Metadata clearinghouse/host –Preferably on application developer’s server –Provides clearinghouse/data administration services

Project Needs On-line application (one interface for 2/3) –Importing existing metadata/reports/survey –Harvesting metadata for GOS template –Parse files –Translator/Crosswalk application –GOS metadata website Access- small databases SQL/Oracle- large complex databases Stop and Go capability –Searchable database –Subscription service