In addition to timestamp, master file and action the data of each record will be written to the output. Pls. select
for that kind of comprehensive recording.
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 just click on the job number that will take you to 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 server.
The list contains the following:
type (GUI, WWW, Z39.50)
license/total number
key (IP address)
time of the last access
Via this function you can set up the date and time when the Alephino
server shall shut down. This setting has just a temporary effect,
i.e. it is valid for the current server 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
server directly by clicking the button "Immediate shutdown".
Parameters
Day:
Select the day when the Alephino server shall shut down.
Time:
Enter the time (as "hour:minutes") when the Alephino server
shall shut down on the previously selected day.
The fundamental idea of the Alephino saving process is data redundancy.
That means the carrying of all database updates (creating, modifying and deleting data) in a log
file
../pools/<pool designation>.log assigned to the respective database -
also called "data pool". This file consequently always contains the difference between the
current database and the last saved database.
Provided that the database and the log file don't become damaged simultaneously
(what is quite unlikely), the saving process ensures the
complete restoration of the data, if they are damaged physically
or logically, e.g. by abnormal system ends.
In order to be able to use the data restoration for all defined database in case of need, you need to make an "initial copy" for every new database with the Alephino saving process.
Subsequent to saving you need to perform the release of the backup.
The interval of repeating the saving is negligible. This depends mainly on the quantity of updates in the database, that accumulate in the log file as explained above.
After modifying the data structure definitions you always need to create a new backup of the related database.
Parameters
Release backup y/n:
The release of the backup effects the removing of all log entries relating
to the previously saved database; the log entries are not required anymore
because the database was successfully saved and is undamaged. Hereby the
log file is usually minimized.
After saving and releasing all databases administrated by the system all log
files should have the size ZERO.
Target directory:
Enter the path in that the data should be stored. If you enter nothing,
the default directory ../backup is used.
You need to load the backup of your database, when a database is obviously damaged, i.e. you get error messages like: "Database damaged", "Database locked" or "Access error".
On using the function "Load pool" the backup is searched on
your hard disk depending on the parameterization.
In the case of success the following message appears: "Backup from
MM/DD/YY HH:MM:SS". Then start the loading of the backup by
clicking "Start".
Parameters
Reconstruction y/n:
By fusing the backup and the updates saved in the log file a consistent and
complete database is created.
The error message "Database is not an original backup" means, that the database used for the reconstruction was not created by means of loading a valid backup. The reconstruction routine refuses a backup created with tools that are not implemented in ALEPHINO.
However, there is no safeguard against using an old backup. In this case you lack the data that were added or modified in the period between the used backup and the valid (last) backup.
The message "Error on writing database" means, that an assignment and the reconstruction of the database is impossible because of too many differences between the backup and the current log file.
Source directory:
Enter the directory that contains the backup files. If you enter nothing,
the default directory ../backup is used.
Delete backup files after success:
Specify, if you want the backup files to be deleted after loading the
database.
This function enables the recording of backups, i.e. the contents of the backup file are converted to uncoded text.
Parameters
Date from:
Enter the date (as YYYYMMDD) from that on the backup shall be recorded.
Date to:
Enter the date (as YYYYMMDD) until that the backup shall be recorded.
(Checkbox) Report including data:
In addition to timestamp, master file and action the data of each record
will be written to the output.
Pls. select for that kind of comprehensive recording.
The default date in both cases is the current date. If you want to have the whole content of the current backup recorded pls. enter "00000000" for both dates.
This function effects a checking of all files - e.g. master files, link lists and indexes - for defective records. For this purpose all related records in the database are read; defective records are output with the corresponding ID numbers and the failure cause.
The routine for initializing a database is normally used, if the empty db cannot be used in its default form, or if a separate data stock shall be administrated in a new database.
! Previously you need to select the db, that you want to create, in the Alephino Administration via the menu "Administration / Select database" !
In Alephino there is a file containing lists if stop words:
file stopl.kat, directory../data
The default list of stop words is available for the searchable fields "title /keyword", "subject" and "corporate body". You can expand or minimize the list or define further searchable fields.
When you modify the stop word list - preferably before starting to enter records to the database - you should initialize a new db and load the stop word list.
If you modify a list of stop words after working with an existing database, you might need to delete the old file in the database before loading the new list and to rebuild the indexes of the related search terms.
Parameters
File number:
Enter the file number (found in the file xyzdata.int).
File to load:
Enter the path and the name of the stop word list.
Unload binarily
This function enables the export of a database, including its records and the
list of stop words. The records are exported binarily.
You could want to select this function to rebuild a database.
Parameters
File list:
Enter a list of logical file numbers (according to xyzdata.int,
directory ../etc), separated by commas. If you want to unload
all files you can use the default value "ALL".
File to load (optional):
Enter path and name of the export file, if you don't want to use the default
path.
Load binarily
This function enables the import of a database, that was previously exported via "Unload binarily", including its records and the list of stop words.
When loading the exported records, an empty database resp. the non-existence of the related file is assumed.
Parameters
File list:
Enter a list of logical file numbers (according to xyzdata.int,
directory ../etc), separated by commas. If you want to load
all files you can use the default value "ALL".
File to load (optional):
Enter path and name of the export file, if the default path was not used
for the binary unloading.
The deletion of files, particularly search term files, may become necessary in the case of errors, modifications or additions.
When an index is deleted, you need to rebuild it afterwards (s.a. Build index).
Parameters
File number(s):
Enter the number of the file to be deleted (as defined in the file
xyzdata.int, directory ../etc). If you want
to delete more than one file in one step, enter them separated by commas.
This function removes a complete master file
- with all associated index-files and link-files that may be -
from current database.
This is usefull especially if you want to load data from foreign sources
repeatedly.
Parameters
Master file:
Select the name of the master file to be deleted.
Searching the Alephino database always requires the existence of an index filled from data fields to be searched. This function serves for creation of indexes in the database. It has to be applied on:
Caution:
If an existing index needs to be modified or corrected the respective index file
has to be deleted before. Otherwise, as a result of indexing, multiple references
to the same records may have been created.
For this use Delete file).
The buildup of an index is controlled by the following Parameters:
Master file:
Select the name of the master file, that the search term is assigned to.
Index number(s):
Enter the numbers of the searchable fields (as defined in the file
xyzindex.int, directory ../etc) to be created
(INDEX=).
This function effects the building of a previously deleted link list (see
Delete files).
You should not work with the database until this function is performed. The
buildup of a link list is managed via parameters.
Parameters
Master file:
Select the name of the master file, that the link is assigned to.
Link number(s):
Enter the numbers of the links (as defined in the file xyzlink.int
, directory ../etc) to be created (LINK=).
Rebuild sequence numbers:
Aleph(ino) GUI-applications must always have a so called sequence number
to address records linked to bibliographic records.
I.e. items linked to a specific title have consecutive numbers -
beginning with "1". As a result of errors while loading foreign data or
whatever this numbering may be corrupt.
If you check the box, the numbering will be renewed while linking automatically.
This function records the control blocks of an existing database. You should make a database protocol when you are uncertain about the data structure of a database and want to compare it with an exsting database definition file.
The protocol contains informations on date and time of the last database backup, index lengths and record lengths.
Parameters
Files to record: Enter the number of the file to be recorded (as defined in the file xyzdata.int, directory ../etc). The default parameter is "ALL", i.e. all master files, link lists and indexes are recorded.
The tool enables the modification of a particular field in the various records of a master file. You specify the modifications to be done and the fields to be modified in a script. Examples of such script files you find in the file ../etc, e.g. *script.txt.
Create one script per every purpose. The scripts are identified via their designations and may be situated in the same file.
Parameters
Master file:
Enter the name of the master file, that the records shall be valid for.
Script file:
Enter path and name of the file, that contains the script to call up.
Script:
Enter the name of the script.
Records from ID: / to ID:
If only a portion of records shall be processed enter a range of ID numbers.
(Checkbox) Mode:
By default only those records that have been modified according to the
script rules will be re-written to the database.
Tick this checkbox to force update of all records.
This function is for deleting authority records that are not linked to any title records. The authority records are authors records, subject headings or classifications. Select the authority file that you want to edit beforehand via the drop-down menu that opens when clicking on the arrow of the field "records to be deleted".
Before you start the deletion batch, you should by all means backup your data stack via the menue point "Saving/Save database" and afterwards "Release backup". Read also the Online help to save database.
Parameters
Records to be deleted:
Choose here the records which should be deleted: Authors without titles, Corporate bodies without title, Subject headings without title or Notations without title.
Mode of operation:
Choose here the type of batch deletion that you want to run:
List file:
Specify here the path and name of the file that contains the list with the identification numbers of the records which should be deleted. If you leave the field empty, the path ../data/purgelist is used as default.
Detailed messages:
Activate this checkbox if you want a verbose protocol of the batch deletion.
This function will delete all bibliographic records which don't have any linked items.
Before you start the deletion batch, you should by all means backup your data stack via the menue point "Saving/Save database" and afterwards "Release backup" (see also Online help to save database)!
Parameters
Entry date before:
Here, you may specify that only records which were created before a certain date should be deleted. If you don't want to filter by creation date, simply leave the field empty.
Mode of operation:
Choose here the type of batch deletion that you want to run:
List file:
Specify here the path and name of the file that contains the list with the identification numbers of the records which should be deleted. If you leave the field empty, the path ../data/purgelist is used as default.
Detailed messages:
Activate this checkbox if you want a verbose protocol of the batch deletion.