July 2016

The Making of an Entry: from Submission to Publication

As at this writing, there are 3,629 published name entries in the dictionary.

Screenshot (85)At the rate of about twenty new entries per day, we could reach a year’s goal of 10,000 entries in no time. In this post, I would like to show you how a submission from the homepage becomes an indexed entry in the dictionary. There will be lots of pictures to illustrate the process.

The homepage is at YorubaName.com where hundreds of users have submitted their names into the dictionary since we launched the public page in February 2016.

Screenshot (86)

So, what happens when an entry is submitted?

On the lexicography dashboard, I see a list of names suggested by the public, or by other in-house lexicographers. As you can see in the image below, the email of the submitter is listed.

Screenshot (62)I have blurred an email address to protect the person’s privacy. In the future, we will have a login name instead of an email address.

To begin editing, I click on whatever name I would like to work on. In this case, I give preference to the publicly submitted name over the in-house ones. The name is “oderinde“.

In the edit mode, the name is expanded and I can see all that the submitter put in his/her submission. In most cases, as in this example, the submitter hasn’t been able to find the exact spelling of the name so some editing will be needed.Screenshot (63)

I begin first with capitalisation. I change the first letter from “o” to “Ọ”

Screenshot (65)

The submitter seems to have an idea of the meaning so I move further down to the syllable breakdown. This functionality is meant to be used to train our text-to-speech system to know how to render Yorùbá names. The functionality isn’t yet live, but the field is compulsory, so I complete it, rendering the name syllable by syllable.

Screenshot (66)By now, I’ve completed the three required fields. So, to prevent my work from being lost, I scroll down and save the entry.

Screenshot (67)

I get a notification on the top right corner.

Screenshot (68)Sometimes I return to the “meaning” box to modify what the submitter wrote.

Screenshot (69)

Then I move to the “morphology” field to break down the name according to its smallest meaningful units (the linguistic term is morpheme). This is usually the most exciting part for me, because that is where the names usually unravel.

Screenshot (70)

The morphology and the gloss fields are usually written in small letters, but their meanings can include capital letters in the case of proper nouns.

Screenshot (71)

Sometimes there is more than one meaning of a morpheme, so I supply them, and then save.

Screenshot (72)I save at this stage by just hitting “enter”.

The geolocation field is one of our most cherished features, designed to be able to map certain names across the country. The user has chosen “Abẹ́òkuta” as the location of this name. But because I know that it is a name that is borne in other different parts of Yorùbáland, I add another location indicator: “General”.

Screenshot (73)

At this point, I get an epiphany as to a better way to express the meaning of this name that is not too literal as to render it risible.

Screenshot (74)

So I edit it again. This time I’m satisfied.

Screenshot (75)

Finally, to see if there are notable people with this name, I turn to Google, which never fails.

Screenshot (76)

I get many hits, but I am biased to the topmost one.

Screenshot (77)

I sometimes also go to the “news” tab, since notability might also reflect in the newsmaking ability of the bearer.

Screenshot (78)

In the end, I settle for the topmost hit on Google. For now, at least, until another user goes to the entry and upbraids us for overlooking another famous name.

Screenshot (79)

I add the link as well.

Screenshot (81)

Then save.

Screenshot (82)

Finally, I publish the entry.

Screenshot (83)

Ọdẹ́rìndé is now in our dictionary!

Screenshot (87)

 

The end.

————-

Addendum

Shortly after this post was drafted for review, Laila drew my attention to an interesting phonological feature in this particular name which I’d not paid attention to in my earlier work: there is an extra /ẹ/ in “Ọdẹ́rìndé” which I hadn’t accounted for before. As it often happens with incomplete entries, I simply returned to the name and edited as necessary.

Screenshot (95)

I also left a short note in the relevant box about the phonological behaviour of certain tones like this in contiguous environment. In a layman’s language, a grammatical morpheme in this word took on the feature of a neighbouring vowel resulting in an extra tone mark where there otherwise isn’t any.

Screenshot (98)

Fascinating linguist’s stuff.

————-

If you’d like to join our lexicography department to help speed up the meeting of our 10,000 names goal, send an email to project@yorubaname.com with “Lexicographer Volunteer” in the subject field.

What Do Lexicographers Do at YorubaName?

