pennylenger
commented
5 months ago @tmqdeborah Hi Deborah, I have some questions about HeadingsFieldsPersonalNames and Family name in terms of the format. How can I make them clear by mapping individually or combination of subfields in the google sheet. If you get time, could you please look at following questions? @GordonDunsire hi Gordon, I have added you subject part to the family name tab of Deborah's original google sheet. I didn't separate them into different rows for one heading, because I think they should be put together. Could you please take a look at it to see whether it works or how I should separate them to fit into Deborah's format?
For x00 $c-Titles and words associated with a name is used for occupation and other distinguishing characteristics, not just affiliation, so needs different mapping – it is a catch-all
For personal names, it has been mapped to authorized access point for person. Should we try to use some more specific element based on different conditions? If yes, how can we write the conditions?
For family names, it has been mapped to hereditary term of honour and profession or occupation. How should we write conditions to make the mapping right or are there any other appropriate elements?
For the personal names tab: Should we list a subfield or combination of different subfields and their mapped RDA elements clearly in each row to avoid confusion and redundancy? For example: for $q, $c, $d, the note says include values for other elements or designations in an access point, if required]. Since these subfields need to be mapped together with other subfields as authorized access point for person, not individually, just like $a,$b,$c,$d,$g,$j,$q,$u -> Authorized access point for person, I think that they should not be listed individually. It may be confusing.
List them individually in a row unless it can be mapped individually to a more specific element, for example: $q - Fuller form of name (NR)->Fuller form of name; or list them in a row with the the combination of different subfields if they can be mapped to other elements, for example: $a$b->Name of person $a$b is also mapped together to Authorized access point for person; and $a individually mapped to Authorized access point for person. Is it redundant as $a,$b,$c,$d,$g,$j,$q,$u has been mapped to Authorized access point for person.
For $q, the note also says to include values for other elements or designations in an access point, which I think is mapped as an AAP together with other subfields. The RDA element in this field is Fuller form of name.
$t and $k are put together, no RDA element in this row, in the notes it says Map as part of title, so is the element for $t$k title of work? And how to map as part of ?
$n is mapped to several elements according to different conditions What does it mean by “map as part a AP” ? Is the element used access point for person? Then what subfields are other parts of the AP? If subfields are listed, it will be clear.
For $p, is the element for $t$n or $t$p$n title of work? and they should be mapped together, no individual mapping for $p ?
For Gordon's documentation. We had a discussion on 5.15 meeting and below it some points.
For x00 first indicator = 3-Family name Family name AAP will be $a$c$d$g In a MARC access point, there would never be $u or $j LCSH and Name Authority File have different approaches to family name
And other people think that $y$z aren’t topical subdivisions, but they are subject subdivisions. And there are still some controversy over $v. Concept (exists(600, 610, 611. 648, 651 $x, $y, $z))
tmqdeborah
AdamSchiff
cspayne
Create mapping spreadsheet for X00’s based on HeadingsFieldsPersonalNames and Personal names portion of Transforming Subject Data
@pennylenger will be responsible for creating the initial pass at this documentation, and will ask questions as needed. @CECSpecialistI will keep an eye out for issues that need attention from @GordonDunsire or Deborah, unless they get to them first :) @cspayne will use the spreadsheet to write transformation code for the relevant fields, using Personal names portion of Transforming Subject Data for additional context as needed.