- Article Type: General
- Product: Aleph
- Product Version: 18.01
During the course of updating a single BIB (SYS01-005733692) and its associated HOL (SYS60-006714951) via manage-18, I accidentally ran manage-18 in SYS01 against the HOL record number (action performed on Feb. 28). After manage-18 ran, the last-doc-number for SYS01 was "reset" to the number of the HOL record number. The last BIB record before manage-18 was run was 005828940. I tried to "reset" the last-doc-number for SYS01 back to 005828940, but when I did, searching in ALEPH was returning unexpected results (action performed on March 6). So, I set the last-doc-number back to the 006000000 range.
I've been reading some of the KBs (8192-1880, 8192-666, 3961, 8192-667, 8192-668, etc.) about having BIB/ADM numbers unsynchronized and large gaps in the BIB record numbers (8192-667). Since there is now a large gap in the SYS01 record numbers (005828964 - 006714950 are empty, a range of 885,986), will the large gap affect how records are indexed for searching? Is there a way to remedy this and have the empty range be not so large?
885,986 is 15% of 5,828,964. This is not so much.
The caveat about "holes" in the bib numbers is in regard to larger-percentage holes.
Since making a change would involve deleting/re-entering all the records created since then, you should just leave it as is.
- Article last edited: 4/16/2014