Systems Librarian Training

Library Client Configuration

South Dakota Library Network1200 University, Unit 9672Spearfish, SD 57799www.sdln.net

© South Dakota Library Network, 2008©Ex Libris (USA), 2004Modified for SDLNVersion 16Last Update: March 2008

2

Application ConfigurationThe Application Configuration window shows the standardvalues and the actual setup of INI files for each module. Toaccess this window, on the menu bar select: Configuration | Application Configuration:

3

Application ConfigurationThe Application Configuration window displays:

4

Application Configuration

The following INI files are viewed and edited in the Application Configuration window:

• Alephcom.ini (Common headings) • Alephadm.ini (ALEPHADM) • Acq.ini (Acquisitions/Serials) • Catalog.ini (Cataloging) • Circ.ini (Circulation) • Ill.ini (Interlibrary Loan)

5

Application Configuration

The client’s current text appears in the left column, and the Aleph default appears in the right column of the table. Lines with a field whose value was changed are highlighted in gray. Clicking on restores the original value of the high- lighted item.

6

Application Configuration

To edit a field, place the cursor on it and double-click. After you’ve finished editing the table, be certain to click

to save the changes you made to the files.

7

Print Configuration

8

Print Configuration

The Print Configuration window shows the standard values and the unique print settings for each module. To access this window, on the menu bar select Configuration|Print Configuration:

9

Print ConfigurationThe Print Configuration window displays:

10

Print Configuration

The following print files are viewed and edited in the Print Configuration window: • Alephcom print.ini (Common Headings) • AlephADM print.ini (ALEPHADM) • Acquisitions print.ini (Acquisitions/Serials) • Cataloging print.ini (Cataloging) • Circulation print.ini (Circulation) • Interlibrary Loan print.ini (Interlibrary Loan)

11

Print ConfigurationThe table/editing portion is divided into 15 columns.

12

Print ConfigurationTable columns include:

• Function Name: This is the name that has been assigned by the programmer for internal use. Do not change this name. Each function produces one or more printouts based on the templates.

• ID: This is the version number of the template. Do not change this number.

• Setup (Y/N): This allows you to display the print dialogue box when you print.

• Mail (P/M/B): This defines if the file will be printed (P), e-mailed (M), or both (B).

• Local File Name: The name of the file as it is saved on the client’s local

drive. • Target 1-10: These are option fields used for print IDs for offline printing or

device IDs for online printing.

13

Print Configuration

Functionality and editing works the same in the Print Configuration files as in the Application Configuration files. To edit a field, place the cursor on it and double-click. Any lines that have been changed are highlighted in gray. Be certain to click to save changes when you are finished.

14

Services

15

Services

Services are processes generated in ALEPH that may: • Manipulate the database in a certain way (e.g. build indexes)• Produce reports of data (e.g. circulation statistics or budget reports)• Produce correspondence (e.g. order lists or overdue notices)

16

ServicesTo access services, go to the Services option on the menu bar in the Circulation, Cataloging or Acquisitions client.

17

Services

Once you’ve selected a service, a window will be displayed prompting you for variables that will impact the report. For example, this is the Missing Items Report window: (ret-item-02)

18

Task Manager

19

Task ManagerThe Task Manager function is present in each of the ALEPH Modules. It enables you to work with print files that have been produced by various functions, view the batch queue and batch logs, and set up and activate printers. To activate the Task Manager, go to the menu bar and select Aleph | Task Manager:

20

Task Manager

The Task Manager window displays:

21

Task Manager

The Task Manager window is divided into four tabs: • Print Daemon• Batch Queue • Batch Log • File List

22

Task Manager

The Print Daemon is used to transfer print files from the server to the workstation according

to the print ID.

23

Task ManagerThe Batch Queue lists the jobs that are waiting to be run. In order for the jobs to be processed, the “status” must be running.

24

Task ManagerThe Batch Log displays the jobs that have run or are running, along with the description of the parameters passed.

25

Task Manager

The File List displays the finished jobs that have printable results. This window allows you to move the results to your local drive where you can print or send them via e-mail depending on your print.ini setup.

26

TAB 100

27

TAB 100

Tab100 defines switch settings for different aspects of the system. Tab100 is unique in two significant ways:

•The table is built in a textual manner as opposed to the column breakdowns used in other tables.

•The table hierarchy is different: the client first reads the system tab100, then the ADM tab100, looking for lines that vary from the system table. This allows libraries to enter values in their table for functionality that is different than the system table.