Presentation is loading. Please wait.

Presentation is loading. Please wait.

Heartland Network Data Management in the Heartland Network Background –Centralized staff –Protocols developed and implemented primarily in-house –12 of.

Similar presentations


Presentation on theme: "Heartland Network Data Management in the Heartland Network Background –Centralized staff –Protocols developed and implemented primarily in-house –12 of."— Presentation transcript:

1 Heartland Network Data Management in the Heartland Network Background –Centralized staff –Protocols developed and implemented primarily in-house –12 of 15 network parks are fairly small and represent places and events of historic and cultural significance –Integrated with prototype

2 Heartland Network What Have We Learned? Data management is hard work!

3 Heartland Network Revisiting Priorities –Data mining –NPSpecies and other service-wide databases –Data management planning –ATR/COR on protocol development projects –GIS/GPS support to monitoring projects In –Data management needs assessment with project leads –Managing data work flow and security –Database development and maintenance –Writing data management SOPs

4 Heartland Network Establishing Clear Roles and Responsibilities Our approach –DM is shared responsibility among Project Manager and Data Manager –Project Manager is expected to have working knowledge of relational databases and ability to independently conduct basic data queries and exports Implications –Platform and design complexity are constrained –Increases risk of data loss –Creates some redundancy in database skills –Increases PI interaction and ultimately results in a better customized product

5 Heartland Network Managing Work Flow Idealized protocol development time line Pilot sampling Internal review Methodology Finalize SOPs Preliminary analyses Objectives Peer review Final protocol T – 1 yr T –2 yr Final version DB Beta version of DB Write DM SOP Database development times should be short, for each version, about 120 days. Keep PIs' involved and the initial database design simple. Add to the complexity later.

6 Heartland Network Minimizing Complexity By Considering Return on Investment The Subprime Syndrome Database Complexity Efficiency/Usability Ratio to Development/Maintenance Effort High Low High Low

7 Heartland Network Get The Data In! Find a balance between data security, ergonomics, efficiency, and data management capacity

8 Heartland Network Get The Data Out! Find a balance between automated data analyses and simple data export routines

9 Heartland Network Inspirational Message Albeit Poorly Crafted Data management is hard work! Yes You Can!


Download ppt "Heartland Network Data Management in the Heartland Network Background –Centralized staff –Protocols developed and implemented primarily in-house –12 of."

Similar presentations


Ads by Google