Alias Collisions

MaxSupernova · 07:35 PM

When I create a topic for "Bolo the Hutt", I also create an alias "Bolo" because I want to have links appear even when I don't list his full name.

Now, when I enter "Bolo the Hutt" in another topic, I get a collision warning because both "Bolo" and "Bolo the Hutt" are possible links.

However, it's a nonsensical collision because one is just a link to the other.

It's a bit of a strange thing to deal with (which words do I want to be a link?) but some logic that determines if both elements in the collision are the same topic (via aliases) and just links the main topic rather than the alias (or the longer of the two or whatever) would be helpful.

I understand that if "Bob" and "Bob Smith" are two separate topics then the collision alerts is necessary, but when they are aliases of the same topic then it's far less relevant.

Does this make sense?

Not a critical improvement, just an annoyance that I ran into.

Parody · 08:39 PM

A possible difference is if you pick "Bolo", the engine might continue and offer "Hutt" as a link to the Hutt race entry. Compare to Paranoia where "Mutant Power" is something characters have and "Power" is the stat you roll for using one. Maybe not the best examples, but it's something you have to allow for.

Farling · May 1st, 2014, 11:57 PM

Warning about those conflicts are fine, Parody, but when the only conflicts are to the SAME topic, then it shouldn't really indicate a conflict (and always take the longest of the available options).

Zaphod Beebledoc · May 2nd, 2014, 12:11 AM

Quote:

Originally Posted by MaxSupernova

Does this make sense?

Perfect sense!

Quote:

Originally Posted by Farling

Warning about those conflicts are fine, Parody, but when the only conflicts are to the SAME topic, then it shouldn't really indicate a conflict (and always take the longest of the available options).

I concur.

rob · May 2nd, 2014, 02:47 AM

This has already been identified as a bug that we'll be fixing in an upcoming release. So there's no further need to +1 this request .

MaxSupernova · May 2nd, 2014, 10:15 AM

Quote:

Originally Posted by rob

This has already been identified as a bug that we'll be fixing in an upcoming release. So there's no further need to +1 this request .

Whoohoo!!!

Finally I suggest something that isn't nitpicky or whiny!

*touchdown dance*

Farling Senior Member Join Date: Mar 2013 Location: Greater London, UK Posts: 2,623 May 1st, 2014, 11:57 PM	Warning about those conflicts are fine, Parody, but when the only conflicts are to the SAME topic, then it shouldn't really indicate a conflict (and always take the longest of the available options).
#3

rob Senior Member Lone Wolf Staff Join Date: May 2005 Posts: 8,232 May 2nd, 2014, 02:47 AM	This has already been identified as a bug that we'll be fixing in an upcoming release. So there's no further need to +1 this request .
#5