Full Load 2 “Known Issues” that affect all P1LS databases (12/01/03):

 

The following Subset 4 Known Issues were resolved with Full Load 2:

 

  1. 505 $t not indexed in TTL and URI indexes:  only 505 tags with no indicators are presently being indexed in the TTL and URI indexes.  This is a syntax error in the indexing table (tab11_acc) and requires reindexing in order to effect a change. (Ticket #218)  RESOLVED.
  2. Missing 4xx, 6xx, 7xx, and 8xx entries in NWT index:  a possible programming change between Rls. 15.2 and 15.5 appears to require different syntax for indexing indexing only those fields that contain $t (tab11_acc).  This requires reindexing in order to effect a change.  (Ticket #222) RESOLVED.
  3. Cross-references not being created from headings with $wnnne: tab20, the table that determines cross-reference creation, appears to create cross-references from $wxxxn (x = any character) and $wxxx[space].  Further discussion and consensus on this question may be required. (Ticket #223) RESOLVED.
  4. ALEPH Loans may not match NOTIS loan count:  The loans on the ALEPH Loans list should match NERCDEV1 “has” list.  The loan count on the NOTIS patron record may not match because patrons were extracted on a different date than loan links were created. (There is no ‘resolution’ to this issue:  please be aware that this will always be the case with migrated Circ transactions.)
  5. Patron List sort by Barcode only retrieves a few records: The Patron List only retrieves a few records when sorted by Patron Barcode.  This problem has been reported to ExLibris.  Sorts by Name and Patron ID seem to be working correctly. RESOLVED.
  6. Ampersand handled as “and” in browse searches:  In NOTIS an ampersand is translated to a space in MHI (headings) searches.  In Aleph an ampersand is retained in indexing in conformance with NACO normalization rules and translates to “and” for browse searches.  The issues are whether handling ampersand as “and” can be changed or should be changed. (Ticket #231)
  7. LCCN indexing:  leading spaces in the LCCN make LCN indexing and retrieval difficult.  Because the LCCN is used in bib matching and merging, and the LCCN is in effect a fixed-length field the solution to this problem may not be simple and must be tested with Aleph’s bib loaders. (Ticket #266)
  8. 866 Summary Holdings don’t display in WebOPAC: For some reason the MARC 866 fields were output with an extra initial, empty $a.  This causes the 866/Summary Holdings field to not display in WebOPAC.  Re-extracting and reloading the Holdings records without this extra empty $a solves the problem, but another WebOPAC problem exists that causes the 866 contents to display twice.(Ticket #174). RESOLVED.
  9. Problems with links to local authority files: For UF and UNF, who have selected authority architecture option #1 (link to both local and resource authority files), the program that “dumps” all local authority headings into the bib browse indexes (p_manage_102) is not terribly refined or subject to detailed specs.  In other words, much of its behavior is hard-coded and can’t be changed.  This results in an inability to correctly load Author/Title authority headings from the local authority file into the NWT index, and inappropriate loading of 130 series headings into the SUB index.  The week of Sept. 20, the ue_08 process will be run against both the local and resource Auth. Files for UF and UNF, to test this different method of linking prior to Full Load #2. UFTEST and NFTEST have been re-indexed and re-linked on 9/24/03.(Ticket #242)
  10.  Formatting of “Brief List” records:  in many places in GUI and WebOPAC, an intermediate “Brief list” of bib records is provided (NOTE:  this has nothing to do with the WebOPAC “Brief Recs” listing.  This brief view of bib records actually consists of a separate Oracle table, Z13, and is defined by aleph table tab22.  There will need to be consensus decisions on how these brief records should be structured.  FCLA is looking into the issue and will make recommendations. (Ticket #245)  There also appear to be some inconsistencies in how the “Brief List” appears in various modules, and FCLA is checking into this with Ex Libris (Ticket #249).
  11. Inappropriate linking to LC authority records in SUM (Subjects, MeSH) index:  links are being found to LC authority records in the SUM index, for no apparent reason.  This appears to be a new problem since the installation of Rls. 15.5.1.  RESOLVED: see UNF’s TEST database for proof of resolution (http://alephtest.fcla.edu:4555/F). (Ticket #268).
  12. Possible empty subfield a in NOTIS data:  Searching “1” or “?” to get to the beginning of a browse index in Aleph may retrieve records with indexed fields that contain an empty subfied “a”.  NOTIS batch cleanup may be possible:  contact Mary Ann O’Daniel with NOTIS cleanup requests. (Ticket #304)
  13. PROGRAMMING REQUEST:  Adding 852 $z for NOTIS copy statements with a STATUS field = d?  UF has requested that FCLA include a new $z (public note) in 852 fields during output of NOTIS copy statements to Aleph HOL records.  The contents of the subfield would be: "Search under individual Author/Title for items in this series."  A test of this public note can be found in the Holdings screen of record #AMM1556 in UF’s Subset 4 database (http://alephtest.fcla.edu:4545/F). (Ticket #274).  UNF and UWF should contact FCLA to request this programming change in their data conversion. RESOLVED.
  14. Diacriticals problems:  Ex Libris’s data conversion and load programs output error messages on a variety of diacriticals.  After the Subset 4 load Ex Libris provided FCLA with a new program that reports the Aleph record number and field where problem diacritics appear, and FCLA is working on additional programs to report these problem diacriticals.  Some of these are random errors in NOTIS, and others may be correctable via batch NOTIS cleanup.  Contact Lydia Motyka (lydiam@nersp.nerdc.ufl.edu) if your institution would like files of these error messages for your institution.  For questions of batch NOTIS cleanup contact Mary Ann O’Daniel (fclmod@nersp.nerdc.ufl.edu). Diacritics conversion errors for Full Load #2 are being submitted to P1LS.  Cleanup on NOTIS is ongoing.
  15.  TKR index and “cut prefix”:  in Subset 4 TKR fields (NOTIS Tickler) are indexed with the pre-fix/parenthetical data.  Aleph has a new indexing feature, “cut prefix”, that skips data within parentheses during indexing.  This feature will be implemented in Full Load #2 on the TKR index.  In Subset 4 it was implemented in the OCL index. (Ticket #281).  Implemented in TKR index in Full Load #2.
  16. Aleph HOL 008 and LDR conversion:  we’ve discovered some possible inconsistencies in the conversion of NOTIS copy statements and MHLD data into Aleph HOL 008 and LDR fields and will be reviewing this prior to Full Load #2.  Additional review of HOL 008 and LDR data would be welcomed, along with additional Problem Reports.  Conversion specs for HOL 008 and LDR fields are attached.  See Issue #27 below.
  17. 650x2 bib headings loaded with $2MeSH:  the Subset 4 bib load neglected to delete the conversion routine that adds the $2MeSH to bib 650x2 headings.  This will be fixed in Full Load #2. RESOLVED.

 

New issues added for Full Load #2:

18.  Keyword WSG index missing 651:  A typo in the keywording table has resulted in the 651 tag being omitted from the WSG index, and instead the 650 is being indexed.  This reinforces the need for all P1LS to carefully check over the indexing tables and report any problems and omissions.  The indexing tables have gone through a large number of changes over time, and although FCLA have proofread the tables several times, it’s still possible that typographical errors exist.

  1. 610 $t missing from Subject browse indexes: Another instance of an indexing table typo.
  2. 8XX NOTIS subfield “6” not converting to subfield “8” in HOL records: The NOTIS to Aleph conversion specs requested this change in subfielding, but it was discovered after Full Load #2 was begun that this conversion was not happening.  The problem has been corrected for UWF in Full Load #2, but HOL re-extraction and reload will be required for UF and UNF to see this change [Subset 5].
  3. Only first 505 $t is indexed in the TTL index.  This issue has been referred to Ex Libris for comment. (Ticket #397, and others).
  4. LCA10:  550 tags display at the bottom of the record in GUIOPAC and WebOPAC. This is not a problem in the local authority files, and duplicating these files in LCA10 doesn’t solve the problem.  The problem has been referred to Ex Libris. (Ticket #403).
  5. 866 displays twice in WebOPAC.  See issue #8 above.  The WebOPAC team is looking into this problem. (Ticket #398).
  6. MARC tags loaded at the bottom of the bib record:  This is caused by tags being excluded from the tab01.eng table of the bib library.  Ex Libris has advised FCLA to include all tags that appear in bib records.  Please submit problem reports of any MARC tags that appear at the bottom of your bib records. [Subset 5]
  7. HOL records with STA = SUPPRESSED display in WebOPAC.  This issue has been referred to Ex Libris with a request for high priority treatment. (Ticket #399)
  8. Migration of Z’d copies into Aleph.  UNF has elected not to migrate any Z’d copies or attached items from NOTIS.  UF and UWF are revisiting the question of whether or not Z’d copies should migrate.  Programming is in place to omit all Z’d copies from the migration, with the exception of specified locations.  UWF’s Full Load #2 will not include Z’d copies, pending resolution of this question.  UF’s Full Load #2 presently includes Z’d copies.
  9. Changes to HOL LDR mapping.   LDR byte 6 conversion has been revised.  See the attached HOLLDRcreation_revised document. [Subset 5]