-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TRANSECT_NUM field is not being populated #251
Comments
@ToddVolkening what are your thoughts on this? |
Craig,
It looks like the Transect_Num field is not being populated to the
database, but a unique Transect_ID is. Scott and Nathan were wondering
what our thoughts on this and whether it's an issue since the Transect_ID
is being populated to the database. What are your thoughts on this? Do
you think we need to record the Transect Number to the database or is the
unique Transect ID sufficient?
For a little background and context, you can view it on GitHub
<#251 (comment)>
Please let us know what you think.
Thanks,
~Todd
…On Mon, May 17, 2021 at 1:29 PM Nathan Kota ***@***.***> wrote:
@ToddVolkening <https://github.com/ToddVolkening> what are your thoughts
on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#251 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIM2EQWYSQ5ZI6S4PSN4KW3TOFVC3ANCNFSM4447RAQA>
.
--
Todd Volkening
Senior GIS Analyst
Utah Division of Wildlife Resources
801-244-5878
***@***.***
|
I heard back from Craig Walker and responded " I think the transect ID is
sufficient."
On Thu, May 20, 2021 at 10:20 AM Todd Volkening ***@***.***>
wrote:
… Craig,
It looks like the Transect_Num field is not being populated to the
database, but a unique Transect_ID is. Scott and Nathan were wondering
what our thoughts on this and whether it's an issue since the Transect_ID
is being populated to the database. What are your thoughts on this? Do
you think we need to record the Transect Number to the database or is the
unique Transect ID sufficient?
For a little background and context, you can view it on GitHub
<#251 (comment)>
Please let us know what you think.
Thanks,
~Todd
On Mon, May 17, 2021 at 1:29 PM Nathan Kota ***@***.***>
wrote:
> @ToddVolkening <https://github.com/ToddVolkening> what are your thoughts
> on this?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#251 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AIM2EQWYSQ5ZI6S4PSN4KW3TOFVC3ANCNFSM4447RAQA>
> .
>
--
Todd Volkening
Senior GIS Analyst
Utah Division of Wildlife Resources
801-244-5878
***@***.***
--
Todd Volkening
Senior GIS Analyst
Utah Division of Wildlife Resources
801-244-5878
***@***.***
|
Thanks @ToddVolkening. Scott is out this week. We will most likely wait until the new fiscal year when the agreement renews to deal with this, and start working the enhancements and updates back into our work schedule. |
This is just a database change. This field is no longer in the app. |
I've removed the I also successfully tested submitting a report with transect data in dev. |
I'm not sure it's ever been populated looking at the code. I wonder if there's any use for it since we already have TRANSECT_ID. Maybe we can just drop it from the table?
The text was updated successfully, but these errors were encountered: