Switch domain list in the Dominant Overstory and Dominant Understory fields

[ToddVolkening]

Habitat > Dominant Overstory and Dominant Understory domain lists are still switched.

Take the domain list that's currently fueling the 'Dominant Overstory' field and instead apply it to the 'Dominant Understory' field. Conversely, take the domain list for 'Dominant Understory' field and apply it to the 'Dominant Overstory' field.

Previously referenced as #75 in Google Word Doc & AGRC GitHub #78

Referenced as UDWR #412

[steveoh]

original #78
pr #98

Please list the values that are supposed to be in each domain. This migration should have swapped the values.

[steveoh]

@ToddVolkening Please list the values that are supposed to be in each domain. This migration should have swapped the values.

[ToddVolkening]

Habitat tab > The 'Dominant Overstory' field domain list should start with American plum, Big saltbrush, Big tooth maple,........ The 'Dominant Understory' field domain list should start with Alkali sacation, Anderson peachbrush, Autumn eleagus,........ I looked at your 'This migration' hyperlink and the reason why the swap didn't work is that the domain values were still incorrectly listed (reversed).

…

On Thu, Apr 5, 2018 at 9:44 AM, steveoh ***@***.***> wrote: @ToddVolkening <https://github.com/ToddVolkening> Please list the values that are supposed to be in each domain. This migration <https://github.com/agrc/electrofishing/blob/master/scripts/migrations/migration_78.py> should have swapped the values. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#122 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AhmiQk2S9h76bz0S1UyC-7y1-XVcEbuzks5tljvNgaJpZM4TFkYn> .

-- Todd Volkening GIS Analyst Utah Division of Wildlife Resources 801-244-5878 [email protected]

[stdavis]

This is wrong AGAIN!

[steveoh]

ok. i cannot do it right so I'm not doing it.

[stdavis]

I wonder if this was a mistake with the xml file...

[stdavis]

DATABASESCHEMA.XML looks correct to me:

I bet that I just forgot to run migration_78.py after you fixed it the last time. I went ahead and ran it on the test database and the app reflects the correct values now.