search

bcgov / invasivesbc

Inventory and database repository for the creation, treatment, and report on BC Invasive plants and animals.
Apache License 2.0
13 stars 4 forks source link

Document Code table update process #332

Closed micheal-w-wells closed 2 years ago

micheal-w-wells commented 3 years ago

Notify @klefler once done.

Other info:

_I’ve recently documented a Reference Data Guide on the IIT Data Design Guidelines page (there’s a lot of info there, but this page has some high-level stuff that could be referenced… https://apps.nrs.gov.bc.ca/int/confluence/display/NRMDDDG/Reference+Data+Best+Practices and this page (still in DRAFT) starts to outline specific topics DA sees with code requests https://apps.nrs.gov.bc.ca/int/confluence/display/NRMDDDG/Common+Reference+Data+Topics). This documentation is still a work in progress, but my goal would be to use some of it to help data managers understand best practices / approaches to managing reference data. It’s a service that DA provided / provides for 50+ FLNRO applications (including IAPP), so we have lots of experience to share.

Code Management Procedures The process for managing the code values should be documented… for example; when is a new code a new record versus just changing a code value or description? When does an existing code get expired? If a value changes does relating data also need to be changed (data conversion)? Are these code values that this program area can/should change (i.e. are they actually managed by another agency)?_

micheal-w-wells commented 3 years ago

@mikeshasko Can you write up a quick summary of how we are managing code tables based on the notes above? Then we can let Kristen know and close this one.