-
-
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
report update questions - MVZ Bird Narrow box label #8363
Comments
The basic need here (ie most relevant) is the original number which is either getting the identifier type of collector or preparator. So a function makes sense! But I think it can be a single one that checks for collector and preparator nums. There are infrequent occasions where there are both. |
Yea, always, and I always struggle there - does a label always have to consider and print every possibility supported by the data structure (in which case we'll all go crazy failing to meet that goal...) or can some simpler pull intended just for a specific use case work well enough? I suppose it's taken me way too long to get there, but I'm becoming a dedicated fan of well-documented instances of the latter. And on that note, how's https://github.com/ArctosDB/PG_DDL/blob/master/function/label_print/get_original_identifier.sql look? Example data:
|
I'm following this thread. I noticed above someone wrote that "where a PLC identifier exists, the preparator number should be listed in the collector slot". PLC numbers are not preparator numbers, they are identifiers issued by the MVZ PLC. |
@cjconroy an example record and the desired 'original_identifier' from it would be useful so that I can tune the function to get that. (Or tell me where I got lost, I don't really understand this complexity and might be completely on the wrong track...) |
I'll let the bird folks respond about bird labels. I just sent an email to the mammal curators to see what their preference is regarding names and numbers. We used to use parentheses around preparator names and numbers, but we also included both names when we did labels by hand. I doubt there is going to be room for all that. |
https://arctos.database.museum/Reports/reporter.cfm?action=edit&report_id=180
@mkoo this report pulls "collectornumber" as a cascade of 'if exist then else ...', and then separately "collector_number_issued_by" and "preparator_number_issued_by", with the comment
Please confirm that these are somehow separate and can't be merged with one function
If I understand the situation, I will experiment with 2 functions
The text was updated successfully, but these errors were encountered: