|
Month
|
Tasks
|
Notes
|
|
January
|
Modify existing
and/or create new stored procedures and triggers for data validation
as necessary
|
|
| |
Modify database
objects (tables, indexes, etc.) as required for the next season
|
|
| |
Run backup of
database following any modifications to data or database structure
(including stored procedures and triggers)
|
|
| |
Develop new
or modify existing reports if needed
|
|
| |
Contact agencies
to determine database needs for upcoming trapping season
|
|
|
February
|
Continue as
in January
|
|
|
March
|
Move previous
season’s data into archive tables (including quad and county-based
data from node at MSU – data can be copied from snapshots)
|
Run backup of
database both before and after archiving data
|
| |
Clear data from
tables following data archival, DBA should do the same at MSU
|
|
| |
Load new predetermined
site data into site_locations table
|
DBA at MSU will
also need to load data into site_locations and site_locations_cty
table
|
| |
Enter trapper
info into database if received from agencies
|
|
| |
Update site_locations
table as changes are provided by agencies
|
|
|
Month
|
Tasks
|
Notes
|
|
April
|
Enter trapper
info into database prior to loading trap placement data
|
DBA at MSU should
do the same at that node
|
| |
Enter trapper
territory (bid unit) data into bid_unit table after trapper info
has been entered
|
ID from people
table is used as contractor number in bid_unit table (not all agencies
provide bid unit info)
|
| |
Begin receiving
and processing trap placement data from earliest trapping areas
(NC, WV, Eastern VA)
|
text files from
GPS units, database is updated automatically if GPS File Uploader
software is used
|
| |
WWW reports
are generated and updated automatically once data are received
|
data errors,
moth population data, and QC reports
|
| |
Perform offline
back-up of database twice weekly
|
Run full export
then shutdown database for offline backup to tape
|
| |
Create new or
modify existing reports upon request
|
|
| |
Correct data
errors as corrections are received from field
|
|
| |
Continue to
update site_locations table as site changes are received from agencies
|
|
| |
Create a database
job that will run nightly snapshot updates of data at MSU
|
Usually scheduled
to run at approximately 6:00 a.m.
|
|
May
|
Continue as
in April
|
|
| |
Continue to
update site_locations table as site changes are received from agencies
|
|
| |
Begin receiving
trap placement data from remainder of trapping areas
|
|
| |
Begin receiving
trap inspection data from earlier trapping areas, QC inspections
arriving first from NC and Eastern VA
|
|
|
June
|
Continue as
in May
|
|
| |
Begin receiving
and processing trap inspection data from remainder of trapping areas
|
GPS
files load automatically with GPS File Uploader software
|
|
July
|
Continue as
in June
|
|
| |
All sites should
be addressed, attempt to resolve all trap placement errors
|
WI, MN may be
an exception
|
|
August
|
Continue as
in July
|
|
| |
All WI and MN
sites should be addressed, attempt to resolve all trap placement
errors
|
DBA at MSU responsibility
|
|
Month
|
Tasks
|
Notes
|
|
September
|
Continue as
in August
|
|
| |
Resolve all
errors, finalize data by third week
|
All states except
IL, MI, MN and WI
|
| |
Generate GIS
files and data reports for post-season analysis
|
Planning meetings
usually begin in early October
|
|
October
|
Resolve all
errors, finalize IL data by first week
|
Illinois only
– assist DBA at MSU if needed
|
|
November
|
Perform database
administration
|
- analyze database
objects (tables, indexes, etc.) for efficient
space usage , modify storage parameters as necessary
|
| |
|
- install software
(upgrades, new software, etc.)
|
| |
Resolve all
errors, finalize data by first week (MI, MN, WI)
|
assist DBA at
MSU if needed
|
| |
Modify existing
and/or create new stored procedures and database triggers
|
|
| |
Create files
to be submitted to NAPIS database
|
Provide files
to cooperators, agencies will submit files to NAPIS. Virginia files
should be given to Virginia’s State Survey Coordinator. Copy NAPIS
coordinator at Perdue on all files.
|
| |
Develop new
or modify existing reports as needed
|
|
|
December
|
Run final back-up
of database to tape, including full export
|
Two backups
can be run, store one copy off-site
|
| |
Modify database
objects (tables, indexes, etc.) as required for the next season
|
|
| |
Run back-up
of database following any modifications to data or database structure
(including stored procedures and triggers)
|
|
| |
Perform database
administration
|
|
| |
Stop job that
runs the nightly snapshot update until next trapping season
|
|
| |
Develop new
or modify existing reports as needed
|
|