If you’re reading this, chances are you have either signed up to be a lexicographer on the YorubaName project or you’re considering joining the ranks of our volunteer lexicography team. If so, chances are also that you have a general idea about what lexicography means. Still I’ll say, to save time for those who don’t, that our work in this department has to do with annotating, tone-marking, providing and researching meaning, researching name geo-locations, and generally being the last line of defense before a name entry is published.

So, thank you for your interest.

This job is quite important. First, if you are a volunteer lexicographer, you have do one thing first. Go, right now, and install our free tone-marking software on your computer. You will be needing it for your work.

In this post, I will try to clarify much of what the lexicographer’s job entails, with illustrations and texts. I’ll give you a feel of the dashboard which I’ll assume, for now, that you haven’t yet had a chance to work with. This would be an introduction to all the features in the back end open to you as a lexicographer, so you can make sure that an entry is good to go before it is published.

Types of Lexicographers

Currently, we have two privilege levels for all lexicographers. There is a Basic Lexicographer and Professional Lexicographer. Both have very important and complementary roles. Both roles are also subjected to the privileges of the head lexicographer who has a slightly higher privilege than both.

The Basic Lexicographer is a new lexicographer whom we have not yet tested, but who is willing and able to work. The “basic” tag says nothing of their ability beyond the fact that we have not yet been able to assess their capabilities. Most Basic Lexicographers will eventually graduate and be given Pro Lexicographer status if their work convinces us of their lexicographic capability and their ability to deliver excellent work without supervision.

Duties and Privileges of the Basic Lexicographer

  • Add new names to the dashboard: This can be done through the homepage, like every other user, or through a personal dashboard account which, as a lexicographer, you will already have. The names you add will not be immediately published, but they will be saved in a place where someone with the Pro privilege can check and approve them.
  • Modify names already in the dashboard: You will have access to the dashboard to see all the names already indexed in the dictionary. You will be able to open and edit any one of them, especially those that are not complete, or those with meanings that could be better defined. These changes, again, will not go live immediately, unless approved by someone with the Pro privilege.
  • Accept names suggested by users: As a basic lexicographer, you will be able to see all the names suggested by our users. Some of them are legitimate Yorùbá names we don’t yet have in the dictionary while some are names that are not Yorùbá at all but sent in as a prank or by mistake. It will be your role to know which to accept and which to reject. You will have the privilege to do both.
  • Sort out feedback messages: As a basic lexicographer, you will be able to see all the feedbacks given to any name entry through the “improve this entry” button on the homepage. You will be able to accept or delete these feedbacks, and/or incorporate them into the name entry as necessary.
  • You will not be able to delete any name in the database. Neither will you be able to make a final publishing decision on your edits. These will go through a second layer of approval before they go live.

Duties and Privileges of the Professional Lexicographer

  • You will be able to do everything the Basic Lexicographer can do.
  • You will have the power to publish these names directly without further approval, which makes your role very important.
  • You will also be able to approve/reject changes made by lexicographers with the Basic privilege.
  • One of your key roles will be to collaborate with those with Basic privileges, suggesting corrections and improvements to their work, and recommending any notable Basic Lexicographer for upgrade to Pro status. 
  • You will also coordinate with the head lexicographer whenever necessary and in making certain decisions that may affect the running of the dictionary.

Welcome to the Dashboard

When you’ve been accepted as a lexicographer for YorùbáName.com, you will get a username and password with which you will be able to login to the dashboard.

When that happens, you will see the log-in page like this:

Screenshot (33)

And when you get in, you will see the dashboard itself which looks like this:

Screenshot (34)

The red box tells you how many names we have in total. The green one says how many have been published/indexed and are available to the public. The blue one shows how many have been suggested/added by the public but haven’t been worked on at all while the yellow/orange box shows the names that are currently being worked on but haven’t been published.

Further down, you can see names recently added and published. But more importantly, you can see the feedback by the public and the date the feedbacks were made. As a lexicographer, you will have access to all these features and will be able to click on them and make changes as necessary.

The “Find Entry” search box also allows you to search for any name in the database. This is especially useful if you’ve come into the database specifically to work on a name that has just popped into your head.

Searching for it here will take you directly to that name, where you can begin to work on it.

This is a name edit mode:

Screenshot (35)

At the bottom of each page in the edit mode – depending on your lexicographer privilege – you will find the button to either save your work, publish your work, or delete the entry.

Screenshot (36)

