11–20 of 38 posts
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
The gender _might_ be used to ensure diverse speaker selection.
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
- It doesn't apply for many cultures.
- The only justification to collect them separately is to link with third-party data.
- They should stop playing around and just ask me what they want to know, "How would you like to be addressed?"
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
Other uses have been to suggest shared sleeping arrangements.
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
The "first name, last name" fields are worse, IMO. - It doesn't apply for many cultures. - The only justification to collect them separately is to link with third-party data. - They should stop playing around and just ask me what they want to know, "How would you like to be addressed?"
The software needs to have a database layout that supports the superset of what all individual users need.
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
The gender field was added for FrosCon. They used it to select what kind of t-shirt you want. Other uses have been to suggest shared sleeping arrangements.
Then it's incomplete without a "shirt_size" column.
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
Some conferences are in locations with restricted accommodation facilities, and if you don’t specify a roommate, you are paired with someone of your gender. So that’s why the gender might be needed. As far as the preferred pronouns are concerned, I see them as something with heavy political connotations. No one who is not hard left believes in the necessity of the xir pronoun, and of course there are trans people als…
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
The "first name, last name" fields are worse, IMO. - It doesn't apply for many cultures. - The only justification to collect them separately is to link with third-party data. - They should stop playing around and just ask me what they want to know, "How would you like to be addressed?"
Anyone reviewed how it compares to indico or eventbirght?
Or easy chair: https://www.easychair.org/
From Frab's schema.rb: create_table "people", force: :cascade do |t| # ... t.string "first_name", limit: 255, default: "" t.string "last_name", limit: 255, default: "" t.string "gender", limit: 255 # ... end Our schema has a similar table, but with "prefix" instead of "gender", where on the front end a list pops down with Mr., Ms., etc. We just use the prefix to form the full name. I wonder where the need to track ge…
The "first name, last name" fields are worse, IMO. - It doesn't apply for many cultures. - The only justification to collect them separately is to link with third-party data. - They should stop playing around and just ask me what they want to know, "How would you like to be addressed?"
I'm struggling to come up with a list of those.
Middle names are definitely not universal, sure, but I can't seem to find a list of cultures that can't map down to "first name, last name".
Iceland, Indonesia, Turkey, Ethiopia, everything I've come across seems to have adopted some superset of "first name, last name" in the last hundred years.
> The only justification to collect them separately is to link with third-party data.
In Japan, many organizations are required to collect this for legal compliance.
> They should stop playing around and just ask me what they want to know, "How would you like to be addressed?"
That is a good thing to ask -- and certainly suitable for generating nametags! -- but I can still see many cases for needing to have a legal name. Generating receipts, etc.