search

NCRN / ForestVeg

Front end application for NCRN Forest Vegetation Access database.
3 stars 1 forks source link

Add Berberis bealei to plants table #99

Closed lizmatthews03 closed 5 years ago

lizmatthews03 commented 5 years ago

Previously recognized name was Mahonia bealei, but the whole genus of Mahonia has been moved to Berberis.

The record of Mahonia spp. at NACE-0399 (2018) should be updated to the new taxon.

blcampbell commented 5 years ago

@lizmatthews03

Currently we have 2 Mahonia records in the plants table - Mahonia spp. and Mahonia aquifolium

Assuming these two plants table records (spp. & aquifolium) would be adjusted to the new Genus Berberis ...

Several questions:

Above I'm assuming that we'd simply swap out the old genus for the new in the plants table, however it begs the question - Should we be tracking these types of taxon changes?

A swapout would have the effect of changing all existing monitoring records that noted either Mahonia spp. or Mahonia aquifolium to the respective Berberis spp. or Berberis aquifolium depending on the TSN selected in the monitoring record.

This matters IF we need to know that the species taxonomy was the old vs. new taxonomy. There are some complexities to tracking changes as a TSN values are used to identify species and likely the "new" taxonomy would have the same TSN as the old.

OTOH taxon change tracking could be a simpler solution of a separate table with TSN, original value, changed value, date of change, reason for change (or similar); where the updates are done at the same time as the SQL db script run to implement a plant record change from one genus to another (or similar change).

Of course if we don't need to track the changes, that is easier. However going back to identify which monitoring records used the old genus would not be possible.

Implementing taxon tracking in the shortened 2019 pre-season is unlikely, however the seed of discussion would be planted for a future solution.

blcampbell commented 5 years ago

@lizmatthews03

Reviewing the I&M minimum implementation standards indicates we should be addressing taxonomic references per TSN (issues #100, #101). So references for plant records are needed (see #101) - both existing & new as in the case of Berberis bealei.

lizmatthews03 commented 5 years ago

A few thoughts:

Liz Matthews, PhD Botanist National Capital Region Network Inventory and Monitoring National Park Service https://www.nps.gov/im/ncrn/index.htm https://www.nps.gov/im/ncrn/index.htm email: elizabeth_matthews@nps.gov office: 202-339-8303 cell: 828-337-2946

On Fri, Feb 1, 2019 at 2:34 PM Bonnie Campbell notifications@github.com wrote:

@lizmatthews03 https://github.com/lizmatthews03

Currently we have 2 Mahonia records in the plants table - Mahonia spp. and Mahonia aquifolium

Assuming these two plants table records (spp. & aquifolium) would be adjusted to the new Genus Berberis ...

Several questions:

  • Should the order & family remain Ranunculales & Berberidaceae respectively?
  • For the new plant record for Berberis bealei (to be added) we'll need these -- TSN (is there an "accepted TSN") -- order & family (if different from Ranunculales & Berberidaceae respectively) -- woody shrub as the other two? -- common name -- should it be a 'favorite' in the application? -- plant code

Above I'm assuming that we'd simply swap out the old genus for the new in the plants table, however it begs the question - Should we be tracking these types of taxon changes?

A swapout would have the effect of changing all existing monitoring records that noted either Mahonia spp. or Mahonia aquifolium to the respective Berberis spp. or Berberis aquifolium depending on the TSN selected in the monitoring record.

This matters IF we need to know that the species taxonomy was the old vs. new taxonomy. There are some complexities to tracking changes as a TSN values are used to identify species and likely the "new" taxonomy would have the same TSN as the old.

OTOH taxon change tracking could be a simpler solution of a separate table with TSN, original value, changed value, date of change, reason for change (or similar); where the updates are done at the same time as the SQL db script run to implement a plant record change from one genus to another (or similar change).

Of course if we don't need to track the changes, that is easier. However going back to identify which monitoring records used the old genus would not be possible.

Implementing taxon tracking in the shortened 2019 pre-season is unlikely, however the seed of discussion would be planted for a future solution.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NCRN/ForestVeg/issues/99#issuecomment-459841178, or mute the thread https://github.com/notifications/unsubscribe-auth/AHyzjqTRw5H0aOzVZmYAJ20tIXMdRFL4ks5vJJaUgaJpZM4acrJP .

blcampbell commented 5 years ago

Following up: Per database field definition PLANTS_Code is the USDA code for the plant. Berberis bealei has the code BEBE2 (if it were Mahonia bealei it would be MABE2.