As you will see, not all the fields are compulsory/required, which means that a name entry can be declared “complete” with just a few compulsory fields filled out. It is our aim, going forward, that each name entry should have a certain threshold to be considered complete,  giving the user a rich linguistic, cultural (and perhaps onomastic) experience on every single entry of the dictionary.

Working Offline

Lexicographers of both Basic and Pro privileges will be able to add names into the dictionary via an offline spreadsheet which can be downloaded from within the dashboard. What this means is that even if you don’t have regular access to the internet, you can download this spreadsheet where you can enter all the names you gather. And when you finally get online, you will be able to upload all the names at once.

But even if you are not adding any names to the dashboard, you can take on the role of the lexicographer that regularly monitors entries without complete fields (e.g. an entry without a complete or verifiable meaning, or an entry without proper tone-marking, etc) and then goes to friends, researchers, or people bearing these names on social media in order to verify the correct spelling, meaning, or tone-marking on their names. Your work is equally as important.

We are also looking to involve scholars affiliated to higher education institutions, professors whose students could directed towards this purpose, or private researchers all around the world, who have time on their hands to visit local Yorùbá villages in order to help improve the geo-location for all the names we currently have. There may yet be other ways to further our lexicography work besides what we’ve articulated here: let us know what you have in mind.

There are a few other lexicographer roles that don’t deal with the dashboard at all. These may also interest you: helping to generate name-related quizzes for our social media accounts, looking out for rare names in the dictionary for highlighting on random days on our social media pages, or helping to come up with interactive ideas from the dictionary that can engage our multimedia audience. This might be best for those who might not have too much time on their hands but still want to help out in some way.

Conclusion

As this is just an introduction, I hope I have given you a broad idea of what to expect. As a lexicographer, you will be joining an active group of people who find names and words fascinating enough to spend hours of their daily time with. We welcome you with open arms and hope that, more than anything, you find the experience as entertaining and educative as you find it challenging and enlightening.

 

If you are just deciding to join us in Lexicography, send us an email at volunteer@yorubaname.com with “Volunteering for Lexicography” in the subject line.

Contribution Guidelines for YorubaName Codebase

This post provides bite-sized information that should help with the onboarding process for anyone who wants to contribute to the YorubaName dictionary project.

The skills needed to work on the YorubaName codebase are quite varied. This makes it possible for a diverse set of people with a wide range of technical skills to be able to join in the project: from developers/designers, UI/UX experts, to enthusiastic users and language lovers. This post provides the basic steps for all these types of people to get started.

Want to Contribute? Where to start?

Getting involved in the project is super easy.

Your first action point is to read the General Information README. It contains project-wide information that should be known to anyone working with the YorubaName codebase. Reading this would help provide clarity regarding the lay of the land and how different aspects of the codebase fit together.

The rest of the post explores the more specific guidelines.

Contributing as a developer to the Dashboard Application

The Dashboard application is a stand alone JavaScript application built with AngularJS. So if you are a JavaScript developer with some AngularJs chops, then this is where you may want to start:

  1. Clone and/or Fork the Dashboard application at https://github.com/Yorubaname/yorubaname-dashboard
  2. To understand how to run the application, go through the README at https://github.com/Yorubaname/yorubaname-dashboard/blob/master/README.md
  3. Ready to start coding? Then check the issue tracker at https://github.com/Yorubaname/yorubaname-dashboard/issues for a list of things you can start working on right away. Feel free to ask questions regarding the issues you are interested in working on in the issue tracker.
  4. If you have any questions regarding the project or the code base, feel free to drop by our gitter room at https://gitter.im/yorubaname-dictionary/dev, we would be eager answer your questions.

Contributing as a developer to the Core Website Application

The core of the dictionary and the website are written in Java using Spring boot. ElasticSearch is also used to power the search. So if you are comfortable with programming in Java and its ecosystem (or maybe you want to learn some more), this is where to start:

  1. Clone and/or Fork the Website application at https://github.com/Yorubaname/yorubaname-website
  2. To understand how to run the application, go through the README at https://github.com/Yorubaname/yorubaname-website/blob/master/README.md
  3. Ready to start coding? Then check the issue tracker at https://github.com/Yorubaname/yorubaname-website/issues for list of things you can start working on. Feel free to ask questions regarding the issues you are interested in working on in the issue tracker.
  4. If you have any questions regarding the project or the code base, feel free to drop by our gitter room at https://gitter.im/yorubaname-dictionary/dev, we would be eager answer your questions.

Contributing as a UX/UI designer

