Missing letters in a name
Indexing instructions say, "If at least part of a name was given for an individual who should be indexed in this project, index the part of the name that was given." They also say, "For consecutive unreadable letters or numbers, use an asterisk (*) to replace the unreadable group of letters or numbers."
Unless I have simply missed it, there is no detail on how to index a name where two parts are given as a first part and last letter. For example, Danl is a typical shortened form of Daniel. The final "l" is a superscript, which implies missing letters between the first and last part of what is written. It is not that the letters between the first and last part are unreadable, but they are just missing and known to be missing. In that sense they are unreadable. Would it be appropriate to index the name as Dan*l?
I would like to suggest that Dan^l be an acceptable way of indexing this name.
Answers
-
I agree - and have stated so I'm the past. However some very knowledgeable indexing participants disagree - they prefer "index what you see" - Danl in this case. I would like to see an official rule at least - like using ^.
If no rule is given I would like to know if post-indexing processes link to Dan*l or Daniel - such that a researcher will find results. I have seen abbreviation results in records - so it would be interesting to know how the results are handled.
0 -
If letters are missing, they're not unreadable. Unreadable means the letters are there but are illegible. That's why we put a symbol for letters we can't read. We just put what's on the document when there are missing letters, as in an abbreviation. In a search on Family Search, Danl, Daniel, Danny, all come up as options.
0 -
If letters are missing, they're not unreadable.
Disagree ...
But if the letters are missing inputting * or ^ is not an expansion - it's just an indication that there ARE letters in that position (don't care how many or few - Danel, Daneel, Daneal, Dananeal...).
In a search on Family Search, Danl, Daniel, Danny, all come up as options.
As options for what? A search for first name Danl or Dan*l? If Danny came up searching for Danl then ...that's why - like I said above - it'd be good to get an official ruling and know how post-indexing handles abbreviations.
If they already handle through linking to wildcard searches - then an official response would resolve the speculation - and we can type it as 'on the record'. But from what I've seen in Search results - post-indexing may not resolve all - so it brings into question ...
... But wait this record indicates missing letters with . - so I better type Dan.l ... That's what I see (ignoring superscript).
I would prefer Dan*l since it is an existing rule for multiple letters - but then if post-indexing didn't resolve Dan?l - I guess the researcher just has to plug that in... Or Dan*. Maybe I should just squint and input Dan* - and similar for all superscript abbreviations?
My best guess is that indexing admin would say input as Danl (grrr...) - Dan*l does no harm (of which I am aware).
0
