State Wildlife Action Plan (SWAP) data project
Description
There is interest in having a vendor combine the existing sources into an easily accessed new source that can support the written SWAP, the data supply to a Regional database, and to support an interactive GIS tool for citizens.
Once compiled and confirmed, the new data source will be considered locked and serve as-is until the next the 10 year cycle in 35.
Problem Statement
A 10 year plan requirement is due 2025 which is supported by various Excel and Access data sources that are not easily tapped and merged for analysis. Coincident with the SWAP submission, data must go to Regional wildlife database and that output is not easily compiled. There is also no way for citizens and groups to readily use the written, PDF format NJ SWAP submission, or the underlying Access/Excel data in their efforts to take actions supporting wildlife.
Project Justification
The planning and submission of data is mandated, but not easily done with current tools.
Estimated Transactions
None
Target Rollout Date
None
Target Rollout Date Reason
None
Attachments
Activity
Show:
Create issue
Completed
Add watchers
Details
Sponsoring Leadership Area
Fish and Wildlife
Sponsoring Leadership Area's Priority
None
Program Area Lead(s)
None
DOIT technical lead(s)
None
All Involved Leadership Areas
Div. of Information TechnologyFish and Wildlife
Created: 9 February 2024, 17:37
Updated:
25 November 2024, 19:11
At today’s LTC/IT Project coordination meeting Kim confirmed this project has been completed.
At a meeting 2/5 with Program and DOIT leads it was clarified that while a vendor will deliver a consolidated Postgres database, this will be used for one-time generation of csv output for the regional update, and for one-time output to a GIS feature that will not require the Postgres database to be hosted, managed or maintained for any ongoing purpose. It will be archived for any unexpected need or failure of resultant products. There is also no need to host or maintain the data entry software beyond the time of final deliverables, as they will mark the lock-up period of the data, after which no regular updates are expected. DOIT will have the ability to make the rare back-end edit for minor data errors, and to resurrect the Postgres database if needed.