The fault in our names – Share your story

I had the opportunity to visit the Burke Museum of Natural History and Culture at Seattle, Washington. I was greeted by a pair of (portraited) open arms of Chief Si’ahl, the most famous dxʷdəwʔabš chief, whose name was anglicised to – as we now know – Seattle.

Picture of the description text for Chief Si’ahl’s portrait.

I can’t help but think about how Chief Si’ahl’s name would most likely be represented in many different ways in a modern data system. For example, Si’ahl already is a compromised ASC-II representation of his name in his original Lushootseed writing, where non-alphabetical characters are simply not accepted. Even in the anglicised form, his name may be recorded quite differently at different places, namely “Sealth” or “Seattle”. This meant that linkage based on his name would be more difficult than others.

Burke Museum gave me another example of situations when people’s naming systems differ from the Western Forename-Surname structure, they are sometimes forced to conform. Chief Jonathan “Whonnock” (anglicised)’s name is structured as such.

You would be mistaken to think these questionable treatments of names is a thing of the past! I was updating my UCL profile recently, and UCL gave this lovely advice – no names containing punctuation, diacritics, special or non-Latin characters, or names that are too long.

This may be innocent and non-consequential for file names – but you won’t say for people’s names. What truly hurts about “being called names” is about being called names that one does not identify. We live in a culture that claim to respect diversity, but has yet to truly reflect on their practices, in terms of data system design. In terms of data linkage, where names are often used to help identify if multiple records belong to the same person, we have long-established inequalities by racial-ethnic groups – where people from White British groups are most well linked, represented, and included in research. I have written about the technical side of this argument in my own academic work – hopefully out soon (waiting for Arxiv…)!

The Fault in our Names – share your stories.

We need to tell our stories to drive change. I have started a page here to invite your submission to collective tell our story – how our names are misrepresented in data systems, and it’s direct impact on our lives. I hope this will create an archive of our stories, and bring them to light.

One day, our names, all names, will be treated with respect.

Week 1: The Beginning

First week of PhD, thoughts on Remote Start. Software Nightmare. and Academic Career Progression

“Welcome to UCL” – 10 online induction courses (no kidding!) but I doubt I’d remembered a lot from them. Possible true that it is to leave a gist, an impression of what the college values: fire safety, implicit bias, data security… All is well! Changing jobs are never simple, and doing this in a remote-working era makes it … a bit weird? But I presume it is something for all of us to get used to.

The plus side of everything going online is that, I get to attend A SWARM of online talks, seminars and groups. It does feel a bit overwhelming to start – my schedule is quickly populated with scheduled meetings and invitations, there are always this prominent speaker coming, that core training one cannot miss – can’t help but wonder – will I ever attain this wisdom to determine which talks are the truly good ones I should listen? Would be a thing to reflect perhaps a few weeks down the line..!

A Virtual Office (Unsplash)
Office. Photo by Laura Davidson on Unsplash

Software Nightmare

The excitement of starting at a new post was quickly overtaken by the frustration of – you guessed it – installing the relevant applications and softwares on my laptop! Numerous emails, calls and remote access sessions but still not able to get all I need. There must be more flexible ways for colleges to adapt to this fast-changing landscape of software development! Take Python as an example, the only version that is easily installable via college software centre is version 3.6.4, which failed to satisfy a lot of the dependencies of many recently developed softwares. Guess it is always this tug of war between data system safety & integrity vs freedom & flexibility…! Hope they all get sorted next week!

Imagining an Inclusive Academia

UCL provides a clear guidance on career progression – the Academic Career Framework (see below) – with a comprehensive list of things one is expected to achieve at UCL Grade 7 and above. This is something I have never heard of! It provides a substantive structure into what is needed to progress at UCL, in other words, things that are (currently) valued by the college.

4 Components of the Academic Career Framework (UCL)

It is said that contributions to all 4 categories is necessary to measure one’s achievement. I appreciate the attempt to provide clarity on progression, and I can see a wider potential of these frameworks to revolutionise academics’ roles in society – As Dr. Nadia Islam rightly put, a community-focused collaborative role needs to be more heavily emphasised in academic research. This would be a part of a change I would like to see, and contribute to in academia in near future!

I think this pretty much wraps up week 1 – excited to continue to embark on this journey, and hope that you will be adjourning with me 🙂