osem
osem copied to clipboard
openSUSE
real name/display name handling
I'm submitting a ..
- [ ] Bug Report
- [X ] Feature Request
Current behavior:
My apologies if this bug is too instance dependent (i.e. it's due to local configuration of the linux fest northwest site) and doesn't make sense to the team developing the product; since the site owners expressed that my request to have my name appear differently posed them some difficulty, I thought perhaps the limitation was in the software.
My profile lets me set a "Name" (annotated as my real full name) and a "Nickname" field (annotated as "how other users see you"). I am also a speaker, and it appears that the schedule-building function inherits and displays "Name". However, I don't use my legal name professionally, and I don't want my legal name to appear on the schedule -- but I also don't want to mislead the conference leaders as to my legal name; they may need my legal name for various official purposes -- ID checks, financial records, secure areas, etc.
This use case may apply to the following groups:
-- immigrants or overseas visitors, who have chosen a name that is easier for locals to pronounce (e.g. it's quite common for Chinese students in the US to choose a more American-sounding name to use) -- women, who face multiple competing norms and laws about their name after marriage -- transgender people, whose legal names may not match their identity
Expected correct behavior:
Lately I've noticed websites deal with this problem by offering a "Legal Name" and a "Display Name" function, with the "Legal Name" only visible to admins in reports and such, and "Display Name" used everywhere else.
Thank you for your consideration!
@kayleachampion thanks for your feedback.
From my point of view, there is just (Display) Name and Nick name. I don't think that having a Legal name in the application is needed. Why would Admins use this Legal name for? What is the problem of having just a Display Name?
I can think of a few reasons that admins might seek a legal name: -- they're making a list for checking people in and want to check the person's government-issued ID -- they need to supply a list of invitees to a security desk (which will in turn check ID) -- they will be issuing letters of invitation (my understanding is that this is useful for people trying to get institutional support or get visas)
@kayleachampion
they're making a list for checking people in and want to check the person's government-issued ID
Why don't they use tickets instead? I have never been asked for my ID in a conference... Is this a real case?
they need to supply a list of invitees to a security desk (which will in turn check ID)
is this a real case? are there conference checking IDs for security?
they will be issuing letters of invitation (my understanding is that this is useful for people trying to get institutional support or get visas)
but I don't think something like this is supported with OSEM, how do you know if someone needs a VISA?
@ddemaio @differentreality @hennevogel what do you think? do you see a use of case for storing a Legal Name?
In the specific case that inspired me to write in, yes, they are asking for my legal name for an ID check; and yes, I've been asked for my ID when checking in to conferences many times. I agree that the international travel example is speculative; it's an example of a situation where event organizers might need legal name.
Hello, I can affirm as a conference organizer that all of the cases mentioned do occur in the real world. There is often a requirement for legal identification, especially at events when alcohol is being served.
Also, I should mention that I personally do not go by my government issued name and have on occasion encountered issues related to it at conferences.
@bear454 figure you might want to take a look at this as well.
I do see the real scenarios behind the examples mentioned above.
The real question is: Which part of those examples does OSEM relate to? So that we can determine if it makes sense for OSEM to include that option (for legal name).
Registration would be one place - based on who is registered (speaker or not), organizers can grant extra access.
@altsalt thx - yes Kaylea raised this with me first. LinuxFest Northwest runs parties, for which registered attendees are invited. Washington State Liquor Control Board insists we provide a list of legal names of party attendees, we have no intention of sharing this publicly.
WRT to ticketing, we don't use tickets for registration (it's redundant to require both (a) registration, and (b) a registration ticket, but that's a bigger issue. A PR enabling this was option was merged in months ago), but I don't see how tickets fix anything here.
This issue is fairly simple; all the schedules should use the nickname field instead of the name field for speakers, and both the nickname field, and the proposal submission form should make this clear.
I would make the change, but at this point in the LFNW cycle, I really don't have time for extra code, and I'm kicking myself for even typing this much on this bugreport. The reporter was kind enough to work around it by basically dis-inviting herself from the free beer at our parties (and when I see her, I'll be sure to rectify any shortcoming ;-)
I've started on this:
https://gitlab.com/lfnw/osem/commit/0b8dffd340c4aca394741140be098d1b13157c36
It's going to need a bit more cleanup, and I won't be able to guarantee that until after LNFW 2019. Right now I just don't have enough time to make it right. 6 weeks left to make 2K conference attendees, speakers, and sponsors happy.
@bear454 no problem. :smile: Maybe someone else has time to finish in the meanwhile. If not you can send the PR when you have time. Good luck with the conference :wink: