From: Naomi D. <nd...@st...> - 2008-07-21 21:12:40
|
Hi Andrew, Thanks for checking into this. It wouldn't surprise me if we had slightly different cataloging practices re: 245 subfields p and n. I will check about your refinements to my suggestions with our metadata expert. - Naomi Begin forwarded message: > From: Andrew Nagy <and...@vi...> > Date: July 21, 2008 1:47:06 PM PDT > To: Naomi Dushay <nd...@st...>, "vuf...@li... > " <vuf...@li...> > Subject: RE: [VuFind-Tech] title fields questions > > Naomi - I confirmed with our metadata librarian that I did have the > oldTitle and newTitle fields incorrect. However it seems that we > should have both the subfield a and the subfield t. > > As to the 245 - we questioned this. The p subfield is kind of like > an alternate title in which we might want to add it to the title2 > field. The n subfield is usually a number, and doesn't necessarily > make sense adding to the title field? > > Regardless - with VuFind 1.0, we have added a new field called > allFields which holds all of the data of the records for doing an > all fields search. So anything missing from the fielded data will > get caught in the allfields field. > > Andrew > > p.s. Non technical questions such as this may be better asked on the > vufind-general list where you will have a wider audience. > > > >> -----Original Message----- >> From: vuf...@li... [mailto:vufind-tech- >> bo...@li...] On Behalf Of Naomi Dushay >> Sent: Monday, July 21, 2008 3:19 PM >> To: vuf...@li... >> Subject: [VuFind-Tech] title fields questions >> >> Has anyone else's librarian's suggested the following? >> >> In one of our librarian views of the VuFind index fields, our >> resident >> MARC expert said: >> >> oldTitle: should be 780 subfield "t" (currently "a") >> newTitle: should be 785 subfield "t" (currently "a") >> >> Looking at the MARC documentation: >> 780: http://www.loc.gov/marc/bibliographic/bd780.html >> 785: http://www.loc.gov/marc/bibliographic/bd785.html >> "a" is "main entry" and "t" is "title." I can't remember what he >> said exactly, but he convinced me that "t" is the more appropriate >> subfield. >> >> also, he suggests that the title field should be changed: >> >> title: should be 245 subfields "a" "b" "n" and "p" (currently only >> "a" and "b"). >> >> I think his example was of a complex journal search that had been in >> two separate parts and then replaced by another journal. >> >> Just wondering if anyone else did the above, or considered the above >> and did NOT do it ... >> >> Naomi Dushay >> nd...@st... >> >> >> >> >> ----------------------------------------------------------------------- >> -- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Vufind-tech mailing list >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech Naomi Dushay nd...@st... |
From: Corinna B. <cor...@ha...> - 2008-07-21 22:31:43
|
<html> <body> Some examples of the significance of $n and $p:<br><br> |a Madrigals. <br> |n Part 1. <br> |p Il primo libro de madrigali a cinque voci (Venice, 1602) <br><br> |a Madrigals. <br> |n Part 2. <br> |p Il secondo libro de madrigali a cinque voci (Venice, 1604) <br><br> |a The Dictionary of national biography.<br> |p Missing persons<br><br> |aThe City of Akhenaten.<br> |n Part I:<br> |p Excavations of 1921 and 1922 at El' Amarneh.<br><br> |a Opera quarta. <br> |n Prima parte, <br> |p Sei introduttioni teatrali <br><br> <br><br> At 02:12 PM 7/21/2008 -0700, Naomi Dushay wrote:<br> <blockquote type=cite class=cite cite>Hi Andrew,<br><br> Thanks for checking into this. <br><br> It wouldn't surprise me if we had slightly different cataloging practices re: 245 subfields p and n. I will check about your refinements to my suggestions with our metadata expert.<br><br> - Naomi<br><br> Begin forwarded message:<br><br> <blockquote type=cite class=cite cite><font face="Helvetica, Helvetica"><b>From: </b>Andrew Nagy <<a href="mailto:and...@vi...">and...@vi...</a>></font><br> <font face="Helvetica, Helvetica"><b>Date: </b>July 21, 2008 1:47:06 PM PDT</font><br> <font face="Helvetica, Helvetica"><b>To: </b>Naomi Dushay <<a href="mailto:nd...@st...">nd...@st...</a>>, "<a href="mailto:vuf...@li...">vuf...@li...</a>" <<a href="mailto:vuf...@li...">vuf...@li...</a>></font><br> <font face="Helvetica, Helvetica"><b>Subject: RE: [VuFind-Tech] title fields questions</b></font><br><br> Naomi - I confirmed with our metadata librarian that I did have the oldTitle and newTitle fields incorrect. However it seems that we should have both the subfield a and the subfield t.<br><br> As to the 245 - we questioned this. The p subfield is kind of like an alternate title in which we might want to add it to the title2 field. The n subfield is usually a number, and doesn't necessarily make sense adding to the title field?<br><br> Regardless - with VuFind 1.0, we have added a new field called allFields which holds all of the data of the records for doing an all fields search. So anything missing from the fielded data will get caught in the allfields field.<br><br> Andrew<br><br> p.s. Non technical questions such as this may be better asked on the vufind-general list where you will have a wider audience.<br><br> <br><br> <blockquote type=cite class=cite cite>-----Original Message-----<br> From: vuf...@li... [<a href="mailto:vufind-tech-">mailto:vufind-tech-</a><br> <a href="mailto:bo...@li...">bo...@li...</a>] On Behalf Of Naomi Dushay<br> Sent: Monday, July 21, 2008 3:19 PM<br> To: <a href="mailto:vuf...@li...">vuf...@li...</a><br> Subject: [VuFind-Tech] title fields questions<br><br> Has anyone else's librarian's suggested the following?<br><br> In one of our librarian views of the VuFind index fields, our resident<br> MARC expert said:<br><br> oldTitle: should be 780 subfield "t" (currently "a")<br> newTitle: should be 785 subfield "t" (currently "a")<br><br> Looking at the MARC documentation:<br> 780: <a href="http://www.loc.gov/marc/bibliographic/bd780.html">http://www.loc.gov/marc/bibliographic/bd780.html</a><br> 785: <a href="http://www.loc.gov/marc/bibliographic/bd785.html" eudora="autourl">http://www.loc.gov/marc/bibliographic/bd785.html</a><br> "a" is "main entry" and "t" is "title." I can't remember what he<br> said exactly, but he convinced me that "t" is the more appropriate<br> subfield.<br><br> also, he suggests that the title field should be changed:<br><br> title: should be 245 subfields "a" "b" "n" and "p" (currently only<br> "a" and "b").<br><br> I think his example was of a complex journal search that had been in<br> two separate parts and then replaced by another journal.<br><br> Just wondering if anyone else did the above, or considered the above<br> and did NOT do it ...<br><br> Naomi Dushay<br> <a href="mailto:nd...@st...">nd...@st...</a><br><br> <br><br> <br> -----------------------------------------------------------------------<br> --<br> This SF.Net email is sponsored by the Moblin Your Move Developer's<br> challenge<br> Build the coolest Linux based applications with Moblin SDK & win great<br> prizes<br> Grand prize is a trip for two to an Open Source event anywhere in the<br> world<br> <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br> _______________________________________________<br> Vufind-tech mailing list<br> <a href="mailto:Vuf...@li...">Vuf...@li...</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/vufind-tech" eudora="autourl">https://lists.sourceforge.net/lists/listinfo/vufind-tech</a></blockquote></blockquote><br> Naomi Dushay<br> <a href="mailto:nd...@st...">nd...@st...</a><br><br> <br><br> -------------------------------------------------------------------------<br> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge<br> Build the coolest Linux based applications with Moblin SDK & win great prizes<br> Grand prize is a trip for two to an Open Source event anywhere in the world<br> <a href="http://moblin-contest.org/redirect.php?banner_id=100&url=/" eudora="autourl">http://moblin-contest.org/redirect.php?banner_id=100&url=/</a><br> _______________________________________________<br> VuFind-General mailing list<br> VuF...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/vufind-general" eudora="autourl">https://lists.sourceforge.net/lists/listinfo/vufind-general</a></blockquote></body> </html> |
From: Andrew N. <and...@vi...> - 2008-07-21 23:00:44
|
Thanks Corinna for sharing some examples. Would it make sense to appending the 245n to the title and adding 245p to the title2 field? Andrew From: vuf...@li... [mailto:vuf...@li...] On Behalf Of Corinna Baksik Sent: Monday, July 21, 2008 6:32 PM To: Naomi Dushay; vuf...@li... Cc: Vitus Tang Subject: Re: [VuFind-General] Fwd: title fields questions Some examples of the significance of $n and $p: |a Madrigals. |n Part 1. |p Il primo libro de madrigali a cinque voci (Venice, 1602) |a Madrigals. |n Part 2. |p Il secondo libro de madrigali a cinque voci (Venice, 1604) |a The Dictionary of national biography. |p Missing persons |aThe City of Akhenaten. |n Part I: |p Excavations of 1921 and 1922 at El' Amarneh. |a Opera quarta. |n Prima parte, |p Sei introduttioni teatrali At 02:12 PM 7/21/2008 -0700, Naomi Dushay wrote: Hi Andrew, Thanks for checking into this. It wouldn't surprise me if we had slightly different cataloging practices re: 245 subfields p and n. I will check about your refinements to my suggestions with our metadata expert. - Naomi Begin forwarded message: From: Andrew Nagy <and...@vi...<mailto:and...@vi...>> Date: July 21, 2008 1:47:06 PM PDT To: Naomi Dushay <nd...@st...<mailto:nd...@st...>>, "vuf...@li...<mailto:vuf...@li...>" <vuf...@li...<mailto:vuf...@li...>> Subject: RE: [VuFind-Tech] title fields questions Naomi - I confirmed with our metadata librarian that I did have the oldTitle and newTitle fields incorrect. However it seems that we should have both the subfield a and the subfield t. As to the 245 - we questioned this. The p subfield is kind of like an alternate title in which we might want to add it to the title2 field. The n subfield is usually a number, and doesn't necessarily make sense adding to the title field? Regardless - with VuFind 1.0, we have added a new field called allFields which holds all of the data of the records for doing an all fields search. So anything missing from the fielded data will get caught in the allfields field. Andrew p.s. Non technical questions such as this may be better asked on the vufind-general list where you will have a wider audience. -----Original Message----- From: vuf...@li... [mailto:vufind-tech- bo...@li...<mailto:bo...@li...>] On Behalf Of Naomi Dushay Sent: Monday, July 21, 2008 3:19 PM To: vuf...@li...<mailto:vuf...@li...> Subject: [VuFind-Tech] title fields questions Has anyone else's librarian's suggested the following? In one of our librarian views of the VuFind index fields, our resident MARC expert said: oldTitle: should be 780 subfield "t" (currently "a") newTitle: should be 785 subfield "t" (currently "a") Looking at the MARC documentation: 780: http://www.loc.gov/marc/bibliographic/bd780.html 785: http://www.loc.gov/marc/bibliographic/bd785.html "a" is "main entry" and "t" is "title." I can't remember what he said exactly, but he convinced me that "t" is the more appropriate subfield. also, he suggests that the title field should be changed: title: should be 245 subfields "a" "b" "n" and "p" (currently only "a" and "b"). I think his example was of a complex journal search that had been in two separate parts and then replaced by another journal. Just wondering if anyone else did the above, or considered the above and did NOT do it ... Naomi Dushay nd...@st...<mailto:nd...@st...> ----------------------------------------------------------------------- -- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Vufind-tech mailing list Vuf...@li...<mailto:Vuf...@li...> https://lists.sourceforge.net/lists/listinfo/vufind-tech Naomi Dushay nd...@st...<mailto:nd...@st...> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ VuFind-General mailing list VuF...@li... https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Lipartito, R. L. <lip...@ro...> - 2008-07-22 15:11:45
|
>> Would it make sense to appending the 245n to the title and adding 245p to the title2 field?<< Subfield p often makes no sense if separated from the main title. (e.g. |p Supplement or |p Indexes) It’s even more essential that the relationships between these subfields is maintained in uniform titles in the 240 or 700 field: (Concertos, ‡m clarinet, orchestra, ‡n K. 622, ‡r A major. ‡p Adagio; ‡o arr.) In cases where we decide that the subfield p data warrants its own access point, we add a 246 with that portion of the title. 245 0 0 Journal of polymer science. ‡n Part C, ‡p Polymer symposia. 246 3 0 Polymer symposia Robert Lipartito Technical Services Librarian Rowan University Music Library lip...@ro... Wilson Hall (856) 256-4500 (ext. 3543) 201 Mullica Hill Road (856) 256-4644 (Fax) Glassboro, NJ 08028 From: vuf...@li... [mailto:vuf...@li...] On Behalf Of Andrew Nagy Sent: Monday, July 21, 2008 7:01 PM To: Corinna Baksik; Naomi Dushay; vuf...@li... Cc: Vitus Tang Subject: Re: [VuFind-General] Fwd: title fields questions Thanks Corinna for sharing some examples. Would it make sense to appending the 245n to the title and adding 245p to the title2 field? Andrew From: vuf...@li... [mailto:vuf...@li...] On Behalf Of Corinna Baksik Sent: Monday, July 21, 2008 6:32 PM To: Naomi Dushay; vuf...@li... Cc: Vitus Tang Subject: Re: [VuFind-General] Fwd: title fields questions Some examples of the significance of $n and $p: |a Madrigals. |n Part 1. |p Il primo libro de madrigali a cinque voci (Venice, 1602) |a Madrigals. |n Part 2. |p Il secondo libro de madrigali a cinque voci (Venice, 1604) |a The Dictionary of national biography. |p Missing persons |aThe City of Akhenaten. |n Part I: |p Excavations of 1921 and 1922 at El' Amarneh. |a Opera quarta. |n Prima parte, |p Sei introduttioni teatrali At 02:12 PM 7/21/2008 -0700, Naomi Dushay wrote: Hi Andrew, Thanks for checking into this. It wouldn't surprise me if we had slightly different cataloging practices re: 245 subfields p and n. I will check about your refinements to my suggestions with our metadata expert. - Naomi Begin forwarded message: From: Andrew Nagy <and...@vi...> Date: July 21, 2008 1:47:06 PM PDT To: Naomi Dushay <nd...@st...>, "vuf...@li..." <vuf...@li...> Subject: RE: [VuFind-Tech] title fields questions Naomi - I confirmed with our metadata librarian that I did have the oldTitle and newTitle fields incorrect. However it seems that we should have both the subfield a and the subfield t. As to the 245 - we questioned this. The p subfield is kind of like an alternate title in which we might want to add it to the title2 field. The n subfield is usually a number, and doesn't necessarily make sense adding to the title field? Regardless - with VuFind 1.0, we have added a new field called allFields which holds all of the data of the records for doing an all fields search. So anything missing from the fielded data will get caught in the allfields field. Andrew p.s. Non technical questions such as this may be better asked on the vufind-general list where you will have a wider audience. -----Original Message----- From: vuf...@li... [mailto:vufind-tech- bo...@li...] On Behalf Of Naomi Dushay Sent: Monday, July 21, 2008 3:19 PM To: vuf...@li... Subject: [VuFind-Tech] title fields questions Has anyone else's librarian's suggested the following? In one of our librarian views of the VuFind index fields, our resident MARC expert said: oldTitle: should be 780 subfield "t" (currently "a") newTitle: should be 785 subfield "t" (currently "a") Looking at the MARC documentation: 780: http://www.loc.gov/marc/bibliographic/bd780.html 785: http://www.loc.gov/marc/bibliographic/bd785.html "a" is "main entry" and "t" is "title." I can't remember what he said exactly, but he convinced me that "t" is the more appropriate subfield. also, he suggests that the title field should be changed: title: should be 245 subfields "a" "b" "n" and "p" (currently only "a" and "b"). I think his example was of a complex journal search that had been in two separate parts and then replaced by another journal. Just wondering if anyone else did the above, or considered the above and did NOT do it ... Naomi Dushay nd...@st... ----------------------------------------------------------------------- -- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Vufind-tech mailing list Vuf...@li... https://lists.sourceforge.net/lists/listinfo/vufind-tech Naomi Dushay nd...@st... ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ VuFind-General mailing list VuF...@li... https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Bernhard E. <ev...@bi...> - 2008-07-22 05:58:51
|
Andrew Nagy wrote: > > > Would it make sense to appending the 245n to the title and adding 245p > to the title2 field? > FRBR would dictate that one bring together what belongs together - in this case meaning all parts ($p and $n are not always both present!) that make up one whole. Moreover, for the "FRBR select" function, there needs to be the option of presenting the whole and its parts in a meaningful way. How you achieve that is a matter of your design. The awful thing about MARC is, in the light of FRBR, that it has no consistent way of representing parts and wholes. Or rather, MARC practice is inconsistent because AACR chp.13 doesn't make it clear which of four options to apply in which cases. B.Eversberg |