-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
modifications to Nature of ID and Basis of Citation #515
Comments
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Whatever we do with this list - can we please, immediately remove 'ID of Kin' as the default? The default should be NULL like every other yellow field in data entry! Too many techs accidentally let records go with 'ID of Kin' when they shouldn't. And fixing them is a one-at-a-time PITA. |
YES, a thousand times yes! This is a weird thing for cultural items and we get way too many of them. |
Yes, absolutely, please. Ditto for any dropdown anywhere - all default
values should be null.
Could we get a list by collection of all "ID of Kin" records so we can go
through and identify which need to be corrected?
…On Wed, Jan 30, 2019 at 3:07 PM Angela Linn ***@***.***> wrote:
can we please, immediately remove 'ID of Kin' as the default? The default
should be NULL like every other yellow field in data entry!
YES, a thousand times yes! This is a weird thing for cultural items and we
get way too many of them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#515 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOH0hKr-MUejbBurT293XpsYhhaCw6Rmks5vIheegaJpZM4aa6QW>
.
|
Original issue reported on code.google.com by
carla...@gmail.com
on 19 Jan 2012 at 1:16The text was updated successfully, but these errors were encountered: