Only with finally clicking on disk symbol
"Save" your settings will be passed on to the system configuration
etc/zgate.cfg;
after restarting the Alephino Z39.50 gateway the changes are effective.
Before performing a function within the Alephino Administration, please select a database from the menu, that should be valid for the following steps. The currently selected database is shown above the menu on the left hand side of the screen. Alephino Z39.50-gateway comes with a predefined symbolic database called "Z". This can be assigned to both record types MAB2 or MARC21. Depending on that record type from the sight of the Alephino client there are two symbolic libraries called "Z-MAB" and "Z-MRC".
The log contains a summary of all performed jobs within the administration. Always the last hundred jobs are listed. On calling up this function the newest entry - i.e. the last performed job - appears at the top of the list.
The list contains the following information:
For viewing a detailed protocol per job memorize the job number and follow the instructions for the function Show protocol.
For the newest 100 performed jobs within the administration one temporary
protocol file per job exists. On entering the job number and clicking
the button "Start" the contents of the protocol file are shown.
You can retrieve the job number via the function Show
log. The preset number always relates to the last performed job.
This function provides the current assignment of the license table on the Alephino Z39.50 gateway.
The list contains the following:
Via this function you can set up the date and time when the Alephino
Z39.50 gateway shall shut down. This setting - which is currently available
for UNIX/Linux platforms only - has just a temporary effect,
i.e. it is valid for the current process only.
For setting the parameters select a day and enter the time; then click
the "Start" button. In addition you can shut down the Alephino
Z39.50 gateway directly by clicking the button "Shutdown now".
Parameters
Weekday:
Select the day when the Alephino Z39.50 gateway shall shut down.
Time:
Enter the time (as "hour:minutes") when the Alephino Z39.50
gateway shall shut down on the previously selected day.
This function serves for exporting data in the batch mode.
Please note that batch export may allocate a great amount of volatile memory -
depending on the number of records requested.
Parameters
Target
Select an Z39.50 server as a data source.
(The targets you can find in the listbox below refer to symbolic files
defined in file
../etc/z39file.ext
Record format
Select the type that the records shall fit after the export.
This specification is important both to have information about the
formal structure of the records and about the character set.
Important note:
The declaration must agree to the "native" record format of the Z-source, that
is "MAB2 Iso-Format" for MAB-Sources (the german standard format),
otherwise "MARC21 Format".
Export file
Enter path and name of the export output file.
Selection criteria
Place the search query for the records to be exported. All search aspects
defined for the selected master file are valid; the syntax is identical with
the command language of the expert search (CCL).
Message per ... records
Specify after how many records each time a progress message is
entered in the protocol file. This specification is optional.
Abort after ... errors
Specify after how many occurred errors the export should be
aborted. This specification is optional.
Set the date and time when the Alephino Z39.50 gateway shall shut down. This setting is valid globally, not temporarily, for a particular process. If you e.g. choose Monday and 18:00 o'clock it means that the gateway shuts down every Monday at this time.
Set date and time for gateway shutdown
Select the weekday where the server shall shut down from the
drop-down menue and enter the time in the free input field (HH:MI).
Then click the "Set" button.
With "No shutdown" the shutdown adjustment will be removed.
Only with finally clicking on disk symbol
"Save" your settings will be passed on to the system configuration
etc/zgate.cfg;
after restarting the Alephino Z39.50 gateway the changes are effective.
Communication
Define the IP-address and port number for the Z39.50 gateway. It's just the specification needed by Alephinos Windows-applications and also Web-OPAC to communicate via the Z39.50 gateway.
Z39.50 Target
This parameter block contains certain properties of the Z39.50-server you want to address. The administration module gives the opportunity to arrange parameters only for predefined targets, to add targets and also to delete them.
Library
The original configuration file etc/zgate.cfg contains some predefined
Z-targets to be used as templates.
Choose a target from the listbox or create a new one using the input field.
Then click on button "Get current values" to retrieve the current definitions
of an existing target resp. a blank form for defining the new target.
Initially the targets "Z-MAB" and "Z-MRC" are the only active ones.
"Z-MAB" means, that the generated alephino record structure
is in accordance with the MAB2 standard description and also the Z-server must
deliver MAB2 formatted records as output.
Otherwise "Z-MRC" means, that the generated alephino record structure
is MARC21 compliant, the corresponding Z-server must deliver MARC21 formatted
records as output.
Both branches - the MAB2 and MARC21 compliant record description - are
supported by Alephino Z39.50 gateway simultaneously.
Have a look at etc/z39file.ext to understand the implementation.
Target
Enter the address of the Z39.50 target this way:
IP-address:port/database
User
Pass
If your Z39.50-target demanded an authentication, enter user and password here.
RecordSyntax
As illustrated before, the Z39.50 gateway supports targets which can
deliver MAB2 and MARC21 formatted bibliographic records.
In case of a MAB2-source enter MAB, otherwise MARC.
CCLRules
The Z39.50 protocol description is designed for a query syntax called RPN
(reverse polish notation), which is not even user friendly.
In addition to that abnormal notation manner the user has to know the so
called BIB1 attribute set, instead of "speaking" search aspects names you have
to use numeric codes.
Whereas Aleph(ino) uses the Common Command Language (CCL) - the most internet
users are familiar with - for database search requests.
The translation from CCL to RPN will be controlled by a table, which is covered
in the file you have to enter here.
For MAB2 and also MARC21 targets translation tables are provided:
etc/mablib.ccl respectively etc/marclib.ccl.
See also:
BIB1 Attributes
Common Command Language
TranslIn
For the translation of the specific character set of the Z-source into the
Alephino character set the following translation tables are provided:
mabtoiso = MAB2 character set marctoiso = MARC21 character set
Timeout
A major difference between the Z39.50 protocol and the Alephino protocol is,
that Z39.50 works "stateful".
To ensure that a Z39.50 session will be closed properly, the gateway closes the
Z-connection after a certain period of time while no access occured.
Enter the period (in seconds) while a Z-connection without actual traffic
should be hold open.
In case of an empty declaration a default value of 600 seconds will be
effective.
Scan
If your Z39.50 target supports scan-functionality (browse an alphabetical index)
- just tick this checkbox.
Navigate
This option is to build links in the full view of records for
the navigation to "related" records.
In difference to Alephino-databases there is no guaranty to find more than
the only record that's currently displayed.
(This function ist only available in combination with Scan.)
Define the parameters as desired and confirm the changes with "Set".
If you want to undo the modifications of the parameters click "Reset".
To remove the whole target - just click "Delete target".
Only with finally clicking on disk symbol
"Save" your settings will be passed on to the system configuration
etc/zgate.cfg;
after restarting the Alephino Z39.50 gateway the changes are effective.