{\rtf1\ansi\ansicpg1252\deff0\formshade\deflang1033{\stylesheet {\ql \li0\ri0\widctlpar\wrapdefault\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 \snext0 Normal;}{\*\cs10 \additive \ssemihidden Default Paragraph Font;}{\*\ts11\tsrowd\trftsWidthB3\trpaddl108\trpaddr108\trpaddfl3\trpaddft3\trpaddfb3\trpaddfr3\trcbpat1\trcfpat1\tblind0\tblindtype3\tscellwidthfts0\tsvertalt\tsbrdrt\tsbrdrl\tsbrdrb\tsbrdrr\tsbrdrdgl\tsbrdrdgr\tsbrdrh\tsbrdrv \ql \li0\ri0\widctlpar\wrapdefault\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1024\langfe1024\cgrid\langnp1024\langfenp1024 \snext11 \ssemihidden Normal Table;}}{\fonttbl{\f0\fswiss\fprq2\fcharset0 Arial Unicode MS;}{\f1\fmodern\frpq1\fcharset0 Courier New;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;\red225\green255\blue225;\red225\green255\blue225;}\viewkind4\uc1\pard\plain \ql \fi-1200\li1200\ri0\widctlpar\wrapdefault\aspalpha\aspnum\faauto\adjustright\rin0\lin360\itap0\lang1033\langfe1033\cgrid\langnp1033\langfenp1033\f1\fs24 

\f0\b 2014 02 03 (version 1.6.197 and higher) \par\b0
\tab\bullet Construction of 338 fields corrected. Instead of 'other microform carrier', and so on, program now just uses 'other'. Program supplies specific code in subfield $b.\par

\f0\b 2014 01 19 (version 1.6.197 and higher) \par\b0
\tab\bullet Validation of commas in personal names now allows the comma to be within quotes (example of heading that now passes validation: n 2013074427; whether this particular heading is correct or not, is not the question.)\par
\tab\bullet New rule in authvalid.cfg: If 376 field is present, 100 field must also be present.\par
\tab\bullet New rule in authvalid.cfg: if 040 $a is DLC, then 008/39 (record source) must be blank.\par
\tab\bullet BAM now allows verification of subfield $a in a 373 field against a series authority record; a person might be the editor of a series, and that's a reasonable use of the "associated organization" concept. (Example: no2007090846)\par
\tab\bullet I have uploaded fresh copies of several of my configuration files (including authvalid.cfg) to the configuration folder at the toolkit download site.\par


\f0\b 2015 01 17 (version 1.6.196 and higher) \par\b0
\tab\bull4t   Change defaults for the lead text used in subfield $b of 670 fields in new authority records from 't.p.' to 'title page' and from 'series t.p.' to 'series title page'. All of these default texts are now available on the options panel (BAM options, Authority tab, Contents sub-tab).\par
\tab\bullet   When BAMming an authority record, if a portion of a heading properly matches the 1XX in another authority record, the BAM report includes the cataloging rules code from that record. If the matching authority record is marked 'not for use under RDA without review', the BAM report uses the ')' code to identify the condition.\par
\tab\bullet   When using the 'pick up' feature on the 'design your own correction' panel, the tags used for the 'new heading' are now correctly 1XX tags, instead of 4XX tags.\par
\tab\bullet   The toolkit automatically notices that you have changed your Voyager tag tables, and re-generates the VITagTableC.txt file for you. You no longer have to delete the file and re-start the toolkit to get a new version of this file.\par
\tab\bullet   If a the text of a coded subfield is not defined, the BAM report will show a normalized version of the code. This allows the toolkit to 'collapse' multiple reports for the same undefined code into a single report, regardless of incidental capitalization or punctuation.\par
\tab\bullet   The toolkit assumes that in all cases subfield $x (ISSN) in bibliographic 8XX fields will follow the last displayable subfield in the field, and that no punctuation is associated with the subfield. It is recommended that the subfield-order rules for bibliographic 8XX fields be adjusted accordingly. Here is Northwestern's version of the rule for the 830 field, for example: 6a\{#nplfksdhmorgtv\}x0 This rule forces subfield $x to come after all subfields, except subfield $0, which is last.\par
\tab\bullet   A bug in the verification routine prevented the toolkit from checking the first subfield in a name/title authority 4XX field. It is not clear how long this bug was present, but it may have only been a short while. (The bug does not appear at other sites with recent toolkit builds, but there is also no comment on the problem code line showing that it was changed recently.) Bug fixed.\par
\tab\bullet   There was some confusion in the verification of RDA fields in authority records. At one point, the toolkit was only considering the second and third characters of tags, and confused a 181 field with a 381 field. All better, now.\par
\tab\bullet   The test of EDTF dates in authority 046 fields allows a date to end with two full stops (indicating an open range, I think).\par
\tab\bullet   The list of possible 338 fields generated with Leader/06 = 'e' was expanded (mostly allowing for more possible cases of 'sheet').\par
\tab\bullet   The toolkit will now generate 33X fields in a bibliographic record with no associated holdings records; but of course it must make assumptions about microform and online possibilities, based on the content of the bibliographic record.\par
\tab\bullet   If the toolkit cannot parse a pre-RDA 502 field into the current RDA subfield structure, the BAM report includes a message to that effect.\par
\tab\bullet   The toolkit does not test language codes in authority 377 if subfield $2 is present.\par


\f0\b 2013 12 03 (version 1.6.189 and higher) \par\b0
\tab\bullet   Change to 338 field generation: "volume" now also generated for music scores. (Previously, most scores did not get a 338 field.)\par
\tab\bullet   Addition to the RDA-ization of 300: If (after spelling out abbreviations) subfield $a is in the form "X pages of music" change to "1 score (X pages)"; similar changes for "leaves of music", and the singular forms of each.\par

\f0\b 2013 11 21 (version 1.6.189 and higher) \par\b0
\tab\bullet   Additional refinements to the sorting form for dates.\par
\tab\bullet   An edtf date (authority 046 field) that is both uncertain (with '?') and contains unspecified parts (with 'u') is no longer reported as an error.\par
\tab\bullet   The routine that generates 'shadow' references no longer creates any if subfield $d in a personal name contains 'active' or 'fl.'.\par

\f0\b 2013 11 18 (version 1.6.189 and higher) \par\b0
\tab\bullet   Refine the verification code (part of the BAM tests) to detect uniform title problems for motion pictures, to work with (RDA-ized) records without 'videorecording' in 245 subfield $h.\par
\tab\bullet   Expand values permitted in validiation special test #41 to include a string of Unicode characters. For example, to scan the 100 field in a record for the Euro character, use this: <41:100,U+20AC>\par
\tab\bullet   The test for an uppercased first character within personal name subfield $c allows "fils" to be lowercased. (The former exception to allow text to begin 'of' was removed.) Additional exceptions will be added as the need is identified.\par
\tab\bullet   The test personal name subfield $d allows family names to have a date without a hyphen.\par
\tab\bullet   An EDTF date in the authority 046 field that lists a choice of dates may contain a comma-space without complaint: '$f [1910-05-27, 1913-05-27] $2 edtf' is considered acceptable.  (GLS doesn't like the space, but there are just too many of these to fix.)\par
\tab\bullet   The 'reset' button on the 'fancy editing' panel preserves the 041 field as it may have been modified; it no longer restores the field to the version currently residing in Voyager.\par
\tab\bullet   Add to the heading verification tests for the '$l' tab the possibility that *part* of the new heading may match all or part of an authority 1XX field.\par
\tab\bullet   Add options to display heading verification results on the '$l' tab in bold, italic or color.\par
\tab\bullet   Button added to the fancy editing form to BAM the record as modified, without actually saving the record to Voyager first.\par
\tab\bullet   Toolkit uses the abbreviation 'S.A.' instead of 'S.Aust.'.\par
\tab\bullet   Add a 'modify 041' button to the $l tab on the fancy editing form; use this to modify an existing 041 field or to create an 041 field where none exists.\par
\tab\bullet   As an experiment, the routine that derives the 'sorting' form for personal names was changed, so that subfield $d consisting solely of a death date is sorted in a more reasonable manner. This may become permanent after further testing.\par
\tab\bullet   Many additional small fixes to the '$l' and the now-associated 'work with list of records' buttons. \b Anyone making heavy use of the '$l' button should make sure to have version 1.6.189 or higher, as the latest version is both more correct and more convenient.\b0\par


\f0\b 2013 10 24 (version 1.6.179 and higher) \par\b0
\tab\bullet   Added a 'Classical Greek' button to the $l panel, to repair the common error of using 'gre' when 'grc' is meant. If you click this button, the toolkit changes the language code(s) in the 041 field, and resets the language names in the drop-down lists.\par
\tab\bullet   When using the $l button: if the toolkit needs to pause to ask a question about the record, the question includes a 'Cancel' button.\par
\tab\bullet   New option for the $l button: If only two languages are involved, automatically click the 'Carry out these instructions' button. Most of the time, this will save one click; if you select this option but don't like the results in a particular case, click the 'Reset' button on the fancy editing panel to start over. If you select this option, get into the habit of paying even closer attention to the 041 field before you click the $l button.\par
\tab\bullet   Completed work on a BAM option for new authority records that appears to have been started at some time but never completed. The new option (on the 'endgame' sub-tab for authority records) applies your decision on pre-AACR2 records also to AACR2 records (now that we're primarily using RDA).\par
\tab\bullet   Enhanced the 'view records in list' tool so that it can pass records directly to the $l button (with the very strong possibility possibility of passing records directly to other buttons in the future).\par
\tab\bullet   Added a button to the $l tab, visible when starting from a file of record numbers: save this record and move to the next. This, in combination with other changes today, means that if you're working on a file of record numbers sent to the $l button, a single click is all you need for the typical record.\par
\tab\bullet   If from the BAM report you click the Change button to flip a heading that matches an authority 4XX field, the toolkit now deals in the standard way with a terminal full stop in the authority 1XX.\par

\f0\b 2013 10 23 (version 1.6.179 and higher) \par\b0
\tab\bullet   Small improvement to display for the $l button when the toolkit pauses to ask if the bibliographic record represents a bilingual edition.\par
\tab\bullet   Fixed a verification bug, eliminating a spurious complaint about punctuation when an authority record has 110 and 500 fields, and both contain subfield $b.\par

\f0\b 2013 09 26 (version 1.6.179 and higher) \par\b0
\tab\bullet   Documentation updated to reflect tweaks to the generation of 33X fields
in bibliographic records.\par

\f0\b 2013 09 26 (version 1.6.169 and higher) \par\b0
\tab\bullet   New builds of toolkit for all known versions of interest. This build incorporates the latest changes/improvements to the "RDA-ization" scheme.  Development/refinement of this scheme continues.\par

\f0\b 2013 09 26 (version 1.6.168 and higher) \par\b0
\tab\bullet   BAM now adds to authority records a 667 field saying "Non-Latin script reference[s] not evaluated." if an authority record contains unsuppressed non-roman 4XX fields and if the record doesn't already contain a similar field. The toolkit also sets the reference evaluation byte (008/29) to 'b'.This isn't optional at present. Those new authority records to which the toolkit adds a 4XX field with non-roman script will have the same note.\par

\f0\b 2013 09 24 (version 1.6.168 and higher) \par\b0
\tab\bullet   Fixed an error in the logic of the "convert a series from traced to untraced" feature; the bug caused the program not to change any of the the things that it shuold, if there were any things that it shouldn't change.\par

\f0\b 2013 09 24 (version 1.6.167 and higher) \par\b0
\tab\bullet   Fixed a mistake in the code that supplies authority 370 $c based on information elsewhere in the 370. The toolkit supplied "United Kingdom" when it should have supplied "Great Britain.\par

\f0\b 2013 08 29 (version 1.6.164 and higher) \par\b0
\tab\bullet   I'm working right now on changes related to the just-announced policy change for the authority 370 field. There needs to be a change to the verification routine that distinguishes between 370 fields created under different policies, and there needs to be a change to the routine that adds 370 fields. If anyone has thoughts on this matter, please contact me directly.\par

\f0\b 2013 08 29 (version 1.6.162 and higher) \par\b0
\tab\bullet   The toolkit now recognizes as valid a record number for a suppressed bibliographic or holdings record that is given within parentheses in the window's title bar.\par

\f0\b 2013 08 15 (version 1.6.162 and higher) \par\b0
\tab\bullet   A small change in the logic for the 'create your own batch correction' panel allows all recognized subject heading systems to appear, not only those that are defined as being staff-displayable.\par

\f0\b 2013 07 18 (version 1.6.160 and higher) \par\b0
\tab\bullet   Print processing list button: fixed a very long-standing bug that caused options related to printing in two columns not to be saved properly--at least, not in all cases (!). Also fixed another bug (? if a bug, also of long standing) that did not save the most recently-selected item on the options panel as the default option when requesting the print processing list feature itself. (It's not absolutely certain that this should be considered a bug, because it may be that the item most recently viewed in the options panel is not wanted as the default. I put a message on the options panel so you at least now understand the behavior.)\par

\f0\b 2013 07 18 (version 1.6.159 and higher) \par\b0
\tab\bullet   BAM: Some improvements to the routine that tries to find a qualifier to add to a 410 field for initials. The initial routine could make the incorrect decision in languages that use lowercase initial letters for 'important' words, and the name also contains 'little' words that begin with the same letters. Example of a 410 that is now correct: "FPP (Front patriotique pour le progre\u768?s)" [formerly: "FPP (Front patriotique pour)" and later "FPP (Front patriotique)")].\par

\f0\b 2013 07 17 (version 1.6.159 and higher) \par\b0
\tab\bullet   Now that I'm again permitted to work on the online documentation, I've been pounding on it tolerably hard. I believe that the documentation now describes in some fashion all of the current features, and describes all of the current options. I may not yet have been perfectly successful at removing things that are no longer relevant, but I'm trying. The documentation still has some glaring holes in it, but it's at least a lot better than it used to be. Make sure your toolkit option for the online help button has the correct (new-ish) base address: http://files.library.northwestern.edu/public/CatalogersToolkit/Documentation/Online/\par
\tab\bullet   I've also updated the associated Word documents, and there is a new one describing many of the configuration files used by the BAM button, created out of an appendix to a document that never got very wide distribution.\par
\tab\bullet   BAM: Fixed a bug in the recently-added 'more than one internal comma in X00 subfield $a' routine: ignore a comma at the end that's followed by a quotation mark (example: Griffin, A.C. "Buck,")\par
\tab\bullet   BAM: The toolkit now complains if a date in an 046 field that does not have subfield $2 with 'edtf' indicates a season of the year (as in: 1924-21). The correct response is probably to add subfield $2.\par
\tab\bullet   BAM: Fixed a bug in the verification of the 372 field, when testing text that follows a double hyphen. At the relevant point, the toolkit is only interested in matching the text following the hyphens against geographic information. There was already a test that required an interesting 1XX field to actually be a 151, and now there is a parallel test requiring that a 4XX field actually be a 451. (Sample heading now verified correctly: "China--History--Qing dynasty, 1644-1912"; formerly, the toolkit matched the last part against a 400 field, and didn't like the result.\par

\f0\b 2013 07 15 (version 1.6.159 and higher) \par\b0
\tab\bullet   Added an option, so that a newly-created AACR2 authority record receives the same handling as a pre-AACR2 record did previously. If you haven't configured the toolkit to coerce AACR2 records into RDA records, this option will allow you at least to receive a notification that a new authoritmy record is not an RDA record.\par

\f0\b 2013 07 11 (version 1.6.159 and higher) \par\b0
\tab\bullet   BAM: Fixed a bug in the validation of dates in authority 046 fields with $2 'edtf' that caused a spurious complaint about a date sfield that contains correct hyphenation\par

\f0\b 2013 07 10 (version 1.6.156 and higher) \par\b0
\tab\bullet   BAM: Fixed a bug in the handling of bibliographic 33X fields that caused the addition of a subfield delimiter with neither subfield code nor text\par

\f0\b 2013 07 09 (version 1.6.156 and higher) \par\b0
\tab\bullet   BAM: Fixed a bug (unnecessary 'subfields out of order' message) that only appears when you select the 'make no change during BAM' option\par

\f0\b 2013 07 06 (version 1.6.156 and higher) \par\b0
\tab\bullet   Added an option to the 'view records in list' button, to copy the Vger bib record number to the Windows clipboard. If the toolkit has trouble opening records, using this option means that at least you'll be able to paste the record number into the cataloging client instead of typing it yourself.\par

\f0\b 2013 07 05 (version 1.6.156 and higher) \par\b0
\tab\bullet   BAM: Added the expansion of abbreviations in bibliographic 260 $c, similar to work done for 260 $a and $b. This is turned on by a new option.\par

\f0\b 2013 07 03 (version 1.6.156 and higher) \par\b0
\tab\bullet   BAM: new option to request duplication of a 410 field for initials with or without ful stops (example: if there's a 410 field for "BZE" the toolkit will create one for "B.Z.E."; or vice versa)\par
\tab\bullet   BAM: new option to request addition of a parenthetical qualifier to 410 fields for initials\par

\f0\b 2013 06 10 (version 1.6.156 and higher) \par\b0
\tab\bullet   BAM: New options on the "Authority-related" tab, "Get started" sub-tab, related to authority 410 fields. Under the first option the toolkit can "duplicate" a 410 field that consists of initials, automatically supplying a form with or without full stops if only one of the two appears in the record. Under the second option (which is independent of the previous option) the toolkit will attempt to find the full form for a 410 that consists of initials by scanning the texts of the 110 and 410 fields. There is some cleverness in this work, but even so the toolkit will not always be able to find a match, and if it does find a match the toolkit will not necessarily find the best match. Especially because of the latter possibility, this option should not be selected by people who will not pay attention to the results of the toolkit's work. (The default value for both of these options is "don't do it.")\par
\tab\bullet   BAM: I have added 260 subfield $c to the 260 subfields that may contain abbreviations to be spelled out. This work is included under the existing option for abbreviations in the 260 field, so if you've already turned this option on, you'll get $c automatically. There is no additional configuration required (at this time) for the toolkit's work wiath 260 $c.\par

\f0\b 2013 06 10 (version 1.6.146 and higher) \par\b0
\tab\bullet   General: I'm making up installation packages for all toolkit verisons, incorporating all changes since the last update.\par

\f0\b 2013 06 08 (version 1.6.146 and higher) \par\b0
\tab\bullet   RDA: Discovered and fixed a bug in the tool that converts headings into an RDA-like form. The bug prevented the spelling-out of the abbreviation "Dept." in subfield $e of X11 fields--but only when "Dept." occurs at the beginning of subfield $e.  (So it doesn't occur very often!)\par

\f0\b 2013 06 07 (version 1.6.146 and higher) \par\b0
\tab\bullet   BAM: Fixed a recently-introduced bug. Consider the 372 field text "$a Italy--History $2 lcsh". When checking the whole heading, the toolkit must indeed insist that the matching heading be an LCSH heading; but when verifying just the bit before the first set of double hyphens, the toolkit (because it doesn't know what the proper tag is) should also include NAF records in the pool of possible matches. The fix introduced today allows for this flexibility.\par
\tab\bullet   Authority loader: Fixed a bug in the routine that compares a bibliographic 245 field to an authority 670 field. The bug occurred when a 670 field matched just one word from the 245; instead of looking at any remaining 670s the program stopped with a maximum match count of one, which is not sufficient to declare a match.\par

\f0\b 2013 06 05 (version 1.6.145 and higher) \par\b0
\tab\bullet   New authority records, and BAM: More elaborate scheme for generating the 368 field has been devised. This scheme involves a new configuration file. (If the configuration file is not present, the toolkit defaults to its original scheme.) The generation of the 368 field is described in revised documentation, just uploaded. The Configuration folder contains a sample configuration file for these additional RDA attributes.\par

\f0\b 2013 06 04 (version 1.6.145 and higher) \par\b0
\tab\bullet   BAM: If authority 372 or 374 field has subfield $2 LCSH, then only LCSH records are examined for matches. (Formerly, NAF records were also allowed, which lead to the occasional incorrect '$' report.) This means that if a 373 field incorretly has "$2 lcsh" on it, the toolkit will report a non-match.\par
\tab\bullet   BAM/RDA: New option on the RDA tab of authority-related options for the BAM button: add 368 subfield $d for recognized personal titles. (Default value: not checked.) NACO participants are asked not to supply 368 $d at this time; if you're a NACO participant, leave this box in its default not-checked state until NACO participants are told to include 368 $d.\par

\f0\b 2013 06 02 (version 1.6.145 and higher) \par\b0
\tab\bullet   RDA: Added conversion of 'ca.' and other abbreviations when they occur in X10 subfield $a. Example of heading that will be changed: 'New York String Quartet (ca. 1970)'. A very few headings were missed during the large RDA conversion, but have been cleaned up subsequently.\par
\tab\bullet   BAM: Added validation rules to find '$' in 370, 372 and 374 fields; and 'http://' in 670 $a and $b. (URLs may legitimately be in 670 subfields other than $u, but I find that most of the time when present, the field has been poorly constructed and needs to be rearranged.)\par

\f0\b 2013 06 01 (version 1.6.145 and higher) \par\b0
\tab\bullet   RDA: For conference name headings, use the LCSH term '$a Congresses and conventions' with subfield $2 'lcsh', in the authority 368 field.\par
\tab\bullet   RDA: For 'spirit' and 'saint' personal name headings, use the LCSH term in the plural in subfield $c, with subfield $2 'lcsh', in the authority 368 field.\par
\tab\bullet   BAM: Added report for all authority 5XX fields that contain vernacular data. Because 5XX fields must match 1XX fields, and because 1XX fields cannot (at present) contain vernacular characters, the presence of any vernacular character in a 5XX field is incorrect. Many of these are already being reported because this 5XX matches a vernacular 4XX in the related record, and in such a case this report will be redundant; but I want to make sure I get them all.\par
\tab\bullet   BAM: Change to the inspection of 670 fields for undifferentiated names, to allow the exact same 670 field to appear more than once in a record, as long as each appearance is under a different 'Author of' 670 field. (Example of a record that no longer generates an error report: n 83161650.) The toolkit will still report repeated 670 fields under one 'Author of' heading in an undifferentiated name record, and repeated 670 fields in a differentiated name record.\par
\tab\bullet   BAM: Added test for multiple internal commas in personal name subfield $a. Example of condition now detected: 'Washington, Cullen, Jr.' with no $c code.\par
\tab\bullet   BAM: Quite a few fixes to reduce the number of spurious '$' reports generated during inspection of 372 and 374 fields, particularly when it turns out that the thing that follows "--" is a geographic subdivision.\par
\tab\bullet   BAM, etc.: When generating a linking field, the tooolkit now uses the first 260 or 264 field for subfield $d. (Formerly, the toolkit only used the 260 field.)\par

\f0\b 2013 05 30 (version 1.6.145 and higher) \par\b0
\tab\bullet   BAM: 'number' added to the texts in 300 $a that will generate 338 'volume'.\par

\f0\b 2013 05 23 (version 1.6.144 and higher) \par\b0
\tab\bullet  A replacement for the former GNIS/GeoNames button has been devised! This function is now on the 'Geographic' sub-tab of the 'Authority' tab of the fancy editing panel. See the revised documentation for details. This is kind of clumsy to use, because of the different interfaces provided by GNIS and GeoNames, but it's far better than typing everything out anew.\par

\f0\b 2013 05 11 (version 1.6.136 and higher) \par\b0
\tab\bullet  BAM: Fixed a bug in the reporting of errors detected by special validation routine #45 (formatted date, such as in the authority 046 field). The symptom is that th BAM report says 'No message for test' when there is of course a message.\par
\tab\bullet  BAM: I have defined 377 second indicator '7' in my Voyager tag tables, and the code 'iso639-3' in my codes.cfg file. (Example: n 2003067500.) This leaves unanswered the question of the proper verification of this language code. For now, these will come up as 'unverified' (unless of course you define them in your codes.cfg file) but perhaps with time something better can be devised.\par

\f0\b 2013 05 11 (version 1.6.124 and higher) \par\b0
\tab\bullet  BAM: Found yet one more place in the verification of 370-374 fields to ignore a MeSH geographic authority record, if that option is selected. (Only important, obviously, if you have MeSH geographic authority records in your authority file.)\par
\tab\bullet  BAM: Two bugs recently introduced into the verification of authority 370-374 fixed, removing spurious '!' and '$' reports.\par

\f0\b 2013 05 10 (version 1.6.118 and higher) \par\b0
\tab\bullet  BAM: Another bug discovered and squashed in the 'shadow references' routine, a follow-on of the change to subfield $d normalization. Changed the manner in which the need to stop this work is detected; because of its arbitrary nature, this should eliminate the possibility of infinite loops in the future.\par

\f0\b 2013 05 10 (version 1.6.112 and higher) \par\b0
\tab\bullet  BAM: Bug discovered in the recent routine for improved handling of NACO normalized form of subfield $d in personal names. Fixed, but requires new builds of toolkit and authority loader. On the way, today and tomorrow.\par
\tab\bullet  BAM: When you double-click on a line in the BAM report, the display of the authority record now shows diacritics and non-roman characters properly.\par
\tab\bullet  BAM: Added 'ju ren' to the list of things that can appear in personal subfield $d when no hyphen is present.\par
\tab\bullet  BAM: Found another place where the NACO-normalized form needs to be used for comparison instead of the plain normalized form.\par
\tab\bullet  BAM: Verification of authority 370-374 fields now indicates (with '$') if the form in the matching 1XX differs in punctuation, etc. from the form in the authority record. (Example: 'University of Wisconsin Madison' versus 'University of Wisconsin--Madison'.) At present there is no automatic repair of such conditions, as there is for bibliographic records.\par
\tab\bullet  BAM: Verification of authority 370-374 fields now indicates (with '!') if the code in subfield $2 is the wrong code.\par

\f0\b 2013 05 07 (version 1.6.111 and higher) \par\b0
\tab\bullet  BAM: New special test (numbered 53) causes the toolkit to inspect the authority 675 field for $a subfields that might be suitable for re-tagging as 670 fields. If there are any, the BAM report indicates this; and a click of the 'Change' button will cause the toolkit to re-tag the 675 field following the revised definitions for the 670 and 675 fields. New version of authvalid.cfg uploaded to the configuration folder.\par
\tab\bullet  NUC code for series treatment: New box on the 'Institution codes' tab of the toolkit's options panel, for the institution code to use in series treatment fields (642, 644-645). Turns out that the code to be used here is not necessarily the same as the code in the 040 field, hence the need for an additional code. If this is the same as the code for the 040 fields in authority records, the toolkit will assume this for you; you only need to visit this options tab if you need a different code.\par

\f0\b 2013 05 06 (version 1.6.110 and higher) \par\b0
\tab\bullet  Merge button: Fixed a bug of very long standing that prevented certain fields from moving from the left (OCLC) record to the right (Voyager) record when clicking the 'merge' button in the middle of the merge form.\par

\f0\b 2013 05 05 (version 1.6.110 and higher) \par\b0
\tab\bullet  BAM: An experimental change to the NACO normalization routine, to retain the leading and trailing hyphens in subfield $d of personal names, allowing the toolkit to distinguish "-1938" from "1938-". Looks good so far, but testing continues. This will have important carry-over into other programs, most notably the correction receiver.\par

\f0\b 2013 05 04 (version 1.6.96 and higher) \par\b0
\tab\bullet  BAM: Options to permit standard RDA-related heading conversions (expand 'Dept.' and so on) added to the 'Changes, pt. 4' tab of the BAM configuration. (Default values are not checked, but you will almost certainly want to check them.) New version of the RDA document available at the download site. This new feature requires additional configuration files, which are described in the RDA document, and are also available at the download site. New installation packages will be built and posted today.\par

\f0\b 2013 05 03 (version 1.6.96 and higher) \par\b0
\tab\bullet  BAM: Fixed bug that caused "Congo (Brazzaville)" in a 370 field to be reported as a problem.\par
\tab\bullet  BAM: Added test of 377 subfield $a against list of language codes used for bibliographic 008/35-37.\par
\tab\bullet  BAM: Added tests of subfields $v and $u in authority 368 and 370-376, to see if the contents have the approximate appearance of text that might be left over from a template.\par
\tab\bullet  BAM: Added tests of subfields $s and $t in authority 368 and 370-376, to see if the contents have the approximate appearance of dates. (The impulse came from a record with 'start period' and 'end period', probably left over from a template, instead of actual dates.)\par
\tab\bullet  BAM: Fixed bug that prevented inspection of punctuation in authority 4XX fields for the first 4XX field in the record.\par
\tab\bullet  BAM: Changed Validit.INI to allow the spacing underscore in authority 370 $m.\par
\tab\bullet  BAM: Toolkit formerly complained about geographic names in authority 372 and 374 fields, expecting that they would be abbreviated, as they should be in the 370 field. The toolkit now correctly allows the full form in 372 and 374 fields.\par
\tab\bullet  BAM: If a geographic name is allowed to be used as a name heading but not as a subject, the toolkit now correctly complains if the name is used as an indirect geographic subdivision.\par
\tab\bullet  BAM: A pre-RDA 240 field with two languages joined by "&" becomes under RDA two analytic 7XX fields, one for each language expression. This often means that the bibliographic 1XX+245 matches an authority 400 field, which (in the absence of a 240 field) the toolkit has reported as an error. Earlier fixes have resolved the problem when BAMming a bibliographic record (by inspecting the analytic 7XX fields in the record); today's fix resolves the problem in the other direction--when BAMming an authority record.\par

\f0\b 2013 05 01 (version 1.6.96 and higher) \par\b0
\tab\bullet  Batch correction review: new version posted, fixing a small bug that affects new users (program doesn't show up!).\par

\f0\b 2013 05 01 (version 1.6.96 and higher) \par\b0
\tab\bullet  'fi' button: Numerous corrections to the program-generated SQL used when reading bibliographic and authority indexes in parallel. (Bug fixes.)\par
\tab\bullet  BAM: ValidIt.INI updated so that spacing underscore character is allowed in URL subfields, and so that spacing tilde is allowed in authority 046 $k and $l. New version posted to the download site.\par
\tab\bullet  BAM: Rule added to authvalid.cfg, declaring code 'd' in 410 $w to be invalid. (OCLC doesn't allow a record to be updated if this code is present.) New version of authvalid.cfg posted to the download site.\par
\tab\bullet  BAM: Validation routine no longer complains of missing terminal punctuation, or unrecognized abbreviations, in a suppressed authority 4XX field.\par

\f0\b 2013 05 01 (version 1.6.95 and higher) \par\b0
\tab\bullet  BAM: Validation routine no longer complains of ISBD-like punctuation in a suppressed authority 4XX field.\par
\tab\bullet  BAM: Validation of authority X00 subfield $d in a non-RDA record now permits the subfield to have either the RDA layout or the pre-RDA layout. (RDA authority records continue to require the RDA layout.) Example: "active 13th century" is now acceptable in a non-RDA record.\par
\tab\bullet  BAM: Validation rule for bibliographic 546 field (when 041 field is not also present) adjusted, so it no longer asks about the 041 field if the 546 field is 'Closed-captioned'. Updated bibvalid.cfg file posted.\par
\tab\bullet  BAM: "U.S." in all 370 subfields added to the list of things that can be in all-uppercase and yet are acceptable. (Actually a bug fix, resulting from a recent addition to report US two-character postal codes as an error.)\par
\tab\bullet  NUL only: the gay pulp fiction routine can be assigned to either the normal call number button, or to the 'move call number from bib to holdings' button.\par

\f0\b 2013 04 30 (version 1.6.93 and higher) \par\b0
\tab\bullet  NUL only: the call number button now handles the special scheme for the gay pulp fiction collection. To use this, check the corresponding check-box on the options panel for call numbers..\par

\f0\b 2013 04 27 (version 1.6.92 and higher) \par\b0
\tab\bullet  RDA and the toolkit document updated to illustrated use of the toolkit to create 034 fields from 670 data, which was strangely missing.\par
\tab\bullet  'RDA' button: New option, to omit 034 subfield $2 if it is 'other'. (Default value: include 034 $2 'other')\par
\tab\bullet  'RDA' button: Improvements to the handling of coordinates given as decimal degrees--in these, the hemisphere indication is implied rather than stated. Additional testing of the creation of 034 fields from data spun out of 670 fields doesn't turn up much of anything else to improve. Examples are requested of cases where the feature produces incorrect results, or no results at all.\par
\tab\bullet  'RDA' button: If you add an 034 field to an authority record based on text pulled from a 670 field in that same record, the toolkit attempts to assign the proper code for subfield $2, based on the text in 670 subfield $a; default value: "other".\par

\f0\b 2013 04 26 (version 1.6.92 and higher) \par\b0
\tab\bullet  NUL only: Toolkit no longer suggests that a videorecording with an 043 code for Africa might need to be relocated to the Africana collection.\par
\tab\bullet  'RDA' button: If you add a 370 field to a corporate/conference record from text in the authority record itself, it goes into 370 $e, not (as previously) 370 $a.\par

\f0\b 2013 04 26 (version 1.6.87 and higher) \par\b0
\tab\bullet  Correction review: new 'To clipboard' button copies the old heading to the clipboard; paste it into the Voyager cataloging client's search window to save yourself some typing.\par
\tab\bullet  Catalogers toolkit: New installations prepared for all the usual versions.\par
\tab\bullet  \b Twitter:\b0  Follow GaryLStrawn for announcements of bug fixes, new features, and so on.\par
\tab\bullet  Correction receiver: bug found in the correction of name/title subject headings that have more than $t, $n and $p in the title segment: the additional subfields disappear. New installers posted for the usual versions.\par

\f0\b 2013 04 25 (version 1.6.85 and higher) \par\b0
\tab\bullet  New authority: Bug introduced last week found and fixed. This bug affects new corporate name authority records, and results in the first indicator being set to "1"; if the heading consists solely of $a, this in turn results in the tag being set to 151. New installers will be available as soon as possible, but I have one more serious bug yet to track down. In the mean time, don't create any corporate name authority records! Or at least change the tags in new ones.\par
\tab\bullet  BAM: Fixed a bug that occurs when verifying an authority record. If you have selected the option to change "$w a" and "$w b" in 5XX fields into their RDA equivalents (with subfield $i) the toolkit formerly would change the first appropriate 5XX field, and leave the others alone. The toolkit now changes all appropriate 5XX fields.\par
\tab\bullet  BAM: Fixed a bug that occurs when verifying a name/title authority record. If an authority 4XX matches bibliographic 1XX+245, the toolkit now looks at 7XX fields with second indicator '2' in the same record; if the toolkit finds a match among these 7XX fields for the authority 1XX field, the toolkit considers the match of authority 4XX against bibliographic 1XX+245 to be a non-problem.\par

\f0\b 2013 04 24 (version 1.6.79 and higher) \par\b0
\tab\bullet  New installation packages for many current BatchCat versions available for pickup.\par
\tab\bullet  New authority record: Add 380 'Libretto' for records with name/title 100 field, and name/title 400 field ending in $s with 'Libretto'.\par
\tab\bullet  'Libretto' button: Additional fixes to the 'composer as librettist' feature, including a new option to control the addition of the work type qualifier to $a or $p depending on context. Documentation revised.\par

\f0\b 2013 04 23 (version 1.6.77 and higher) \par\b0
\tab\bullet  BAM: A bug in the toolkit prevented the addition of 510 fields for hierarchically superior bodies. Had this bug not been present, a different bug would have caused diacritics to be mangled. Both bugs are fixed.\par
\tab\bullet  RDA: new version of the RDA document uploaded. Among other things, this describes the latest addions to the 'libretto' feature.\par
\tab\bullet  'Libretto' button: Additional features for the 'composer also the librettist' button.\par
\tab\bullet  BAM: If the final 264 field in an RDA bibliographic record ends '].', the toolkit removes the unnecessary full stop.\par
\tab\bullet  BAM: (not really version-dependent): New tests defined for 046 subfields in authority records, filling an unintentional gap in coverage. New version of authvalid.cfg posted to the download site.\par

\f0\b 2013 04 22 (version 1.6.77 and higher) \par\b0
\tab\bullet  'Libretto' button: Options added, allowing for the user definition of appropriate texts for the type of musical work and type of accompanying text. (Defaults: 'Opera' and 'Libretto'). The tookit uses these texts in subfield $i, and, when needed, in parenthetical qualifiers for uniform titles.\par

\f0\b 2013 04 20 (version 1.6.77 and higher) \par\b0
\tab\bullet  'Libretto' button: Creation of authority record for the libretto written by the composer of an opera contains the appropriate 400 field.\par
\tab\bullet  BAM: Search for conflicts related to title main entry corrected (bug fix).\par
\tab\bullet  'Libretto' button: New check-box for retaining (or not retaining) 240 subfield $a in the libretto title when subfield $p is present. I'm not sure which is the correct usage (for rare things like the libretto for Das Rheingold) but this way you have the option; I just make sure that both possibilities work properly.\par
\tab\bullet  General: new option (on the General tab) to align the text in the toolkit's message window (the grey rectangle at the bottom) to the right rather than to the left. This may be of benefit for people who, like me, usually have the toolkit running off the left edge of the monitor.\par

\f0\b 2013 04 19 (version 1.6.77 and higher) \par\b0
\tab\bullet  'Libretto' button: A new 'composer is also the librettist' button helps untangle an additional category of pre-RDA bibliograpic record.\par

\f0\b 2013 04 19 (version 1.6.75 and higher) \par\b0
\tab\bullet  'fi': Define a new search prefix, 'jq' for "qualified title". The results from this search give the cataloger a one-stop view of titles beginning with given word or words, and allow them to assign a new uniform title that fits well amongst existing entries.\par

\f0\b 2013 04 18 (version 1.6.74 and higher) \par\b0
\tab\bullet  BAM: The toolkit's inspection of subfield $d in personal names was originally designed for authority records, and as it turns out does not map perfectly onto bibliogrpahic practice. (A non-RDA bibliographic record may contain a mixture of RDA and non-RDA personal name fields.) The test is revised, so that a non-RDA bibliogoraphic record may have $d in either format; a non-RDA authority record may only use pre-RDA conventions; an RDA record (bibliograpic or authority) must only use RDA conventions in subfield $d.\par
\tab\bullet  BAM: When adding '$e author' to a 100 field, the toolkit no longer removes a full stop that follows an uppercased letter.\par
\tab\bullet  BAM: new option for adding enhanced punctuation to 505 fields. This option switches on/off the use of subfield $g at space-colon-space. Default value: not checked (do not add $g at space-colon-space).\par

\f0\b 2013 04 14 (version 1.6.73 and higher) \par\b0
\tab\bullet  Libretto button: Substantial changes today and over the next few days. See revised documentation.\par
\tab\bullet  New authority record: option to convert bibliographic work/expression/manifestation 7XX fields into authority 5XX fields. When this feature was added, such fields were added in every case; there was no option. Option is on the 'Get started' sub-tab of the 'Authority-related' tab of BAM options. (Default: add the fields.)\par

\f0\b 2013 04 13 (version 1.6.72 and higher) \par\b0
\tab\bullet  Authority creation for a libretto: New option added on the 'Get started' sub-tab of the 'Authority-related' tab of BAM options. If this option is selected (default value: selected): When you create an authority record for what the toolkit considers to be a libretto, if the bibliographic record contains 700 fields for what appear to be joint authors of the libretto, the toolkit asks if any should be added to the authority record as name/title 400 fields.\par

\f0\b 2013 04 12 (version 1.6.72 and higher) \par\b0
\tab\bullet  \b Correction receiver:\b0 New installers being prepared to fix a big. Get a new version before you change any bibliographic X30 fields.\par
\tab\bullet  Libretto: There is a problem with librettos by two or more authors; the names of the librettists may be given in any order in a note. On the assumption that any authority record for the libretto by itself will have name/title 400 fields for the other authors, the toolkit now searches for an authority record with the assumed librettist+title as a 400 field. If the toolkit finds such an authority record, it searches the original bib record for the author from the authority record's 100 field as a 700, and if found, uses that instead of the librettist initially identified. If the identified librettist is in a name/title 400 field and the name portion of that authority record's 100 field does not appear as a 700 field in the original bibliographic record, the toolkit reports the problem to the operator for resolution.\par

\f0\b 2013 04 11 (version 1.6.72 and higher) \par\b0
\tab\bullet  BAM: Working in a new feature: if the primary access point is a title, detect cases where records in the local database indicate that a 130 field is needed. To make space for the options that will be required, I have slightly revised the Options panel for the BAM button. The "General" tabs are now called "Tests", the "Make changes" tabs are now just "Changes", and there is a new "Tests, pt. 4" tab. Finally, the "Subject systems" tab is now on the second row. Details on this new feature as implementation approaches.\par

\f0\b 2013 04 10 (version 1.6.72 and higher) \par\b0
\tab\bullet  BAM: Subfield $i is recognized as a valid subfield to occur before subfield $a in bibliographic 7XX fields.\par
\tab\bullet  BAM: When comparing illustration codes in the bibliographic 008 field to information in the 300 field, the toolkit recognizes the word 'genealogical' as well as its abbreviation.\par
\tab\bullet  BAM: A bug relating to nonfiling indicators in the code that replaces a bibliographic record that has 'small differences' from the form in the corresponding authority record has been fixed. This fix has spill-over into the correciton receiver. I have re-organized the code modules that constitute the batch correction engine, so that they can be used directly in a program, rather than as a separate DLL. This eliminates a major source of version problems: no longer must the cataloger's toolkit, correction receiver and authority loader all be re-issued simultaneously because of a change to the batch correction engine.\par

\f0\b 2013 04 09 (version 1.6.72 and higher) \par\b0
\tab\bullet  The $l and libretto buttons work together more smoothly. When dealing with an older record for a multi-lingual libretto, start with the 'libretto' button to adjust the primary and secondary access points, then flip to the 'Subfield $l' tab to deal with subfield $l. Starting with the subfield $l tab and then flipping to the libretto tab will not produce correct results.\par

\f0\b 2013 04 08 (version 1.6.72 and higher) \par\b0
\tab\bullet  'Libretto' button: Substantial additional development. Several options have been defined to go with this button. The 'RDA and the toolkit' document contains a description of this button; the revised document is available in the Documentation folder.\par
\tab\bullet  Elaborate editing panel: All records placed into this panel undergo a common suite of mofidifications, as described in the revised RDA document.\par

\f0\b 2013 04 06 (version 1.6.72 and higher) \par\b0
\tab\bullet  \b NEW BUTTON:\b0  I'm working on a 'libretto' button that will (with as little operator involvement as possible) 'flip' a pre-RDA bib record for a separately-published libretto with main entry for the composer. Ideas welcome.\par
\tab\bullet  '$l' button: If there is only one 041 $a code, the toolkit asks if it should copy the code from 041 $h into a second $a.\par
\tab\bullet  '$l' button: This rule is in effect if you approve a change to the 1XX+240 in a record and the original language is classical Greek (grc): If the database contains other records with the same 1XX+240, the program will silently change the 'gre' language code in those other records to 'grc' (unless, of course, the original item involves a translation from classical into modern Greek).\par
\tab\bullet  '$l' button: Now correctly removes nonfiling characters in the 130 and 240 fields.\par

\f0\b 2013 04 06 (version 1.6.71 and higher) \par\b0
\tab\bullet  RDA button: If you start from an authority record, then click the 'Get second record' button when the Voyager cataloging client shows another authority record, the toolkit picks up the authority 1XX as potential 372, 373 and/or 374 (depending) on the 'Suggestions' tab.\par
\tab\bullet  BAM: If the indirect subdivision form for a geographic name used in a bibliographic record does not match the form found in the 781 field of the corresponding authority record (assuming that there is such a record, and such a 781 field), the BAM report contains the code '@' to indicate the problem with indirect subdivision. (This is an existing code already used for other problems with indirect subdivision.) Example: the subject heading "Botany $z Ryukyu Islands" is labeled as an indirect subdivision problem, because the 781 field in the authority record for the Ryukyu Islands gives the indirect subdivision form as "$z Japan $z Ryukyu Islands.".\par

\f0\b 2013 04 05 (version 1.6.69 and higher) \par\b0
\tab\bullet  '$l' button: For bi-lingual 1XX+240 changes, the toolkit now identifies other records with the same conditions, and presents them for your approval. The toolkit can change all of the records at once. Revised documentation is available.\par

\f0\b 2013 04 03 (version 1.6.69 and higher) \par\b0
\tab\bullet  BAM: Validation rule added: RDA record cannot have 245 $h.\par
\tab\bullet  BAM: Toolkit no longer suggests that a terminal full stop might be unnecessary, if the 490 field text ends with a recognized abbreviation.\par
\tab\bullet  BAM: When testing a series in a bibliographic record, the toolkit reports an error if it can't draw a correspondence between the publisher(s) named in the authority record and the publisher(s) named in the bibligoraphic record. This scheme originally only dealt with the bibliographic 260 field, but is now expanded to include the bibligraphic 264 field.\par
\tab\bullet  BAM: The option to re-tag a 260 field as a 264 field no longer applies to 'serial' records.\par
\tab\bullet  '$l' button: Capability (added yesterday) to handle fields that contain subfield $6 has been successfully tested with right-to-left languages.\par

\f0\b 2013 04 02 (version 1.6.69 and higher) \par\b0
\tab\bullet  '$l' button: Now correctly handles fields that contain subfield $6; has been successfully tested with left-to-right languages.\par
\tab\bullet  BAM: bug fixed in routine that examines 300 $a for abbreviations, eliminating an unnecessary error message.\par
\tab\bullet  BAM generation of 505 fields: Added a few dozen lines of code to allow generation of a TOC from the very clear table-of contents layout used by dollarsandsense.org. To use this capability (once you've installed an appropriate toolit version, and assuming you've included an appropriate URL in an appropriate record), go to the BAM options, Make changes pt. 1 tab, and click the URL options button. Add a definition for 'dollarsandsense.org/bookstore', declare it to be a table of contents source, and give your preferred text for subfield $z or $3 in the appropriate box.\par

\f0\b 2013 04 01 (version 1.6.64 and higher) \par\b0
\tab\bullet  \b ALERT: \b0 There is a bug in recent versions of correct receiver. Happily, the bug causes the program not to do something that it should, rather than to do something that it shouldn't. This will require new installations for the correction receiver, cataloger's toolkit, and authority loader.\par
\tab\bullet  '$l' button: Additional tricks for handling classical and modern Greek, and for items that contain the same work in modern and pre-modern versions of the same language. (Example: an item that contains Chaucer's Canterbury tales both in the original Middle English and modern English.)\par
\tab\bullet  '$l' button: One of the tricks for handling classical Greek entails the definition of yet another configuration file, ClassicalGreekAuthorsAndWorks.cfg. A sample of this file is available at the download site, and it is described in the documentation.\par

\f0\b 2013 03 29 (version 1.6.63 and higher) \par\b0
\tab\bullet  '$l' button: If 240 $a or $t of a name/title heading is 'Selections', the toolkit inserts 'Works' and moves 'Selections' to subfield $k, in accordance with RDA practice. As is the case with other changes that the toolkit makes to a record when you click the '$l' button, the toolkit does not write this change to Voyager until you click the 'Save' button.\par
\tab\bullet  '$l' button: The toolkit shows the column of check-boxes under the '$f' caption in all cases, and provides a work area for the date to be used in subfield $f if requested. The toolkit uses a rather elaborate logic to set the default value for the $f check-boxes, as explained in the revised documentation.\par
\tab\bullet  BAM: if the ISBN (or other standard number) in a bibliographic record also exists in another record, each record is listed only once. (Because the toolkit makes multiple attempts for ISBNs and OCLC numbers, it occasionally happens that it finds the same record more than once.)\par
\tab\bullet  '$l' button: The toolkit chops any subfield of the 041 field that contains more than one code into separately-coded subfields. (Example: '$a frelat $h' becomes: '$a fre $a lat $h lat'.) There's no option for this; you want to do this anyway.\par
\tab\bullet  '$l' button: The toolkit now remembers (for the duration of the current session) that a particular work was originally written in classical or modern Greek; so it only asks the question once.\par
\tab\bullet  BAM: Added 'force' rule to bibvalid.cfg to re-tag a 243 field as a 240 field.\par
\tab\bullet  '$l' button: Added an option to re-tag a 243 field as a 240 field.\par

\f0\b 2013 03 28 (version 1.6.63 and higher) \par\b0
\tab\bullet  BAM: The toolkit recognizes that under RDA a series added entry and the corresponding series numbering example in authority 642 can (until a decision is handed down to the contrary) contain a roman numeral. The presence of roman numerals in both locations no longer causes the toolkit to report a discrepancy in the bibliographic series numbering. (The presence of a roman numeral in one place but not both will still cause the toolkit to report a discrepancy.)\par
\tab\bullet  Fancy editing panel: The new 'Save and close bib' button allows you to save a record to Voyager and close it in the cataloging client.\par

\f0\b 2013 03 28 (version 1.6.62 and higher) \par\b0
\tab\bullet  NUL ONLY: The call nuumber buttons reject a 300 subfield $c that does not contain any numerals.\par
\tab\bullet  Fancy editing panel: The new 'Save and BAM' button allows you to save a record to Voyager, and then BAM the record, with a single click.\par
\tab\bullet  '$l' button: New option regarding an 041 field generated by the toolkit. If you select this option, the toolkit will add the 041 field to the record-in-progress, and show you the record with the 041 field in bold. If you do not select this option, the toolkit will (as before) ask you if its proposed 041 field is correct. In either case, the toolkit will not allow you to use the features of the '$l' button unless the record ends up with a suitable 041 field. The 'RDA and the toolkit' document is being revised to show the changes.\par
\tab\bullet  Options: Most of the options pertaining to the handling of multi-lingual subfield $l moved to a new panel, for the '$l' button. The toolkit uses most of these options both during BAM, and when you use the '$l' button.\par
\tab\bullet  Toolkit news: The behavior of the news feature was changed slightly. The toolkit now fetches the latest news from the server each time you ask the tookit to display the news. This means that you always see the most recent news. (In earlier versions, the toolkit just fetched the news once per session, which meant that you saw the same news all day, unless you closed the toolkit and re-started it.)\par

\f0\b 2013 03 27 (version 1.6.57 and higher) \par\b0
\tab\bullet  \b ALERT: \b0 There is a strange and severe problem with batch changes to the bibliographic 130 field. Investigation has just revealed the source of the problem (stupid programmer error, as usual), and re-builds of installation packages are underway. (Re-building the installation packages will take several hours.) You will need new installations of both the toolkit and the correction receiver. Do not make batch corrections that can involve 130 fields until you have new versions of both programs.\par
\tab\bullet  '$l' button: The toolkit searches the entire text of each new or modified field for a matching authority 1XX field. If there is no matching authority 1XX for the complete bibliographic field, the toolkit shows the field in boldface in its display. This is your indication that further (authority-related) work may be required.\par
\tab\bullet  BAM: Since 1999, the toolkit has (correctly) ignored the fact that a bibliographic 1XX+245 matched an authority 4XX field, as long as the bibliographic record also contained an appropriate 240 field. But under RDA, for multi-lingual items, the 'correct' access point is given in an analytical 7XX field. The toolkit now accepts such a record construction as valid. (The line in the BAM report for the 1XX+245 is marked with the code that means "matches a 4XX, but that's OK," and the text of the 1XX+240 is given in lowercase letters.)\par
\tab\bullet  Revised version of 'toolkit and RDA' document uploaded.\par

\f0\b 2013 03 26 (version 1.6.57 and higher) \par\b0
\tab\bullet  '$l' button: An annoying problem that caused some of the buttons and boxes from the 'Subfield $l' tab to appear on other tabs (on top of things proper to those tabs) fixed.\par
\tab\bullet  RDA button: If the primary record is an authority record and the secondary record is a bibliographic record, 490 fields now appear as 430 fields on the 'suggestions' tab.\par
\tab\bullet  '$l' button: Behavior of the 'CLR' button changed. Formerly, the 'CLR' button cleared the current row and all following rows in the display; now, each 'CLR' button only clears its own row.\par
\tab\bullet  '$l' button: The toolkit now recognizes 'and' in subfield $l (incorrectly used instead of an ampersand) at all relevant spots, not just some of them.\par
\tab\bullet  '$l' button: If a bibliographic record does not contain an 041 field and contains a single bi-lingual subfield $l, the toolkit will in many cases suggest an 041 field. If you accept the proposed 041 field, the toolkit will display the '$l' editing panel. If the toolkit is not able to create an 041 field for you, or if the proposed 041 field is not correct, you will need to supply an appropriate 041 field before you can use this button.\par

\f0\b 2013 03 25 (version 1.6.51 and higher) \par\b0
\tab\bullet  'BAM: Handling of dual-language $l during BAM has been turned off. Until new versions are available, users should not take the option of automatically splitting dual-language $l during BAM. A revised function will be available in the near future.\par
\tab\bullet  '$l' button: Very interesting bug found and fixed. The bug appears only to affect the Greek language (I can explain this if you like but it takes more space that is available here). WORK-AROUND: Until new versions are issued, if Greek is involved, simply click the drop-down arrow next to the language name and select either classical or modern Greek; or type just 'Greek' into the box if you don't want the parenthetical qualifier. New column of check-boxes added, to retain a parenthetical qualifier in a language name.  Revised documentation posted.\par

\f0\b 2013 03 24 (version 1.6.45 and higher) \par\b0
\tab\bullet  BAM: The toolkit can automatically split many pre-RDA dual-language access points (those with an ampersand in subfield $l). This work is controlled by a new set of BAM options on the 'Make changes, pt. 3' tab.\par
\tab\bullet  \b New button:\b0 The new '$l' button helps you work directly with access points with subfield $l containing two languages joined by an ampersand, or containing 'Polyglot'. This button leads to a new tab on the fancy editing panel. This work is controlled by a new set of options--the same ones that control the toolkit's automatic handling of many instances of '&' in subfield $l during BAM.\par
\tab\bullet  BAM: RDA-related options for bibliographic records are arranged in a more reasonable manner.\par
\tab\bullet  BAM: New stanza 'LanguagesByCodeSubfieldL' in the codes.cfg file. New version of the file available at the download site, with a model stanza.\par
\tab\bullet  The 'RDA and the toolkit' document updated to describe the new features and their controlling options.\par

\f0\b 2013 03 23 (version 1.6.45 and higher) \par\b0
\tab\bullet  BAM: The abbreviation 'U.K.' in any subfield of the authority 370 field is now recognized as valid.\par
\tab\bullet  RDA button: Several enhancements to the creation of an authority 034 field from coordinates in a 670 field. (There were also fixes of several bugs in the creation of 034 fields discovered along the way.) The toolkit now skips common abbreviations such as 'lat' and 'lon', and makes a brave attempt at handling decimal degrees, minutes or seconds correctly. If a coordinate contains decimals, the toolkit does not translate the hemisphere indicator (N,E,W,S) into a '+' sign or '-' sign in the 034 field; it uses the hemisphere indicator. Example: the highlighted text "LAT: 09\'b0 48.3' N LON: 079\'b0 4.7' E" becomes this 034 field: "$d E07904.7 $e E07904.7 $f N00948.3 $g N00948.3".\par

\f0\b 2013 03 21 (version 1.6.44 and higher) \par\b0
\tab\bullet  BAM: When creating 370 subfield $c from the text 'N.Z.' at the end of some other 370 subfield, the toolkit now uses the LC-mandated abbreviation, rather than the full name 'New Zealand' (bug fix).\par
\tab\bullet  BAM: If subfield $e was preceded by a comma itself preceded by a full stop, the toolkit formerly displayed a message suggesting the possibility of a problem. (Example: the bibliographic 100 field 'Strawn, Gary L., $e author.' would cause the toolkit to suggest that the punctuation might require attention.) This behavior has been adjusted; there is now no message at all if the text before subfield $e ends in a recognized abbreviation (including an initial). The toolkit still suggests the possibility of a problem if the full stop is not part of a recognized abbreviation. (Example: the 100 field 'Strawn, Gary., $e author.' will cause the toolkit to suggest that the punctuation may require adjustment.) If you see such a message remember that it is only a suggestion of a problem, and should not be taken as calling in every case for a corrective action on your part.\par
\tab\bullet  The 'news' panel now (again!) shows the date of the earliest item in the display.\par

\f0\b 2013 03 20 (version 1.6.29 and higher) \par\b0
\tab\bullet  BAM: The 337 field supplied by the toolkit when 245 $h contains 'videorecording' changed from 'projected' to 'video'; corresponding code changed from 'g' to 'v'.\par
\tab\bullet  New installation packages prepared for popular recent BatchCat versions, making this 'news' feature available to most users.\par
\tab\bullet  BAM: Change to parsing of 502 fields: better handling for 502 fields that contain more than one set of double hyphens. Example: Thesis (Ph.D.)--University of Wisconsin--Madison, 2009. This brings the successful yield to about 80% in Northwestern's database; your results will vary.\par
\tab\bullet  BAM: 'leaves' added to the list of texts in 300 $a that can trigger the generation of 'volume' in the 388 field. Revised 'RDA and the toolkit' document posted to the download site.\par

\f0\b 2013 03 19 (version 1.6.28 and higher) \par\b0
\tab\bullet  BAM: Some time before this date, option to re-tag the bibliographic 260 field as 264 was added (exact date not recorded). This option is on the 'Making changes, pt. 2' tab of the  BAM configuration. The toolkit makes this change for all bibliographic 260 fields, not just those in RDA records. The toolkit makes no attempt to adjust the contents of the re-tagged field.\par
\tab\bullet  BAM: Configuration files authsup.cfg and bibsup.cfg changed to sort alphabetic 034 subfields into alphabetical order; this appears to be particularly important for $d, $e. $f and $g (the most commonly-used subfields). New versions of configuration files available at download site.\par
\tab\bullet  RDA button: When adding an 034 field, the toolkit now supplies $d, $e, $f and $g if the source data contains point coordinates rather than a bounded area.\par
\tab\bullet  Toolkit 'news' feature: The program version number is included with the date for each day's group of fixes and enhancements. The version number of the local program is displayed at the bottom of the news panel for comparison. It is not possible to add the version number retrospectively to earlier news items.\par
\tab\bullet  Romanization button: When creating a new 880 field from an existing vernacular field tagged as a 'regular' field, the toolkit re-tags the existing vernacular field as 880, and creates a new field with the 'regular' tag.\par
\tab\bullet  Toolkit 'news' feature changed, to use a file on a server rather than statements within the program. This allows for the broadcast of news without requiring a new program installation.\par
\tab\bullet  BAM: Bug fix; record containing 'shadow references' is no longer saved to Voyager.\par

\b 2013 03 16\par\b0
\tab\bullet  BAM: When splitting a single-subfield 502 field into new subfields, the toolkit corectly recognizes dates that consist of month and year, month, day and year, or season and year.\par
\tab\bullet  RDA button: Add '034' radio button to the 'Texts' sub-tab on the 'Authority' tab. To use, highlight coordinate information in an authority 670 field, select the '034' radio button, then click the 'Add text from record on left' button.\par
\tab\bullet  RDA button: If the secondary record is a bibliographic record, the toolkit copies any bibligoraphic 034 field into the 'Suggestions' sub-tab of the 'Authority' tab. If there is no bibliographic 034 field but there is a 255 field, the toolkit uses its standard conversion routine and proposes an 034 field based on the 255 field.\par

\b 2013 03 15\par\b0
\tab\bullet  BAM: Fix to bug recently introduced into the 'shadow references' scheme.\par
\tab\bullet  BAM: Option added to insert 'enhanced' subfield codes ($g, $r, $t) into 505 fields that contain only subfield $a. The option is on the 'Make changes, pt. 2' tab of the BAM configuration. This option is by default not turned on, so if you want the toolkit to add enhanced coding to your 505s you'll have to check the box yourself.\par

\b 2013 03 14\par\b0
\tab\bullet  BAM: Enhancments to the scheme for splitting a single-subfield 502 field into new subfields: Dates given as month, year or month, day, year are now separated off correctly. Additional texts are recognized as indicating that the program should do nothing; for example, 'respontent' and 'under the title'. Toolkit does not attempt to do anything with 502 fields that contain more than one double-hyphen. Toolkit now ignores all square brackets in the 502 field. A terminal comma no longer causes the parser to mis-identify the date.\par
\tab\bullet  NUL ONLY: BAM: For 'Northwestern' 502 fields, there are even more enhancements, mostly dealing with variant ways of indicating the department or school.\par

\b 2013 03 13\par\b0
\tab\bullet  Romanization button: an internal test for the presence of vernacular data in a variable field was switched; it now uses the current method. There may yet be spots at which the older method is still in use, yet to be discovered.\par
\tab\bullet  BAM: Change to all messages relating to punctuation that precedes subfield $e.\par
\tab\bullet  BAM: New validation rule for bibliographic records: if the 040 field does not contain subfield $b, toolkit adds '$b eng'. (Revised bibvalid.cfg file posted to download site.)\par

\b 2013 03 12\par\b0
\tab\bullet  Romanization button: '/r' now added to the end of subfield $6 in program-created 880 fields for right-to-left languages. This entails an addition to the General stanza of the romanization configuration file for right-to-left languages. Revised configuration files for Arabic and Hebrew are available at the download site.\par
\tab\bullet  Scheme for 'NACO normalization' adjusted, to retain the '@' character. This was done for authority record n 2012204748, so that the 400 field was not reported as being a duplicate of the 100 field. The 400 field does not show up in the BAM report, however, because in the Voyger system the normalized forms of the 100 and 400 remain the same.\par
\tab\bullet  RDA authority records for families (BAM, and new authority record): Toolkit adds required 667 field if missing, and sets 008/15 (subject usage) to 'b'.\par
\tab\bullet  New RDA authority record: Option added, to create 381 field for all unnumbered series. By default, this option is selected. When this option is selected, 008/13=b gives 'Unnumbered' wheneveer 008/12 contains 'a', 'b' or 'c'.\par
\tab\bullet  New RDA authority record: Option added, to create 380 field for all series. By default, this option is selected. When this option is selected, 008/12=a gives 'Series', 008/12=b gives 'Multi-part item' and 008/12=c gives 'Series-like phrase'.\par
\tab\bullet  Toolkit news display: Click of 'Cancel' button now handled correctly (bug fix).\par
\tab\bullet  New authority record: when subfield $e is dropped from a name/title heading (including 1XX+240), the comma before subfield $e is converted into a full stop.\par
\tab\bullet  BAM: comma before subfield $e in a name/title heading (including 1XX+240) is no longer reported as a 'small difference' (with code '$').\par
\tab\bullet  Toolkit news display shows the date/time the news was last viewed.\par
\tab\bullet  BAM: Toolkit no longer removes full stop from subfield $e in certain circumstances (bug fix).\par

\b 2013 03 11\par\b0
\tab\bullet  BAM: Toolkit no longer complains about X00 subfield $d that contains 'jin shi'.\par
\tab\bullet  BAM: Toolkit no longer attempts to create an authority 370 field from $c in a conference heading, if the record already contains a 373 field. (Previously, only tested for the presence of a 370 field.)\par
\tab\bullet  BAM: When presented with an RDA CIP 300 $a containing 'p. cm.' the toolkit replaces it with 'pages cm.'\par
\tab\bullet  BAM: For an RDA record, the toolkit no longer complains about a duration in 300 subfield $a that contains a recognized abbreviation. For example, there is no longer a complaint concerning an unrecognized abbreviation in this RDA 300 $a text: '1 videodisc (113 min.)'\par
\tab\bullet  BAM: Toolkit no longer complains that an RDA record lacks 245 $h. This required several changes to bibvalid.cfg; new version available at download site.\par

\b 2013 03 09\par\b0
\tab\bullet  When you click the toolkit's button to go to the options panel, the toolkit's icon no longer disappears from the Windows taskbar (the row of icons at the bottom [or side] of the screen).\par
\tab\bullet  BAM: Change to the scheme to generate 'shadow references': If the $d subfield in a personal name begins with a hyphen, transform into subfield $d that begins 'd.'. For example, '$d -1952' becomes '$d d. 1952' in a shadow reference.\par
\tab\bullet  BAM: Toolkit gives an error message if subfield $l in an access field begins with a lower-case letter.\par
\tab\bullet  BAM options panel no longer displays 'Text1' as a template file name, if none is defined. (Bug fix.)\par
\tab\bullet  New version of the 'RDA and the toolkit' document posted to the download site. No major additions, just clarification and rearrangement.\par
\tab\bullet  BAM: When parsing a 502 field into separate subfields, the toolkit skips any 502 field that contains the text 'originally.'\par
\tab\bullet  BAM: No longer any complaint about punctuation in any bibligoraphic 2XX $e (bug fix, really)\par
\tab\bullet  BAM: A new test in bibvalid.cfg warns of use of the 260 field in RDA records. (Revised file available at download site.)\par
\b 2013 03 08\par\b0\tab\bullet  BAM: error message for hyphen-comma before subfield $e added.\par\tab\bullet  'Go to download site' button added to options panel; this opens the download site in your preferred web browser.\par\b 2013 03 07\par\b0\tab\bullet  'News' feature added to the Options panel (this is what you're looking at right now)\par\tab\bullet  The download site has been reorganized: I moved various documentation files, and a fresh set of configuration files, to separate folders, in an effort to make things clearer.\par\tab\bullet  NUL-only document on toolkit configuration for RDA available at download site.\par\tab\bullet  RDA button: you can (on the options panel) define constant texts for frequently-used authority 37X fields; when you use the RDA button, the texts you define appear amongst other fields you can add to a record\par\tab\bullet  RDA button: there's a new button on the 'Texts' sub-tab of the 'Authority' tab of the fancy editing panel, with the caption 'Add text from record on left.' Use this button to convert text in an authority record into an RDA field in the same record: highlight text in the record on the left, select the radio button for the appropriate tag, and click the 'Add text from record on left' button.\par\b 2013 03 05\par\b0\tab\bullet  Linking fields button: icon changed to three links of a chain.\par\tab\bullet  BAM: Option to convert 510 with $w a/b to use subfield $i. If you select this option, the toolkit will convert a 510 or 510 field with '$w a' or '$w b' into a 510 field with '$w r' and new text in subfield $i.\par\tab\bullet  BAM: Option to convert 530 with $w a/b to use subfield $i. If you select this option, the toolkit will convert a 530 field with '$w a' or '$w b' into a 530 field with '$w r' and new text in subfield $i.\par\tab\bullet  Fancy editing panel: title-casing now correctly handles apostrophe-s at end of words. (Until this fix, the toolit considered the 's' following the apostrophe as a separate word.)\par\b 2013 03 04\par\b0\tab\bullet  New authority records: In new RDA authority records, 400 fields no longer contain subfield $q.  If subfield $q is needed in a particular case, you can add it yourself later.\par\tab\bullet  Linking fields: Program-generated linking fields now use the subfield $i code for introductory text, instead of $c.\par\b 2013 02 25\par\b0\tab\bullet  BAM: Subfield $e (non-conference headings) is tested as coded a subfield only for RDA records; the toolkit does not test subfield $e in non-RDA records.\par\tab\bullet  BAM: Subfield $j (conference headings) is tested as a coded subfield only for RDA records; the toolkit does not test subfield $j in non-RDA records.\par\tab\bullet  BAM: Improved handling of terminal full stop or comma in $e (this is just a bug fix)/$j\par\tab\bullet  BAM: 'Centuries' recognized as a valid thing to appear in subfield $d of headings for families.\par\b 2013 02 23\par\b0\tab\bullet  New authority records: Generate 046 field in a series authority record if the new series appears to be established from volume 1 (determined by subfield $v, or the 640 field)\par\tab\bullet  New authority records: Option to add a 377 field to all series records even if subfield $l is not present in the 1XX field.\par\tab\bullet  New authority records: The toolkit no longer creates a 377 field for '$l Polyglot' (bug fix)\par\tab\bullet  Romanization: New 'add parallel RTL field' button. If you click on a romanized variable field in the record and then click this button, the toolkit creates a parallel 880 field for the romanized field, with the marker '/r' at the end of subfield $6. The presence of this marker allows you to use the 'right-to-left editing' button, even if the field does not (yet) contain any right-to-left text.\par\b 2013 02 22\par\b0\tab\bullet  BAM: When checking the order of $v and $x subfields in 490 fields, the toolkit uses the same rule for RDA records that it uses for AACR2 records ($x should come before $v). \par\tab\bullet  BAM of linking fields: When filling out a minimal linking field that contains just 'number' subfields, the toolkit can get data directly from OCLC if the linking field contains an OCLC number and if there is no matching record in Voyager and if you have defined a Z39.50 connection for OCLC.\par\tab\bullet  BAM, and new authority records: Generate a 381 field from $s in learly every case, even when not the last subfield (bug fix)\par\tab\bullet  RDA: When generating 510 'hierarchical superior' fields, test new fields for duplication against all 510 fields in the record, without regard for any subfdield $i text\par\b 2013 02 21\par\b0\tab\bullet  New authority records: Supply 380 'Series' for series records, if nothing else is possible\par\tab\bullet  New authority records: Supply 381 'Unnumbered' if the series heading contains '(Unnumbered)'\par\b 2013 02 20\par\b0\tab\bullet  RDA: Eliminate the former rule that prevented generation of 510 'hierarchical superior' fields when references are 'unevaluated.' Because the toolkit must find a 110 that matches all such potential 510 fields, the value of the reference evaluation byte is actually irrelevant.\par\b 2013 02 17\par\b0\tab\bullet  Thesis note (502 field): The toolkit returns a more useful message if the 502 field has already been parsed into individual subfields\par\b 2013 02 12\par\b0\tab\bullet  Options for the 4XX, 643 and/or 670 buttons: use the new fancy editing panel instead of the original (simpler) technique.\par\tab\bullet  Linking fields: The button on the fancy editing panel to create the 'reverse' linking field now works if there is only one linking field, even if you don't click on the field. (If there is more than one possibility, you still have to identify the field in question.)\par\tab\bullet  Many options related to the RDA-ization of bibliographic records added; see the separate document on RDA and the cataloger's toolkit at the download site.\par\tab\bullet  Fancy editing panel: Propose a 670 field on the 'Authority' tab if the base record is an authority record and the second record is a bibliographic record.\par\tab\bullet  Fancy editing panel: 'Authority' tab added, available via the RDA button (as well as the linking fields button, the romanization button, and so on). Use the RDA button to load an authority record into the panel; you can directly add certain fields to that authority record (046, 375, 377), and you can add fields to that record based on a second (bibliographic or authority) record.\par\b 2013 02 10\par\b0\tab\bullet  BAM: The validation of 372 and 374 fields now correctly handles (that is, complains about) three hyphens in a row (!)\par\b 2013 02 08\par\b0\tab\bullet  BAM: Abbreviations are no longer expanded when they appear in in vernacular fields.\par\b 2013 02 07\par\b0\tab\bullet  Fancy editing panel: The button on the 'romanization' tab to create a parallel 880 field now only replaces $a with '*'. Formerly, it replaced the text of all subfields with '*'. In quite a few cases, subfield $a is the one that you're going to replace with vernacular text; but in any case, you have to save the record and finish it in Voyager.\par\tab\bullet  NUL ONLY: Call number button: Call numbers in holdings records containing 'inquire' and 'use only' are now recognized as not being 'real' call numbers.\par\b 2013 02 06\par\b0\tab\bullet  BAM: During validation of authority 3XX fields, the toolkit ignores series authority records.\par\b 2013 02 04\par\b0\tab\bullet  BAM: Options added that tell the toolkit to expand abbreviations in certain fields (such as 'et al.' in 245 $c, and 'ill.' in 300 $b). See the documentation on RDA and the toolkit at the download site.\par\tab\bullet  BAM: Option added to automatically generate bibliographic 336-338 fields.\par\b 2013 02 01\par\b0\tab\bullet  NUL ONLY: Call number button: Code in 043 field for South Sudan is now recognized.\par\b 2013 01 15\par\b0\tab\bullet  Linking fields button: New button defined (icon: 76X-78X). This button replaces the never-finished 'print acquisitions' button). This button leads to the same fancy editing panel as the 'romanization' button; just starts on a different tab.\par\tab\bullet  BAM: a comma is now called for before $e in RDA records.\par\b 2013 01 13\par\b0\tab\bullet  Fancy editing panel: on the 'romanization' tab, add 'add parallel field' button. Click on a variable field in the record to which you wish to add a parallel (880) vernacular field, then click this button. The toolkit creates an 880 field, properly linked to the original field via subfield $6. (This means you don't have to deal with the mechanics of subfield $6 on your own.) Save the record and return to Voyager to finish the vernacular field.\par\b 2013 01 12\par\b0\tab\bullet  BAM: Options added for handling of bibliographic 33X fields. The toolkit can supply subfield $b if only $a is present, or supply $a if only $b is present; if $a or $b is repeated, the toolkit can create separate fields; the toolkit can add subfield $2 if it recognizes the term or code in $a or $b.\par\tab\bullet  BAM: The toolkit collapses repeated identical validation error messages into a single message, with a counter. (For example, if all of the $d subfields in the 4XX fields of an authority record have the same error, you get one message, with a counter.)\par\tab\bullet  BAM: The toolkit enforces the rule for RDA records regarding the full stop (or its lack) after 'cm' in the 300, depending on presence/absence of a 490 field.\par\tab\bullet  BAM: The toolkit no longer tests punctuation, abbreviations, etc., in suppressed authority 4XX fields.\par\tab\bullet  BAM: THere is a 'field order' instruction available (in the ExtendedFieldOrder stanzas of the authsup.cfg and bibsup.cfg configuration files) for the 33X fields. The code 'Rda33x' means: the primary sort is by the contents of subfield $3, then by the tag. For an example, see the bibsup.cfg file in the configuration folder at the download site.\par\b 2013 01 11\par\b0\tab\bullet  BAM: Expansive new routine for handling RDA data, depending on options. Initially dealt with the 33X fields (vastly improved over the next few days); later options allow for addition of '$e author' to the bibliographic 100 field, conversion of bibliographic 260 field to 264, and conversion or authority 5XX '$w a' and '$ b' to text strings in $i.\par\tab\bullet  NOTE: the toolkit's handling of 33X fields during BAM uses the new configuration file 'RdaCodes.cfg'. For an example, see the configuration folder at the download site.\par\b 2013 01 09\par\b0\tab\bullet  Fancy editing panel: on the 'romanization' tab, there is a new 'edit right-to-left panel' for handling Arabic and Hebrew text. This labeled display allows you to see clearly which characters are present in a field in their input order, and to manipulate the characters without being confronted with right-to-left and left-to-right issues.\par\tab\bullet  Fancy editing panel: the 'text labels' display gives text labels for Arabic and Hebrew characters.\par\tab\bullet  Fancy editing panel: on the 'capitalization' tab, the button for uppercasing a whole string now skips over subfield codes (bug fix)\par\b 2013 01 08\par\b0\tab\bullet  Fancy editing panel: on the 'capitalization' tab, there are new 'lowercase whole thing', 'uppercase whole thing', 'sentence case', and 'title case' buttons.\par\tab\bullet  NOTE: the 'title case feature' on the 'capitalization' tab of the fancy editing panel uses new configuration files. There is a new 'TitleCaseFiles' stanza in RomanizationMaster.cfg, and one or more language-based titles. See the examples in the configuration folder at the download site.\par\b 2013 01 07\par\b0\tab\bullet  Batch corrections: The toolkit has a new button (icon: big red cross with the Cyrillic 'ia' character in the middle). This button allows you to define a batch correction to vernacular (880) fields. If you want to use this new feature, you must also get a new version of the correction receiver program.\par\b 2013 01 02\par\b0\tab\bullet  BAM: the validation of authority 37X fields is now limited to particular vocabularies for particular fields. (Example: the toolkit only validates subfields of the 370 field against LC/NACO and LCSH authority records.)\par\tab\bullet  New authority records: option to add 'RDA' fields to non-RDA records.\par\tab\bullet  New authority records: define a default and neutral field-order definition to overcome a problem encountered by ExLibris. (This is a bug fix for a problem only seen by the people who use the authority generator built into the Voyager cataloging client, which is the same one included in the toolkit. For toolkit users, this default value is immediately overridden by the field-order definition in your authsup.cfg configuration file.)\par\b 2012 12 31\par\b0\tab\bullet  Internal routine for removing an initial article: If the removal of the article (based on the value of a non-filing characters indicator) leaves the title with no text at all, then return a special code. This is really just a bug fix applied to cases (such as found in LC/NACO record n 2011031406) where the toolkit is testing titles for potential initial articles. (In this record 'les' looks just like a French initial article, but there is nothing else in the title.)\par\tab\bullet  BAM: Added several tests on X00 subfield $d that does not contain a hyphen, to catch more date subfields that are not well-formed. (The tests differ, depending on whether the record is RDA or not.)\par\tab\bullet  RDA: When attempting to generate a 370 field from X11 subfield $c, do nothing if $c contains 'and', or a semicolon.\par\b 2012 12 29\par\b0\tab\bullet  BAM: a new results code (the right parenthesis) added to indicate the presence of a 'heading cannot be used undfer RDA' 667 field in the matching authority record.\par\tab\bullet  RDA: When attempting to generate a 370 field from X11 subfield $c, discard 'etc.' at end of the subfield.\par\b 2012 12 26\par\b0\tab\bullet  BAM: test for an initial uppercase character following the opening parenthesis in X00 subfield $c.\par\tab\bullet  BAM: test authority access fields (1XX, 4XX, 5XX) for a terminal comma. (You'd be surprised how often this happens!)\par\tab\bullet  RDA: when verifying a text from the authority 370 field: if the match is on an authority 151 field and if the subfield's text is one that ought to be abbreviated, act as if the match were instead on a 451 field. (Example: if 370 $c contains 'United States', the toolkit pretends that it found a match on a 451 field, and uses the '!' verification code; the 370 $c should contain 'U.S.')\par\b 2012 12 24\par\b0\tab\bullet  RDA: If the authority heading contains subfield $f, use that date to generate the 046 field.\par\b 2012 12 22\par\b0\tab\bullet  BAM: an invocation of special test #14 can now have '*' to indicate 'count them all'. (For an example, see the test of 370/a in the authvalid.cfg file available in the configuration at the download site. This particular test means that an authority record should show only one place as the place of birth.)\par\tab\bullet  RDA: When generating a 377 field, also recognize a number of languages that appear differently in the MARC list (chiefly, early versions of modern languages).\par\tab\bullet  RDA: Do not generate a 377 field if the language code is 'grc' or 'syr', except for Bible headings. (The terms 'Greek' and 'Syriac' in subfield $l are otherwise ambiguous.)\par\b 2012 12 21\par\b0\tab\bullet  RDA: Do not add an 046 field to an authority record for a '(Spirit)' heading.\par\b 2012 12 20\par\b0\tab\bullet  Transformer tool: 'conditional comma' instruction added. This allows the tool to insert a comma at the end of a subfield only if certain conditions are met.\par\tab\bullet  RDA: When generating 510 'hierarchical superior' fields, do not generate a 510 for an organization that is itself hierarchically superior to another 510 in the same record. (For an example, consider n 81138628. Since the Wharton School is (as determined by its own authority record) itself subordinate to the University of Pennsylvania, the correct 510 for a hierarchical superior in this record is Wharton School, and not also the University of Pennsylvania.)\par\b 2012 12 19\par\b0\tab\bullet  RDA: When generating a 377 field, if the language code in the source bibliographic record is a code for a collective language group, also include the name of the specific language in subfield $l. (For the toolkit's purposes, a language group is a defined MARC value whose name includes 'languages' or '(other)'.)\par\tab\bullet  RDA: When generating a 510 'hierarchical superior' field, the second indicator is always blank (bug fix, really)\par\b 2012 12 18\par\b0\tab\bullet  RDA: Only attempt to generate a 368 field if the authority 1XX field represents a name alone. (No 368 fields for name/title headings, for example.)\par\b 2012 12 17\par\b0\tab\bullet  RDA: When generating a 510 'hierarchical superior' field (remembering that the toolkit must find a matching 110 in its own authority record for each possible 510 field): the matching authority record may not yet have received RDA-related changes, so a second search is often necessary to find a match.\par\b 2012 12 11\par\b0\tab\bullet  BAM: If a term in an authority 37X field is a single word, it may not match a personal name authority record. (A match of a single word on a topical or geographic authority record is OK.)\par\tab\bullet  Transformer tool: box for 'new tag' added to the definition of a transformation.\par\tab\bullet  Transformer tool: the indicator value '#' means 'blank'\par\tab\bullet  Transformer tool: a string of subfield codes can be given within double quotes\par\b 2012 12 10\par\b0\tab\bullet  RDA: When devising searches for a 510 'hierarchical superior' field, the parenthetical qualifier in the last subfield of the 1XX field may not be present in the last subfield of 4XX field; allowance is made for this possibility. (Example: no2001085730, where the '(U.S.)' in the 110 is not present in 410 fields that show hierarchical relationships.)\par\b 2012 12 02\par\b0\tab\bullet  RDA: only add 510 'hierarchical superior' fields if *all* of the putative additions to one record find matching 110 fields in other records. (The scheme for finding matches has received significant improvements over time; some of these improvements are noted at other points in this news panel.)\par\b 2012 12 02\par\b0\tab\bullet  BAM: add $2 codes to authority 37X fields if the text in subfield $a is recognized.\par\par}