Connexion Client Enhancement Request from the OCLC CJK Users Group  March 6, 2013

Responses supplied by OCLC March 14, 2013, are in italics following each bullet

•NAR/SAR review mechanism, such as reviving 952 field used in OCLC Passport

oCurrently available in the Client.  See “Exchange Records for Peer Review” in the Connexion Client help.  The 952 field is not the mechanism used. 

•Spell-checking function to authority records

oCurrently available in the Client.  You need to customize Spell Check to get it to check the fields in the authority records.  Go to Tools, Options, Spelling, Fields to Check – then add in 100, 400, 667, etc. for use in authority records.  The fields automatically set up do only apply to bibliographic records. 

•In the authority record, can the institutional symbol in 040 field show its full name when we lay mouse over it like it for the bibliographic record?

oWill consider as a future enhancement.  The codes are MARC institution codes and not OCLC symbols, which means different programming is needed. 

•Add warning function when authority 4XX in NAF normalizes the same as 1XX in another record in NAF

oWill consider for the future. 

•Some oddity in NAF indexing: search results are not exactly alphabetical order; or selected headings linked to totally different records

oPlease provide specific examples, so that we may examine what is happening

•Problem with two character original script search in NAF using standard search box, rather than browse search box (one or more than three character(s) seems fine, but … )

oPlease provide specific examples, so that we may examine what is happening

•Include our CJK Toolkit in the OCLC website or a link to Connexion client

oPlease confirm that the Toolkit as this link is the one referred to:

https://eastasianlib.org/oclccjk/oclccjk/Toolkit.html

       OCLC would be happy to add text to the OCLC website at:

https://www.oclc.org/connexion/features/nonlatin.en.html. 

      If this is agreeable, please work with David Whitehair on the specific text you would

      like added to the OCLC website along with this link. 

•A global/batch update function for the local save files, such as batch delete, find, and/or replace a certain string across the records in the whole file with one single request, apply one macro to all records in the file at a time, etc.

oWill consider for the future. 

•Undo function for unlimited steps as the one in Office Word

o Will consider for the future. 

• Can OCLC create macros/drop-down lists for all controlled vocabularies/codes/terms, e.g. relationship designators, in the variable fields?  A good model to follow is exactly like the existing fixed fields and 33x macros.

oWe are considering preparing such a macro.  However, we will likely wait until some of the relationship designator lists are expanded.  Or, if someone else wants to create such a macro and share it, they are welcome to do so. 

• Automated punctuation filling in ISBD

oIn the future OCLC will provide a non-MARC editor and punctuation will not need to be supplied manually in that editor.  Also, the role of punctuation in the Bibliographic Framework initiative is unknown at this time. 

•Invalid characters and errors: instead of receiving an error message, the invalid characters are just highlighted.  It’s very cumbersome to count where that error occurs.

oUnder consideration for the future

•Local save file search: When searching local save file, using Romanized form doesn’t work always like searching WorldCat. Is it something to do with diacritics?  With or without diacritics, the search results seem different in the searches in both online and local save files. I guess that’s why we have “Enter Diacritics …” bottom in the both search windows. But then the regular WorldCat search also has “Enter Diacritics …” button, but it doesn’t seem make difference in results with or without diacritics. Is this true? Then, why?

oPlease provide some examples so we can figure out what is happening. 

•Regarding OCLC FirstSearch, why the search results vary when 2-byte space is included in my search query. When searching in Japanese language, adding multiple keywords cause inclusion of 2-byte spaces if I did not switch keyboard or input mode. Then sometimes it will return me nothing. If I return to the search screen and replace 2-byte space with 1-byte space, I do find some records for the same search query. 2-byte space doesn’t cause this problem all the time, but sometimes it does.

oPlease provide some specific examples so we can figure out what is happening. 

•Allowed action "save record to online file" and "save record to local file" from other IR records (currently only master is allowed), and then add our own IR to master. Quite often, IR record is better than master to use.

oThere is no plan to enhance IR functionality at this time. 

•Add font color for online save file/local save file for bibliography and authority.

oUnder consideration for the future.

•One master one manifestation. List different agency language records as IRs under one master.

oGLIMIR functionality, which is being rolled out slowly, will bring all the different language of cataloging records together.  In the future, OCLC expects to include cataloging functionality at the work level, which will also help to address this issue. 

•Adjustment to OCLC-supplied macro "GenerateAuthorityRecord": so that it will work with field 264 (in addition to field 260) appearing in each base bibliographic record, from which a NAR or SAR is to be generated

oThis macro is almost ready and is currently being tested by a few people.  It will be released very soon.  Meanwhile, a workaround with the current macro is temporarily edit the 264 to a 260 in the bib record before applying the macro. 

•Have the ability to input Hanja characters directly when Korean books come with the t.p. written in Hanja, not Hangul. Microsoft IME does not seem to have this ability

oUnder consideration for the future

•Make it possible to search records under the first assigned subject headings, that would be very helpful to find the classification #.

oThere are no current plans to address this.  Perhaps the Classify tool will fill this need.  In the Connexion Client, use a command Classify on the Edit menu to automatically supply a Dewey or Library of Congress classification number in a displayed record for a book, DVD, CD, or other material type in a field you specify. The command uses the prototype, FRBR-based Classify Web service http://classify.oclc.org/classify2/ to provide a classification number from a WorldCat record with a matching standard number in this order: OCLC number, ISBN, ISSN, UPC, LCCN.