Single station configuration

Operating system:

Windows^® Vista (Business or Ultimate) , Windows^® 7 (Professional, Enterprise, or Ultimate), Windows^® 8 (Pro or Enterprise), or Windows^® 10 (Pro or Enterprise).

CPU speed:

sufficient to operate Windows

RAM:

4GB

Hard drive capacity:
System minimum:

20GB
Add 60MB per 1,000 records in your Local Database (Active file)
If you now receive data on DVDs, add capacity as needed to support your subscriptions according to the chart on the FAQ page.

Screen resolution:

1024 X 768 pixels

Access to the Internet or a DVD-ROM drive to access copy cataloging data

Multi-user configuration

Client stations:

Operating system:

Windows^® Vista (Business or Ultimate) , Windows^® 7 (Professional, Enterprise, or Ultimate), Windows^® 8 (Pro or Enterprise), or Windows^® 10 (Pro or Enterprise).

CPU speed:

Sufficient to operate Windows

RAM:

4GB

Hard drive capacity:
System minimum:

60GB

Screen resolution:

1024 X 768 pixels

Access to the Internet or a network server to access copy cataloging data

Server:

Operating system:

Windows 2008 Server, or Windows 2012 Server

CPU speed:

sufficient to support operating system, 2+ GHz recommended for configurations exceeding five users

RAM:

12GB, 1+ GB recommended, especially for configurations exceeding five users

Hard drive capacity:

60GB + 60MB per 1,000 records in your Local Database (Active file)
If you now receive data on DVDs, add capacity as needed to support your subscriptions. See the chart. You will also need a DVD reader.

Screen resolution:

1024 X 768 pixels

Client station acting as server: Not recommended. TLC testing showed that as soon as the user on the dual-use station began routine Windows functions (e.g., using office suite software, chat, email, media players, etc.), the time it took to search and save a typical MARC record increased considerably for all catalogers. If this station is used exclusively for cataloging, 1+ GB of RAM and a 3+ GHz CPU is required.

Local Database size requirements vary considerably during use. A file that consumes 100 MB when the server is shut down may consume considerably more, up to an estimated 300MB, during active use. The file will shrink again to its normal size during the "vacuuming" process, which removes temporary data. This variance is built into the above specifications.