On Oct 11, 2007, at 1:03 PM, Christiaan Hofman wrote: > > On 11 Oct 2007, at 6:48 PM, Adam M. Goldstein wrote: > >> I am starting to work through the cataloging rules in order to >> improve treatments of imports from z39.50 imports. First, I have a >> question for Christiaan or some other developer about how the parsers >> work. Does it work by reading the field numbers, and then the >> indicator? > > Basically, yes. BTW, we don't use the format dumped in the Annote > field but the raw MARC, which is better machine readable (more well- > defined). >
That makes sense. >> For example, the following line was copied from the >> "Annote" field of a BT record in BD that I imported from a library >> catalog: >> >> 050 00 $aB358$b.C57 >> >> 050 is the field number, while the first 0 is the first indicator and >> the second 0 is the second indicator. >> >> The question is, could the parser determine the value of the >> indicators? These can provide important information about the >> formatting of the contents of the field. >> > > That parser can in principle determine the indicators, but currently > they are ignored. They are not always included and are sometimes > inconsistent. I haven't found a real need for them for the fields we > parse. > >> I take it that is possible identify the contents of a subfield, e.g., >> B358 in this case being subfield a, indicated by $a. >> Well, in some cases, the indicator can tell if a name is in direct order or reverse order. It also is used to distinguish titles from subtitles in the 245 field, and this has standardly used punctuation, which I usually end up having to correct. >> I am starting with subject terms, which I think should go into the >> keywords field. >> > > My problem is that there seem to be really a lot of fields that could > be suitable for keywords. I think most users wouldn't want to pollute > their keywords with too much trash. > There are some things that people probably do want, like library of congress subject headings; but maybe not. Generally the 600 fields are used for subjects of various kinds. I have been identifying those most likely to be useful with the hope that the parser can be tinkered with to put them in the keywords field. Currently subjects are imported from PubMed, so I am building up a subset of MeSH subject headings in my keywords field. A given record usually has lots and lots of those; a library catalog record will have at most three or four. I think it would be nice to do the same with the LoC keywords, or at least, not have to enter in the keywords myself from my own list at first, especially if I import a lot at once. If developers and other users really do think they don't want keywords brought in, let me know, and I won't keep up the effort. > Christiaan > >> Second---It would be useful for people using the library catalog >> import to email (off-list?) with particular issues they've had with >> content or formatting difficulties they have noticed appearing on a >> regular basis. Let me know which library you're getting the >> references from. >> >> Thanks everyone! >> >> -Adam > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Bibdesk-users mailing list > Bibdesk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-users ================================= Adam M. Goldstein PhD Assistant Professor of Philosophy Iona College -- email: [EMAIL PROTECTED] web: http://www.iona.edu/faculty/agoldstein/ tel: (914) 637-2717 post: Iona College Department of Philosophy 715 North Avenue New Rochelle, NY 10801 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
