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.
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 serves for importing data in the batch mode.
Parameters
Master file:
Select the name of the master file, that you want to import the records
from.
Data format:
Enter the type of the records that will be imported.
This specification is important both to have information about the
formal structure of the records and about the character set.
For the Alephino- as well as Aleph data format the following additional specification can be made:
with identification number: check if identification numbers (field IDN)
should be ignored if present in the records to be imported.
Import file:
Enter path and name of the file that you want to import.
Mode:
Select the mode of the data import.
The mode Import includes all
check routines known from the cataloguing module, relating to the formal
structure of records, dependencies between fields, links between records etc.
The mode Load without checks abstains from those check routines
and creates linked records automatically, as long as the records to be imported
contain entries in the link fields and those records do not exist in the system.
Only for MAB version:
The mode Merge is for merging records that already exist in the databas
e
and records that are imported. When merging you have to define precisely which
fields of the record that already exists in the database shall be preserved
and which fields of the record to be imported shall not be taken over into the
old record. These specifications are listed in a merge table. The standard table
s
are located in the directory ../etc of your server installation and are called
tab_merge.XYZ, whereby XYZ stands for the record type (e.g. LOK for hol
ding records,
KOR for corporate body records). This import mode is important most notably for
members of SWB library consortium who import download files of the consortium in
to
Alephino. For merging see also the parameter "merge rules"
(s.u.).
Records from / to
Enter the number array of the records, that you want to import.
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 import should be
aborted. This specification is optional.
Response to doublets:
Select the way, that Alephino responds when finding duplicates. The
records can either be saved to a separate file for subsequent control;
or you may ignore the message and admit the record to the database in spite of
the duplicate. The records may also be merged (on this read also the description
of the parameter "Mode").
Response to errors:
Specify, if Alephino shall save imported records, that are realized as
defective, to an error file, or if they shall be imported anyhow.
Translate table input:
This specification is optional.
When importing characters are converted depending on the selected data format.
The rules for these conversions from one characterset into another are
defined in tables which are generaly called "translate tables". For the
characterset conversion there already are standard tables in Alephino
(all files with the ending *.trl in the directory ../etc of the server
installation, e.g. marc2utf.trl). Which are for the different data formats
is defined in the file alephino.cfg, directory ../etc of your server
installation, parameter "TranslIn".
Each translate table has a name that is used to address it when importing.
The names of the translate tables are listed in the file *transl.int in
the directory ../etc of your server installation. If you have defined a new
translate table, the name of the table has to be entered in this field if the
new table is supposed be used for the import.
Valid declarations for data import are:
DOSTOEXT - Import in character set PC850 (MS-DOS code page) ISOTOEXT - Import in Latin-1 character set (ISO 8859-1) MARCTOEXT - Import in MARC-8 character set
Translate table output:
This specification is optional. The principle is identical with the one
described under "Translate table input", only that in this case the
characterset conversion happens the other way round. When importing
records also an output may take place,e.g. if records where errors have been
detected are written into an error file, therefore "put out". This includes
a characterset conversion back into the initial character set (standard:
alephino.cfg, directory ../etc, parameter "TransOut").
Valid declarations for data export are:
EXTTODOS - Output in character set PC850 (MS-DOS code page) EXTTOISO - Output in Latin-1 character set (ISO 8859-1) EXTTOMARC - Output in MARC-8 character set
Conversion rules in:
Before records are imported they are converted into the Alephino data format.
This does not refer to the characterset (see above) but the formal structure
of the records, e.g. field categories, indicators etc. The rules for this
conversion are defined in certain files. The standard files are located in
the directory ../etc of your server installation. They have different names,
e.g. mab_alephino.TIT. This is the file for converting the records from MAB to A
lephino,
namely title records. Only if you have defined a new file you have to enter the
path
and the name of the file in this field, if the file is supposed to be used for t
he conversion.
Otherwise leave the field empty.
Merge rules in:
Enter here the path and the name of the file that contains the merge definitions
(about merging read also the description of the parameter "Mode").
An entry in this field is only required if you have created own files that contain
merge tables. The merge control tables are to be located in the directory ../etc of your
server installation and are called tab_merge.XYZ, whereby XYZ
stands for the record type (e.g. LOK for holding records, MEX for item records).
Preprocessing by XSLT:
On import of a XML-formatted file a XSL stylesheet can be applied which serves for
transformation respectively preprocessing into the Alephino MARC/XML format.
The stylesheet is to be located in sub-directory etc/xslt; its filename has
to be entered without leading path and without ending ".xsl".
This function serves for exporting data in the batch mode.
Parameters
Master file:
Select the name of the master file, of which records you want to export.
Data 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.
For the Alephino data format the following additional specifications can be made:
with identification number: check if the identification numbers (field IDN)
of the records should be included in the exported records.
$$ as subfield character: specify if the subfield character of the
records at hand should be "$$".
Export file:
Enter path and name of the export file. Select any device or file name
you want.
Selection (CCL):
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.
Records from ID / to ID:
Enter the number array of the records, that you want to export.
If you want to export all records leave the field empty.
To narrow down the amount of results fill in the parameter "Selection (CCL)" (se
e above).
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.
Translate table output:
This specification is optional.
When exporting, characters are converted depending on the selected data format.
The rules for these conversions from one characterset into another are
defined in tables which are generaly called "translate tables". For the
character set conversion there already are standard tables with Alephino
(all files with the ending *.trl in the directory ../etc of the server
installation, e.g. marc2utf.trl). Which are for the different data formats
is defined in the file alephino.cfg, directory ../etc of your server
installation, parameter "TranslIn".
Each translate table has a name that is used to address it when exporting.
The names of the translate tables are listed in the file *transl.int in
the directory ../etc of your server installation. If you have defined a new
translate table, the name of the table has to be entered in this field if the
new table is supposed be used for the export.
Valid declarations for data export are:
EXTTODOS - Output in character set PC850 (MS-DOS code page) EXTTOISO - Output in Latin-1 character set (ISO 8859-1) EXTTOMARC - Output in MARC-8 character set
Conversion rules in:
When exporting, a record conversion takes place depending on the selected export
format.
This does not refer to the characterset (see above) but the formal structure
of the records, e.g. field categories, indicators etc. The rules for this
conversion are defined in certain files. The standard files are located in
the directory ../etc of your server installation. They have different names,
e.g. mab_alephino.TIT. This is the file for converting the records from MAB to A
lephino,
namely title records. Only if you have defined a new file you have to enter the
path
and the name of the file in this field, if the file is supposed to be used for t
he conversion.
Otherwise leave the field empty.
This function is to export records from a specific master file incl. their linked records from other master files. That can be e.g. a bibliographic record with a linked authority record, or an item record with a linked loan records - which linked records should be exported together with the basic record, will be defined from the customer by creating a new file which contains the needed link definitions (please see below the explanation of the file format).
Parameters
Master file:
Select the type of the records that want to export.
Data 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.
For the Alephino data format the following additional specifications can be made
:
with identification number: specify if the idenitification numbers (field 001)
of the records should be taken over when importing the records.
$$ as subfield character: specify if the subfield character of the
records at hand is "$$".
For the export format MAB2 you can define in addition, if
a) starting from MAB2 main records (H-records) each time all subordinated
records (U-records) shall be exported as well or
b) starting from a subordinated record each time the linked main record shall
be exported.
Export file template:
Define path and name of the export files. Use the variable %s (percent s)
instead of the short name of the master file, e.g.
../data/%s.exp
Link configuration in:
Type in path and name of the file which contains your link definitions
for the export. This file must have the following format:
The file contains label in format
(ExpLinkfile)
Replace file with the short name of the master file, which records
should be the base for the export. If the records should be titles, the
label must be named
(ExpLinkTIT)
Define the link aspects for the import with the parameter LASP=. Should the linked records be authors, type
(ExpLinkTIT)
LASP=AUT
Further link aspects should follow in the format
(ExpLinkTIT)
LASP=AUT
LASP=SUB
Starting from the linked record it is possible to define again linked records by using the parameter LINK=. In our example the items records to the title should be exported, and together with the items the loan records:
(ExpLinkTIT)
LASP=AUT
LASP=SUB
LASP=MEX,LINK=VBU
Filter by:
Enter the number of the field which should serve as a filter
option and type in the filter text. Use only the fields that are
related to your selected type of records.
Records from ID / to ID:
Enter the number array of the records, that you want to export.
If you want to export all records leave the field empty.
To narrow down the amount of results fill in the parameter "Filter by"
(see above).
Translate table output:
This specification is optional.
When exporting, characters are converted depending on the selected data format.
The rules for these conversions from one characterset into another are
defined in tables which are generaly called "translate tables". For the
characterset conversion there already are standard tables in Alephino
(all files with the ending *.trl in the directory ../etc of the server
installation, e.g. marc2utf.trl). Which are for the different data formats
is defined in the file alephino.cfg, directory ../etc of your server
installation, parameter "TranslIn".
Each translate table has a name that is used to address it when exporting.
The names of the translate tables are listed in the file *transl.int in
the directory ../etc of your server installation. If you have defined a new
translate table, the name of the table has to be entered in this field if the
new table is supposed be used for the export.
Valid declarations for data export are:
EXTTOMAB - Output in MAB2 character set EXTTODOS - Output in character set PC850 (MS-DOS code page) EXTTOISO - Output in Latin-1 character set (ISO 8859-1) EXTTOMARC - Output in MARC-8 character set
Conversion rules in:
When exporting, a record conversion takes place depending on the selected export
format.
This does not refer to the characterset (see above) but the formal structure
of the records, e.g. field categories, indicators etc. The rules for this
conversion are defined in certain files. The standard files are located in
the directory ../etc of your server installation. They have different names,
e.g. mab_alephino.TIT. This is the file for converting the records from MAB to A
lephino,
namely title records. Only if you have defined a new file you have to enter the
path
and the name of the file in this field, if the file is supposed to be used for t
he conversion.
Otherwise leave the field empty.
This function serves for the balance of local stored bibliographic records with the central database of a consortium. The proceeding:
This function serves for signaling changes in local item and holding records to the central server of a consortium. The proceeding:
Parameters
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 processing should be
aborted. This specification is optional.
Once the connection to the consortium server failed, the processing will stop
immediately.
This function unloads your patron data using the PLIF format.
Parameters
PLIF action indikator:
Choose the action indicator to be used for the unloaded patron data
records.
Data format:
Select either "classical" sequential text - or the new
XML-format for output.
Export file:
Enter path and name of the export file. Select any device or file name
you want.
Selection (CCL):
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.
Records from ID / to ID:
Enter the number array of the records, that you want to export.
If you want to export all records leave the field empty.
To narrow down the amount of results fill in the parameter "Selection (CCL)" (se
e above).
This function loads patron data coming in the PLIF format.
Parameters
Input file:
Enter path and name of the file that you want to load.
Data format:
Select either "classical" sequential text - or the new
XML-format for input.
Ignore indicator:
Because of the fixed length structure of PLIF records all fields have to be
completely filled. Therefore it may be necessary to specify a special
indicator, called the ignore indicator, to prevent certain fields in the
record from being loaded.
Specify the character that serves as the ignore indicator in the PLIF
load file. The specification of the ignore indicator is optional; if no
one is specified, all fields of a PLIF record will be loaded.
Preserve permissions:
If set to "yes" the actual values of the patron's permissions will be
protected against changes. Otherwise they will be reset to the defaults
given by the patron's status and sublibrary.
Search for doublets:
With "Yes" selected the check for doublets will be applied as defined for record
type "Users" in the Alephino control tables. If a record has been identified a doublet,
it will be discarded.
Preprocessing by XSLT:
On import of a XML-formatted file a XSL stylesheet can be applied which serves for
transformation respectively preprocessing into the Alephino PLIF/XML format.
The stylesheet is to be located in sub-directory etc/xslt; its filename has
to be entered without leading path and without ending ".xsl".
This serves for unloading bibliographic records to supply a Primo pipe. Data will be written to output OAI formatted.
Parameters
output file:
Enter path and name of the file you want for output.
To fill in this field is mandatory.
selection (CCL query):
Enter either a search query for title records (Alephino CCL syntax) or
alternatively the keyword NEXT.
(Can be pre-filled by use of the button next to that input field.)
With NEXT all title records will be included in the output record set that have been modified, inserted or deleted since the publishing was performed for the last time.
records from ID / to ID
Enter here a range of ID numbers for records to be included in the output
record set.
If you want to have all records written to output, simple leave these and also
input field "selection" empty.