Aleph v20 Upgrade – pt. 2 of 2

TO: SUNY Libraries with Aleph Regions housed on the SUNYConnect Shared Servers at ITEC

The v18-v20 upgrade calendar for the DEV and PROD regions of the campuses on the shared servers Delaware, Saranac and Seneca is available at the Aleph Support Portal at

The calendar starts with **MUST READ** notes. Please review these notes as they provide valuable information that campus staff must be aware of regarding the upgrade.

Contact me as soon as possible if there are any problems with the date of your campus PROD upgrade to v20. Given the number of campuses and the complexity of scheduling, the OLIS can consider re-scheduling a campus PROD upgrade only if there is a **SIGNIFICANT** campus activity going on at the same time that would prohibit library staff from checking their v20 PROD environment when it becomes available.

The differences between Aleph v18 and v20 will not require regional Aleph training. Refer to the TRAINING note on the attached calendar for additional information. A list of major highlights in Aleph v20, along with more information about Aleph updates, is available through the Aleph Support Portal at:

Because the OLIS and ITEC staff are heavily involved in preparing for the upgrade, some v18 support requests might not be addressed until after the v20 upgrade. Please be assured that the OLIS and ITEC will continue to support urgent issues related to server access and major PROD functionality problems. The types of requests that will be re-evaluated after the v20 upgrade relate to requests for new initiatives and changes in functionality that already work. Examples include support requests for help with:
• new indexes
• batch data loads EXCEPT for PLIFs
• table edits EXCEPT for tab16, 17 and 31 (Circ changes needed every semester)
• new functionality that the campus had not previously implemented
• optional global data changes (reclassifications, new collection codes, transfers, etc.)
• new printed products and changes to overdues

Also, there are types of requests that the OLIS and ITEC are not able to support. While this is not new, hopefully this review will be helpful. Examples include:
• requests not specifically related to Aleph (workflow questions, basics of cataloging, implementing external search forms)
• requests to disable or override features in Aleph that actually do serve a purpose (such as disabling document validation errors – bib record does not have a 245 [title] field)
• requests to support non-standard functionality (serials pattern data in the campus 50 library rather than in the 60 library)
• WebOPAC and GUI customizations beyond what is needed for functionality
• support for 3rd party applications/products outside of any required Aleph configuration (ILLiad, OCLC Connexion, printers, labeling software, Macros, LDAP)

We appreciate your understanding as we all work together to move from v18 to v20. Additional information regarding the upgrade will be provided to campuses when their v20 Aleph DEV regions become available.

Thank you

Comments are closed.