Here are a couple of working branches that add the preferred data in two ways to wide_hold_data
First - use the preferred data by default. user/stompro/lp1968750_wide_holds_preferred_name_fields_default https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1968750_wide_holds_preferred_name_fields_default
Second - Add in a set of fields for the preferred name data. user/stompro/lp1968750_wide_holds_preferred_name_fields_duplicated https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1968750_wide_holds_preferred_name_fields_duplicated
I prefer the first one, since it is simpler, but maybe someone needs to access the non-preferred name fields in the pull list and hold shelf?
I think either one would solve is issue of not being able to access preferred name fields in the hold shelf list print template.
Here are a couple of working branches that add the preferred data in two ways to wide_hold_data
First - use the preferred data by default. lp1968750_ wide_holds_ preferred_ name_fields_ default /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ stompro/ lp1968750_ wide_holds_ preferred_ name_fields_ default
user/stompro/
https:/
Second - Add in a set of fields for the preferred name data. lp1968750_ wide_holds_ preferred_ name_fields_ duplicated /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ stompro/ lp1968750_ wide_holds_ preferred_ name_fields_ duplicated
user/stompro/
https:/
I prefer the first one, since it is simpler, but maybe someone needs to access the non-preferred name fields in the pull list and hold shelf?
I think either one would solve is issue of not being able to access preferred name fields in the hold shelf list print template.