Wishlist: Make Preferred Name variables easier to use
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Evergreen 3.2
The Preferred Name variables used in print templates and action triggers should return the preferred version of the name field, if one exists, otherwise the primary version of the name field should be returned.
Currently, when using the following variables in print templates and action triggers:
pref_prefix
pref_first_
pref_second_
pref_family_name
pref_suffix
if there is no value for the preferred name element, nothing is returned, so conditional code must be used to return the primary name if there is no preferred element. An example of conditional code that is needed for print list templates provided on the mailing list by John Amundson is:
<span ng-if="
<span ng-if="
<span ng-if="
<span ng-if="
Similarly, conditional code is also needed to make use of the preferred names in action trigger templates.
With this proposed change, configure print templates and action triggers would be much simpler.
Should there be a need for the patron's full legal name, the following would still provide those name elements:
prefix
first_given_name
second_given_name
family_name
suffix
Relevant IRC discussion:
http://
Relevant email thread:
https:/
tags: | added: printing receipt |
Changed in evergreen: | |
status: | New → Confirmed |
It would be really nice if this could be done via the IDL for consistency across many different uses, not just in print templates or triggers.