With the codebase of applications now on GitHub, someone with UX/UI experience can also easily see how the site is built and contribute in improving the user experience of the application. As a UX/UI expert the following steps should help in getting started:

  1. Read the general Information README here https://github.com/Yorubaname/general-information
  2. Explore the dictionary at http://www.yorubaname.com, and if you have any UI/UX suggestions then create an issue at https://github.com/Yorubaname/yorubaname-website/issues explaining the UX/UI improvements you have to suggest. Make sure to tag the issue with the UI/UX label.
  3. …OR: Peruse open issues with the UI/UX label in the Website Issue Tracker and Dashboard Issue Tracker and join in the conversation.

Contributing as a SEO expert

If you have expertise around SEO optimisation, then your ideas are also welcome. You are free to take a peek into the code base, and contribute your ideas on how to improve the SEO. You can either:

  1. Go to the GitHub issue tracker for the respective repository, and add issues explaining the changes you would suggest that would improve the SEO
    or
  2. If you know your way around code, clone and/or fork the codebase and create pull requests around SEO improvements.

Even if you are not a developer/designer/UI/UX expert, you can still contribute! The beauty of moving the development of the dictionary to GitHub is that it allows users to easily help shape the features that are built into the dictionary.

Contributing as a User

The codebase is not the only thing that is now on GitHub: our issue trackers, available in the form of the GitHub issues, can be found in the repositories. This is where we collect all bugs and feature requests that will be built into the dictionary. So if you encounter any bug or have any idea on how to improve the dictionary at www.yorubaname.com, then:

  1. Go to the GitHub issue tracker for the Website and the Dashboard, and add issues explaining the feature you want to see added to the dictionary. The developers will do their very best in building it.

So there you have it! Hopefully the information outlined should help make the process of getting started a lot easier.

Webinar for developers

If you’re still not quite sure, do not despair… To further aid people who would like to contribute to the project we are putting together a webinar on the 23rd of July targeted specifically towards developers where I will be:

  1. explaining how the different parts of the application fit together,
  2. how to setup the application on a local machine,
  3. how to get started writing code and contributing.

More details regarding the webinar can be found here. Register for free using this Google Form.

You should also connect with us on our social media channels: on Facebook here and on Twitter here.

Yorùbá Name on the road: University of Ibadan

On 1st July, Kọ́lá Túbọ̀sún and I were invited by IFRA Nigeria to present the Yorùbá Name project at the University of Ibadan. As I’ve been contributing remotely from Nairobi and other places, I could never have imagined how warm the response from both students and professors would be. It’s one thing to be told that people at UI are taking the project to heart, it’s another to sit in front of a room full of knowledgeable, passionate Yorùbá speakers loudly debating the breakdown of the name Sójìmí. If this is what linguistic research allied to technology can do, I definitely want more of it!

Beyond the heart-warming feeling of speaking to an enthusiastic audience, our trip to Ibadan was a great opportunity to establish links with a dynamic university community, and UI didn’t disappoint in this regard. We left convinced more than ever that the geolocation of names is going to be of crucial importance to establish patterns, due to the dialectal distribution of the Yoruba language. This was illustrated in particular by a couple of names from Ondo State that had previously eluded the Yoruba Name community, yet were well-known to some participants from this area, who could explain their meaning and origin. This observation certainly highlights the need for finer research into local naming practises in the various regions where Yorùbá is spoken.

One underlying current behind all the questions and comments that kept us engaged until time ran out, was how personal the project felt to participants. Some worried about how ‘funkifying’ one’s name could affect the course one’s destiny as inscribed in the name given at birth, while others recalled the long road they had taken to understand the meaning of their names and it seemed that all had a sense of how meaningful a name can be.

After hearing a few personal accounts of how a person’s name came to be, I have become increasingly interested in listening to more such stories, because meaning is never univocal. Instead, it is found in carefully peeling back the layers to gradually expand the perspective: first the combination of words that form the name, then the deeper signification of this utterance in a particular context. And there is more. In there is the back story of a person’s birth which is a family history, ensconced in a vaster community of memory. A website such as this one can never capture all these family histories criss-crossing the bigger canvas of History, but it can probably do a little to help those looking for a clue.

I left Drapers Hall with a renewed desire to continue devoting time to this project, to follow these threads of meaning across language and time and to keep on learning from all the people I meet along the way.

The full report of the Drapers Hall event can be found here on the IFRA website.