-
-
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
Remove requirement for date and determiner on collection object attributes #4184
Comments
It's "required" because someone thought it should be at some point, it would be good to decide how to handle this as a Community. I can confirm that date is not required in the table. I don't have much opinion and this certainly isn't my decision to make, unassigning me. |
For old specimens or even recent transfers, we often have attribute data, but no information on when they were recorded. I vote this is made optional in data entry. I'm fine with keeping determiner as required because you can always enter unknown - that's not an option for dates. |
I agree. We don't require these for part attributes. Let's be consistent.
…On Thu, Oct 13, 2022 at 9:43 AM Andrew Doll ***@***.***> wrote:
* [EXTERNAL]*
option of leaving this blank for no data records
For old specimens or even recent transfers, we often have attribute data,
but no information on when they were recorded. I vote this is made optional
in data entry. I'm fine with keeping determiner as required because you can
always enter unknown - that's not an option for dates.
—
Reply to this email directly, view it on GitHub
<#4184 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBGNPV2QVCB6EFCUM2DWDAU3BANCNFSM5J2GAC7Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I just loaded some records earlier this week and was admonished for not including an attribute date - it is currently required. |
Interesting - I loaded some without a date with no rejection!
…On Fri, Oct 14, 2022 at 9:24 AM Teresa Mayfield-Meyer < ***@***.***> wrote:
* [EXTERNAL]*
I just loaded some records earlier this week and was admonished for not
including an attribute date - it is currently required.
—
Reply to this email directly, view it on GitHub
<#4184 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ7JBDU4Q4WUTMMQIZNJ5TWDF3MJANCNFSM5J2GAC7Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
HMMMMMM - I'll try again in a week or so and we'll see what happens. |
I don't think this needs further discussion. It would be lovely if we all had these dates, but we don't and we shouldn't be required to make up data. |
According to the Attribute Bulkloader at https://arctos.database.museum/tools/BulkloadAttributes.cfm?action=ld
![image](https://user-images.githubusercontent.com/14808196/145650469-a85f7074-bfff-4d4f-8b70-e5b53d572d80.png)
the attribute date and determiner are highly recommended but not required.
But users are getting errors in Data Entry if they leave the date field blank:
We need the option of leaving this blank for no data records. In this case the data may eventually be found, but at the moment all we know if that the record and the attribute were recorded sometime after 1995. If the actual value is 2007, putting 1995 as the value seems like it introduces confusion. Recommend we only require dates when they are know for everything except verbatim, begin and end dates, because the latter allow for recording the degree of uncertainty.
The text was updated successfully, but these errors were encountered: