Patty has created a story for this feature
How will preferred names be entered into FOLIO? Under what circumstances would a preferred name be used?
Would the group prefer first name only? Something that can be manually typed in? Is a token needed (conditional if present)?
Requirement: if a preferred name is present, use as the "First Name" token.
Demonstration of token use in notice templates
Honorifics, name suffixes also need tokens
Would this field be protected from being overwritten by a feed from an identity provider?
This would be a poor use of a custom field
Tie in to patron empowerment?
There may be a need to store both a legal name and a preferred first name
Display name string versus first name/last name/preferred name data elements?
Example needed of this kind of field in a different system
UICIRC-162 Add the preferred name token to the list of patron notice tokens
Logic (if...else) statements needed in notice templates in order to select appropriate name token (preferred name vs. first name); ability to use a conditional block (basic "looping" functionality already supported)
Alternative: construct "display name" in patron record based on preferred first name/first name presence and last name; protected field; create "display name" token for notice templates
Need preferred first name element from data load before "display name" calculation (possibly including honorifics)
Different libraries might want to construct these display names differently ("Preferred first name + last name" or "Honorific + Preferred first name + Middle initial + Last name + Suffixes")
Construction of a display name might need to be different based on the use case (different types of display names)
Should preferred names be searchable?
Use of non-standard characters (varchar? strings, non-ASCII, spaces, etc)
Patty will make necessary edits to UIU-1649 for review