= Modify profile
and
= Delete profile
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.
Alephino profile service provides to you - and via Web-OPAC also to the user -
the opportunity to automatise specific retrieval requests.
For this the alephino database may contain so called profile records, which
are linked to the user.
A profile record consists of the following categories:
The proceeding:
The user - or substitutionally the system administrator - creates profile records for every search request that should be executed repeatedly. The execution of all profiles should be initiated dayly using Execute all profiles Finally the result lists will be sent to the users via E-mail. For the automatisation of that procedure the Alephino print deamon may be used.
After pressing you'll get a short list of all profile records. If you've entered a valid user barcode in field Barcode, the list contains only profiles of the specific user. The list is sorted descending by creation date , that means the newest profile record is at the top.
At the beginning of each line in the list you will find the following links:
and
After saving a profile, the profile list of the user will be refreshed; after deleting a profile a refreshed list of all profiles will be displayed.
Parameters:
Search query
Enter here the search query in the Alephino command language.
(=Expert mode in OPAC)
Example: tit=history*
Filter
Optional.
Enter here the category number of a field, which shall serve as filter
criterion and also the filter text.
Only "native" fields from bibliographic records are effective for filter
purposes.
Syntax: category number=filter text
Example: 425 = 2002 (means: only titles with issue date in 2002)
Interval
Enter here time interval for executing the search profile.
If you choose "On demand" the actual profile must be started by the user
explicitely from Web-OPAC - it will not be included when running
"Execute all profiles".
Hit mode
Determine here which hits should be included in the result list:
Checkbox Active
Remove the check mark if you want to temporarily suspend the actual
profile from execution.
Further parameters see above.
Mandatory fields:
Barcode, Name (of the Profile) and also the search query are necessary, otherwise saving the profile record will be denied with an error message "Mandatory field missed".
Test a profile:
From within the screen for processing a profile record you also can check whether your profile is correct - and executable - or not. To do so, press . In contrast to the regular execution of the profile the result list will not be sent to the user automatically - and normally discarded.
Start the execution of all profiles from this screen. You have the opportunity - e.g. for test purposes - to enter a deviating execution date and also a specific output file. Please note that the result list are only automatically sent to the users via the print daemon if the agreed path name for the output file ../print/sdiresult.nnnn (nnnn = Job-number) is kept. This is ensured by simply letting Output file empty. Otherwise you have to send the result lists manually from the Alephino Job-Manager.