Open mwmalinowski opened 10 years ago
I think any differentiation due to translation or typos should be reflected with parenthesis rather than a forward slash. I associate the forward slash with another unique name. If the names are actually referring to the same individual but it is only misspelled or typed incorrectly I think that is best indicated by parenthesis. This could be applied to aliases as well. As if to say (also known as ...)
The reason I shied away from parentheses was because of multiple aliases--usually when there are spelling discrepancies mixed with aliases.
How would you write up 85-6450?
Ideally this is something that the backend search engine code should deal with... but currently that is not the case.
Ideally this is something that the backend search engine code should deal with... but currently that is not the case.
Does this mean that on the website we could identify the instrument by it's correct spelling and/or correct industry standard name, but have the ability to allow buyers to pull up that same instrument if they enter an incorrectly spelled name? ([e.g. Buyer types Zipster, Stockman-Zipser or Stockmann-Zipser etc. but Zipser comes up in the search -because Zipser is actually the correct name and the correct spelling)
I don't believe we currently have the capability, but it's not outside the realm of feasibility. I'm not sure I would want the search engine to do it without a "did you mean _Zipser_" or something like that. We don't want the user to think that they got irrelevant search results.
Sometimes we have a compound family name:
Sometimes we have two family names that are mostly the same, save for one key difference:
Sometimes the two family names are true aliases and have no known difference
Sometimes the differentiation is not consistent in the industry:
Sometimes translations yield multiple variations:
Sometimes typos are so industry-pervasive that we include them:
I've also considered that maybe we should only use hyphenations for actual surnames:
I've listed everything above according to what I've been doing to this point; I'm not saying that these are the formats that we must use, moving forward.