Add option to use patron's preferred name in notices
Currently LX Starter uses the "n" field in Sierra to pull patron first name. Some patrons want to be addressed by their preferred name, not their legal name. Our library would like to offer this more personalized experience, so it would be good if there were a choice in which merge tag LX Starter uses for names.
Maria Laude
shared this idea
-
Adminashleybarey
(VP, Innovative)
commented
For MEEP voting for 2027:
Current State
Users set up the LX Starter templates and it pulls the Patron First name from the ‘n’ field or their legal first name.
Libraries would like a choice around which merge tag to use so that that they can use ‘preferred’ name if they would like.Functional Workflow
As a user, when I create or update templates in LX Starter I would like to be able to select separate merge tags for Patron’s preferred or legal name; when connected to either Sierra or Polaris.In the event the preferred name is not available template will default to ‘LegalFullName’ or the ‘n’ field.
Result
Patron receives a notice where they can see their ‘preferred name’. -
Emma Olmstead-Rumsey
commented
Interesting! In Polaris, it pulls from preferred name, NOT legal name. Very weird that it's opposite for the two ILSes.
-
Mieko Fujiura-Landers
commented
Our libraires use the Polaris patron record 'Use Single Name Field' setting for institutional records (schools, businesses, ILL lending) and patrons with mononyms. The Single Name currently maps to the LX Starter last name merge tag. Libraries generally just use the First Name merge tag in notices, so no name appears in notices for patrons that use Single Name Only. It would be really helpful if there was a way for these names to map to the First Name merge tag!