Best practice for using "field number" over "trapline identifier"? #8956
kderieg322079
started this conversation in
General
Replies: 1 comment
-
Those can't be field numbers, please check the definition.
Please don't use this, it's not appropriate for any purpose and is guaranteed to result in messy data and more work.
Sounds like a field number to me!
That's a collector number if it refers to an individual person's "book", or an identifier if it's something less personal. In either case, issued by is critical. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm wondering if anyone else has been using "trapline identifier" but migrated to "field number" per the recommendation in the code table. I have data that have field numbers assigned to each captured animal, then trapline ID numbers assigned to all animals captured on that trapline.
Any one have any ideas of the best way to differentiate the two? Should I just put "trapline ID" in the identifier_remark? That is what the field is called on our paper sheets and I want to maintain that connection.
Any thoughts welcome!
Beta Was this translation helpful? Give feedback.
All reactions