1 / 15

Getting Ready for STEVE

Getting Ready for STEVE. Mapping Tools for STEVE William R. Bolton, Jr. State Registrar and Director Division of Vital Records Administration New Hampshire Department of State. NHVRINweb Development. NHVRINweb = New Hampshire Vital Records Information Network web

devika
Download Presentation

Getting Ready for STEVE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Getting Ready for STEVE Mapping Tools for STEVE William R. Bolton, Jr. State Registrar and Director Division of Vital Records Administration New Hampshire Department of State

  2. NHVRINweb Development • NHVRINweb = New Hampshire Vital Records Information Network web • http://nhvrinweb.sos.nh.gov • Real-time birth, death, marriage and divorce WDQS • 2005-2007 project involving NH DVRA/NCHS/Constella partnership • 10/30/07 implementation

  3. NHVRINweb Development • 3 part development • Presentation layer • Database layer • ETL Tool • Extraction, Translation (into IJE format) and Load (into an ODS) • Scripting Engine • Viewer for viewing IJE data • Dovetails nicely with STEVE

  4. NHVRINweb Development • ETL tool as originally specified was derailed due to problematic DBA • NH ETL tool was developed specifically for Oracle DB • Could be shared, but presently tailored to NH Oracle database • Time consuming to further modify for useful software tool

  5. Current State Issues • Multiple Source Database Platforms • Oracle, MySQL, SQL Server, PostgreSQL • Varying Source Database Designs • Complex & limited sharing of crosswalk and transformation data and code

  6. ETL Application

  7. Components & Features • Embedded Database • Transformation data & crosswalks • Transformation data management • Import & Export • Provides support for sharing and maintaining transformation data

  8. Components & Features • Scripting Engine • Transparent • Easy code sharing • Not a black box • Full featured C# language • Libraries for accessing, managing & validating IJE formatted data • Colocated reference information is used to verify that translation worked correctly

  9. Components & Features • Management UI • Scheduling • Connection management • Rule & crosswalk editing • Reporting & Logging

  10. That’s Nice; but Where Do We Go From Here? • Piggy-back on work already done • Generic version ETL is 1/3 to 1/2 done • Estimated 1-3 months to complete development • Need test environments at several states

  11. That’s Nice; but Where Do We Go From Here? • Options for Integration Based on Registration Area’s Level of Comfort: • Use local IT staff to integrate and maintain ETL • Use developer to integrate tool and local IT staff can maintain • Use developer to integrate and maintain

  12. That’s Nice; but Where Do We Go From Here? • Likely savings in level of effort if states with similar software are able to partner with ETL configuration • Single ETL will benefit ease of incorporating future IJE modifications • Ancillary Benefit – WDQS 

  13. That’s Nice; but Where Do We Go From Here? • Investigate Alternatives • Registration areas already report an IJE-Lite file to NCHS • Registration area may be able to use DTS tools that SQL Server provides • Registration area may use current EBR/EDR software developer to further develop output files

  14. Questions? William R. Bolton, Jr. State Registrar and Director Division of Vital Records Administration New Hampshire Department of State william.bolton@sos.nh.gov

More Related