Thread:Shabook/@comment-10473115-20160327104119/@comment-16461120-20160328205028

I agree that this is largely a problem created by the character template having been broken for months with no one aware of how to fix it.

One bug displayed the entire page name if you didn't use the title field, yet another bug removed autogeneration of some categories when you added the title; furthermore, there were also issues with which fields did or didn't autogenerate links, so many users circumvented the problems by manually adding both the categories and the fields or used functioning fields in place of the proper fields to get entries to actually display.

This was obviously only a temporary fix, but now those complications appear to be at least momentarily resolved on a modified version of the rolled back template; however, the resolution has generated its own set of dilemmas, as now many fields which were automatically linked instead require brackets, the month's of bug circumvention activities need to be corrected, etc., with multiple suggestions of different solutions on how best to handle that.

Anyway, if we want users to add title fields instead of depend upon the current alias field to create a header linked to the disambiguation, then everybody on staff needs to be on the same page there, so as not to confuse the users, 'cause I see them as often redundant and oft blank them for that reason.

In terms of this specific example, I'd agree that full first names probably belong in the title field, since they're technically not aliases, though can certainly understand the notion that the current alias field is convenient and likely used many times throughout the database as a viable substitute.