Skip to content
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

Add support for suffixes and/or display name on Person content type #2924

Closed
joeparsons opened this issue Nov 14, 2023 · 0 comments · Fixed by #3739
Closed

Add support for suffixes and/or display name on Person content type #2924

joeparsons opened this issue Nov 14, 2023 · 0 comments · Fixed by #3739
Assignees
Labels
enhancement New feature or request

Comments

@joeparsons
Copy link
Member

joeparsons commented Nov 14, 2023

Motivation

The AZ Person content type included in Quickstart does not provide a way to add suffixes to people.

Is your feature request related to a problem? Please describe.

Because no suffix field exists, content editors and site builders end up adding suffix information to their people in inconsistent ways:

  • Including suffixes in the Last Name field
  • Adding additional field(s) to the Person content type, e.g. suffix or display name
  • Probably other ways as well

Proposed Resolution

Describe the solution you'd like

We should consider either:

Adding a suffix field to the AZ Person content type

  • This field would be designed to only contain suffix values (e.g. MD, PhD)
  • Would require updating existing field display settings (display modes) to include the suffix field
  • Would also require updating any views using fields to also include the suffix field
  • Would probably require concatenating First Name, Last Name and suffix values with commas where appropriate
  • This would be a more structured data oriented approach but might not meet the needs of various site requirements as easily

Or

Adding a "display name" field to the AZ Person content type

  • This field would be designed to contain a full name + suffixes (e.g. Jane L. Doe, MD, PhD)
  • Would require updating existing field display settings (display modes) to replace first and last name with display name
  • Would also require updating any views using fields to replace first and last name with display name
  • Would probably have to be a required field
  • Would result in duplication of name in first name, last name, and display name fields
  • This approach is definitely less structured data oriented and requires duplication of name values but may ultimately be more flexible to accomodate different site requirements, e.g. this field would also make it possible to include a middle initial even though we don't have a middle initial / middle name field
@joeparsons joeparsons added the enhancement New feature or request label Nov 14, 2023
@trackleft trackleft self-assigned this Sep 20, 2024
trackleft added a commit that referenced this issue Sep 23, 2024
@trackleft trackleft linked a pull request Sep 24, 2024 that will close this issue
32 tasks
trackleft added a commit that referenced this issue Sep 26, 2024
trackleft added a commit that referenced this issue Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants