Closed karindalziel closed 8 years ago
Yes, I think the Ellen example is right. I think all of the surnames and forenames should be grouped in the Alternate name(s) field if possible, so for Ellen (if she had a different first name); Alternate name(s): Trunel, Trunnells, Trammells, Trammel, Elen, Ellan , etc. not Elen, Trunel, Trunnels, Ellan, Trammels, Trammel
And don't forget about middle names/initials which will be encoded as
Laura
I think what you have is great, @karindalziel. If it is easy to do, you can distinguish between surname and forename in the alt name field. But I don't think it's super important; it should be obvious in almost all instances what the alt names are different spellings for.
OK, Name generation is here. Add comments with problems.
errant space before the name if it is first name only
per.000106 - <genName>
should appear after <surName>
instead of <foreName>
@kaci Wouldn't that look like e.g.:
Smith junior, William
Does that look right? I thought junior was on the foreName (e.g. the second william, not the second smith)
Do not include <roleName>
or <addName type="honorific">
? Should these even be encoded in oscys.persons?
@lweakly ?
per.000254 - TEI contains <forename type="husbands">William</forename> <addName type="honorific">Mrs.</addName>
which does not show up in generation.
<forename type="first" subtype="alternate">
is showing on several persons
@kaci - this is something @lweakly needs to fix in the TEI. She's aware of it.
@kacinash Where exactly should <forename type="husbands">William</forename> <addName type="honorific">Mrs.</addName>
appear?
My ordering:
'surname[not(@type)]' (a surname without a type on it, assumed to be the true last name) ',' (comma) 'roleName' 'forename[@type='first']' (for each, there could be more than one) 'forename[@type='middle']' (for each, there could be more than one) genName surname[@type='maiden']
Do you think it's necessary to show all of the different names? I think for search purposes (as opposed to how it looks on the person page) it should just be surname, forename middle
@kaci I think for search everything should be in there, including all the alternate names. That way if someone comes across one of the alternate spellings they can still find the person.
In the spreadsheet, I am giving them a fullName (which I proposed to Jessica be changed to displayName). Perhaps we could just use that? I have not cleaned those up yet, but was planning on it.
Laura Weakly Metadata Encoding Specialist Center for Digital Research in the Humanities University of Nebraska-Lincoln Lincoln, NE 68588-4100 402-472-4547
From: Kaci Nash notifications@github.com Sent: Thursday, July 16, 2015 2:19 PM To: CDRH/earlywashingtondc Cc: Laura Weakly Subject: Re: [earlywashingtondc] need rules on displaying people names (#11)
Do you think it's necessary to show all of the different names? I think for search purposes (as opposed to how it looks on the person page) it should just be surname, forename middle
Reply to this email directly or view it on GitHubhttps://github.com/CDRH/earlywashingtondc/issues/11#issuecomment-122057253.
@kacinash @lweakly The problem is, the name is not coming from the spreadsheet for the solr stuff. It is coming from the personography. I can't think of a way to use the spreadsheet at this point that's not terrible convoluted and prone to breaking. So I would really rather either format the names from the personography persName, or add another field in the personography where we put a display name.
Karin,
I will add a
@lweakly if you do that in the person TEI then you will not need to do it in the spreadsheet any longer, because I can grab the information from the TEI instead! :)
Closed because we addd persName=display
Here's a nice example, but there are probably more complicated ones:
<person xml:id="per.000896" source="http://earlywashingtondc.org/cases/oscys.case.0124.001"> <persName><surname>Trunnell</surname> <addName type="surname" subtype="alternate">Trunel</addName> <addName type="surname" subtype="alternate">Trunnells</addName> <addName type="surname" subtype="alternate">Trammells</addName> <addName type="surname" subtype="alternate">Trammel</addName>, <forename type="first" full="yes">Ellen</forename></persName>
In this case I imagine the rules are:
in name field: if surname, then surname if surname AND forename, add comma: , if forename then foreName
in alt name field: all instances of addName? (Should we distinguish between surname and forename here?)
thus, you'd end up with Trunnell, Ellen for the name and Trunel, Trunnells, Trammells, Trammel in the alternate name field
If there were no last name, it would be just "Ellen" and if no first name it would be just "Trunnell"
Hope this makes sense. We might need to have a meeting about this and work it out on the white board, but first, I think it would be useful if @lweakly and @kacinash determine the hardest name cases so we can look at those.