Frequently Asked Questions
FCLA Homepage
**Site Under Construction**
 
   When will our library migrate to ALEPH?
   How do we catalog while our data is being migrated?
   Will all library functions be migrated at the same time?
   How much staff time will be required for the migration?
   What is the general migration process?

 

When will our library migrate to ALEPH?

The order will be determined by the library directors. The first four libraries to migrate (the Phase 1 Libraries) have been identified as UNF, UF, UWF, and FGCU.

How do we catalog while our data is being migrated?

Most libraries will probably institute a cataloging moratorium while their final database extraction and load is being done. Depending on how long it will take to load and index your data prior to "switching to production" (STP, in "ALEPH-speak") you may institute a "gap" procedure, whereby a "cutoff date" for extracting the data is set, your full database is extraction and load begins, and any new cataloging added after the "cutoff date" will undergo a second extraction and load. The timing for the gap extraction and load varies, but it often happens at around the time when staff begin cataloging on the new system. The most important concern is to make sure that no records, particularly new cataloging, fall through the cracks and are not loaded into the new database. FCLA expects that only the largest databases may need a "gap" load, and that most libraries' databases can be loaded in approximately a week or so. Will all functions be migrated at the same time? Yes: we expect that all library data and functions will migrate to ALEPH during the "Switch to Production" phase of the implementation. (An Overview of the Switch to Production Process.) However, you will still be able to search and view, but not modify or add to, your NOTIS data for some time after Switch to Production. After the last library has migrated to ALEPH plans will be made for shutting down the NOTIS system. How much staff time will be required for the migration? At a minimum, learning a new system will involve time and practice for functional training. Beyond actual training, staff actively involved in implementing the new system should expect to devote a substantial amount of time to the implementation and may need to be released from some of their usual responsibilities. Certain stages of the implementation, such as evaluating a test load, may involve a large number of staff over a brief period. What is the general LMS migration process? An Overview of Each Library's Tasks in the Implementation Process

 
Navigation Bar