100 likes | 190 Views
Building the LTER Network Information System. NIS History, Then and Now. NIS Mission Statement. “… to promote advances in collaborative and synthetic ecological science at multiple temporal and spatial scales by providing the information management and
E N D
NIS Mission Statement “… to promote advances in collaborative and synthetic ecological science at multiple temporal and spatial scales by providing the information management and technology infrastructure to increase” • availability and quality of data from LTER sites • timeliness and number of LTER derived data products • knowledge generated from the synthesis of LTER data Bottom line: Make all LTER data available in a consistent format through a single web portal Provide derived and value-added data for community use
NIS Ingredients • Site collected data and metadata • LNO developed middleware (software) or integrated from other sources (e.g., sites, open source projects) • Derived data and metadata products • Data modules from other LTER science initiatives (e.g., ClimDB/HydroDB, EcoTrends)
LTER Network Information System Site data and metadata NIS middleware (PASTA) Value adding applications
Timeline Operational Prototype Apr 2012 • Integration into current web portal • Basic programming interface for discovery/access of data • Simplified workflow execution • Automated metadata/data harvesting with QA/QC for tabular data • Minimal provenance capture for data life-cycle May 2010 Production Deployment Start of Development • Full featured web portal • Standard programming interface for building external applications • Support for user-created workflows and creation of derived data • Automated metadata/data harvesting with QA/QC of tabular and complex data • Provenance capture for data life-cycle Apr 2014
Completing the NIS requires involvement from a broad cross-section of LTER members • Tiger Teams – to provide community dialogue and rapid feedback as part of specific component development teams • Requests for Comments – to receive thoughtful written comments from individuals or groups in the stakeholder community • Working Groups – to provide design, specification, and development on specific tasks and sub-components • Focus Groups - to get focused feedback on specific components • Surveys – to assess bi-directional communication effectiveness • NISAC – to provide advise and evaluation on the NIS • LTER Executive Board – to provide endorsement and evaluation
Tiger Teams • Community Collaboration • Working one-on-one with NIS developers • Commitment