names

names extending

The simple ways to manage a names database

This is one of those instances (like fully accessible design) that businesses have to let go of some things that they've prioritized and built entire machines around.

names extending

Why building out the full name pattern is the exception

names info design

Names taxonomy

I spent weeks, probably hundreds of hours, researching names, trying to find different patterns and different taxonomies before finding W3C and Wikipedia examples like Akan names, Indian names, and African-American names.

names info design

Data myths in names

Part of the 26 cultures researched, as noted in Names taxonomy.

names info design

Multiple potential starting points

So, we’ve acknowledged that the current construct is US-centric, and the US has patterns of cultural fuckuperry.

names info design

Mixed governance names data

Legacy Our legacy standard is first_name:text, which we’re already shifting conceptually to given:text. In the legacy construct, the field name – e.g., first_name or given – is the category.

names info design

Mixed governance names UI

Legacy Our legacy standard for interfaces between governed and ungoverned data fields is pretty strict. Text field goes to ungoverned data. Dropdowns, checkboxes, radios, toggles go to governed data.

names info design

Allowing for multiple names

Understanding the name structure doesn't mean we now know all the ways to refer to them based on context, (presumed) relationship, legal form, etc. Broaden the cultural context enough, and even the legal name shifts in expectation.

names logic

Logic shifts: internal chunking

The reality is that the current structure (first/last) works in the population in which it works. We don’t have to start from scratch, we just have to be more realistic about the full complexity.

names logic

Big-picture logic shifts

The names pattern can look intimidating. There are lots of details involved, with complex structures and behaviors, and it's shifting something so prevalent that it can feel like you've stepped outside of the known information universe. Take a deep breath, it's not that bad.

names logic

More nimble logic: JSON

JSON data can use governed data, constraining both the available categories and potential entries.

names logic

Logic shift: factor in construction context

Part of what likely contributes to keeping names “simpler” is that we have to fill them in everywhere. It’s extra work for developers, extra work for systems architects and information architects, UX’ers, content managers, marketing. It's an administrative burden for users.