Aleph 20 Syslib Guide - ADAM
Aleph 20 Syslib Guide - ADAM
- ADAM
Version 20
CONFIDENTIAL INFORMATION
The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will result in
economic loss. DO NOT COPY UNLESS YOU HAVE BEEN GIVEN SPECIFIC WRITTEN AUTHORIZATION
FROM EX LIBRIS LTD.
This document is provided for limited and restricted purposes in accordance with a binding contract with Ex
Libris Ltd. or an affiliate. The information herein includes trade secrets and is confidential.
DISCLAIMER
The information in this document will be subject to periodic change and updating. Please confirm that you have
the most current documentation. There are no warranties of any kind, express or implied, provided in this
documentation, other than those expressly agreed upon in the applicable Ex Libris contract. This information is
provided AS IS. Unless otherwise agreed, Ex Libris shall not be liable for any damages for use of this document,
including, without limitation, consequential, punitive, indirect or direct damages.
Any references in this document to third‐party material (including third‐party Web sites) are provided for
convenience only and do not in any manner serve as an endorsement of that third‐party material or those Web
sites. The third‐party materials are not part of the materials for this Ex Libris product and Ex Libris has no
liability for such materials.
TRADEMARKS
ʺEx Libris,ʺ the Ex Libris bridge , Primo, Aleph, Alephino, Voyager, SFX, MetaLib, Verde, DigiTool, Preservation,
URM, Voyager, ENCompass, Endeavor eZConnect, WebVoyage, Citation Server, LinkFinder and LinkFinder
Plus, and other marks are trademarks or registered trademarks of Ex Libris Ltd. or its affiliates.
The absence of a name or logo in this list does not constitute a waiver of any and all intellectual property rights
that Ex Libris Ltd. or its affiliates have established in any of its products, features, or service names or logos.
Trademarks of various third‐party products, which may include the following, are referenced in this
documentation. Ex Libris does not claim any rights in these trademarks. Use of these marks does not imply
endorsement by Ex Libris of these third‐party products, or endorsement by these third parties of Ex Libris
products.
Oracle is a registered trademark of Oracle Corporation.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open
Company Ltd.
Microsoft, the Microsoft logo, MS, MS‐DOS, Microsoft PowerPoint, Visual Basic, Visual C++, Win32,
Microsoft Windows, the Windows logo, Microsoft Notepad, Microsoft Windows Explorer, Microsoft Internet
Explorer, and Windows NT are registered trademarks and ActiveX is a trademark of the Microsoft Corporation in
the United States and/or other countries.
Unicode and the Unicode logo are registered trademarks of Unicode, Inc.
Google is a registered trademark of Google, Inc.
Copyright Ex Libris Limited, 2010. All rights reserved.
Document released: October 5, 2010
Web address: http://www.exlibrisgroup.com
5.2 Integrate the Fulltext Index for Web and OPAC Searching................................. 18
5.2.1 Fulltext Search in the GUI (pc_tab_sear.<lng>).................................................................. 18
5.2.2 Search in the OPAC (find-code-include et al.) .................................................................... 18
6 SERVICES....................................................................................................................... 19
9 CREATE THUMBNAILS.............................................................................................. 31
Normally, ‘Oracle text’ will be installed automatically. If the instance was aborted, ‘Oracle
text’ has to be installed later.
The following command will check if ‘Oracle text’ is available on your system:
$ORACLE_HOME/ctx/bin/ctxhx
Output:
• View
• Index
• Thumbnail
• Backup
The table tab_z403_directory.<lng> defines the storage directories for objects on the ALEPH
server. The table may be placed in the BIB library’s tab directory. If so, it is possible to store
the objects in different subdirectories, if more than one BIB library is active on the same
ALEPH installation. The table tab_z403_directory.<lng> may also be placed in the directory
$alephe_tab if storing related to a specific BIB library is not needed.
ADAM automatically creates new sub-directories under the defined storage directory, if the
maximum number of files is reached. The directory names are numeric (starting with 1). The
first 1000 objects are automatically stored in directory /1. Subsequent objects are stored in
directory /2 and so on.
BACKUP: When loading objects with the service adam_02, copies may remain in the
specified directory. These objects have the usage type BACKUP.
INDEX: An object was automatically built by ADAM when performing the Indexing
function.
VIEW: Usage type of all objects that are displayed in the OPAC.
Example:
! 1 2 3 4 5 6 7 8 9
!!!!!-!!!!!!![…]-!!!!!!!!!!!!!!!!!!!!-!-!-!!!!-!!!!!!!!!!-!!!!!!!!!!-!![…]!->
asf asf f-tn-movie.jpg
avi avi f-tn-movie.jpg
bmp bmp f-tn-image.jpg Y 100k convert
djv djv f-tn-image.jpg
djvu djvu f-tn-image.jpg
doc doc f-tn-doc.jpg Y 100k gen
ead ead f-tn-text.jpg
gif gif f-tn-image.jpg Y 100k convert
html html f-tn-link.jpg
ip2 ip2 f-tn-image.jpg
ipg ipg f-tn-image.jpg
jpg jpg f-tn-image.jpg Y 100k convert
mid mid f-tn-sound.jpg
mp3 mp3 f-tn-sound.jpg
mpg mpg f-tn-movie.jpg N
mpeg mpeg f-tn-movie.jpg N
pdf pdf f-tn-pdf.jpg gen
ppt ppt f-tn-ppt.gif Y 100k
ram ram f-tn-sound.jpg
System Librarian’s Guide - ADAM 7
October 5, 2010
rtf rtf f-tn-doc.jpg gen
sid sid f-tn-image.jpg
tif tif f-tn-image.jpg
txt txt f-tn-text.jpg N 100k txt
url url f-tn-link.jpg
wav wav f-tn-sound.jpg
wmv wmv f-tn-sound.jpg N
xls xsl f-tn-xcel.jpg
xml xml f-tn-XML.jpg Y 100k
##### f-tn-unknown.jpg
Column 9: Viewer
If you want to use an external viewer for displaying objects, the
pathname to the viewer’s executable file must be entered here. If this
column is left empty, the default plugin of the browser will be used.
• OBJECT-USAGE-TYP
The entries define the dropdown list for the object’s Usage Type. Note that the usage
type is connected to system functionality. Valid options are VIEW; THUMBNAIL,
and INDEX.
• OBJECT-CHAR-SET
The entries define the dropdown list for the field ‘Character set’ (Technical Data Tab),
which is used for full text indexing. Definitions in table
./alephe/unicode/tab_character_conversion_line have to be defined for each character
set which is in use. These lines define the required character conversion.
• OBJECT-RESOLUTION
The entries are used to define the dropdown list which contains the resolution for
image objects in tab “Technical Data”.
• OBJECT-COPYRIGHT-OWNER
This option is used for the dropdown list Copyright Owner in the Copyright tab
• OBJECT-COPYRIGHT-TYP
This option is used for the dropdown list Copyright Type in the Copyright tab.
• OBJECT-COPY-NOTICE-T
This option defines the dropdown list for Copyright Notice type in the Copyright tab.
Note that the code in column 4 of the table corresponds with the suffix to the file
media-permission in $alephe_root/www_f_<lng>.
setenv item_object_tree_style 1
setenv item_object_tree_style 2
The objects displayed are related to the ADM record, if the stated sublibrary in the field ‘Cat.
Sublibrary’ is assigned to the ADM library or if the field is left empty.
setenv item_object_tree_style 3
The objects displayed are related to bibliographic record (option 4), and to the ADM record
(option 2).
setenv item_object_tree_style 4
The display of the Objects List is defined in pc_tab_col.<lng>, which is located in the tab-
directory of your BIB library (lib01).
! 1 2 3 4 5 6 7 8 9 10
3.1 apache_media
For displaying objects in the OPAC, the directory apache_media must be created. In addition,
you have to define the variable “setenv APACHE_MEDIA” in file $alephe_root/aleph_start.
This directory contains temporary files and should be cleared regularly, for example, by using
[Util X/6].
aleph_start
surprise-a18(1) >>pwd
/exlibris/aleph/a18_1/alephe/apache/htdocs/exlibris/aleph/a18_1
surprise-a18(1) >>ls -l
total 6
drwxrwxr-x 6 aleph exlibris 512 Nov 20 02:07 aleph/
lrwxrwxrwx 1 aleph exlibris 34 Nov 20 02:07 apache_media ->
/exlibris/aleph/a18_1/apache_media/
lrwxrwxrwx 1 aleph exlibris 25 Nov 20 02:07 tmp ->
/exlibris/aleph/a18_1/tmp/
! 1 2 3
!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!>
########## get_buf_z403_media VIEW
In addition, further entries in this table are necessary for displaying the fields 655 (electronic
address, MAB) and 856 etc. (MARC) which contain URLs.
BUF-Z403 expand_doc_mab
! 2 3 4 5 6 7 8 9 10 11 12 13
!-!-!!!!!![…]-!!![…]-!!-!!-!!!!-!-!-!!!!!!!!!!-!!-!!!!!-!!!!!-[…]
[…]
7 L Photo 00 00 0040 S ## TN
8 L Media 00 00 0040 S ## MED
Note: It might be necessary to activate the additional columns through the files short-a-head
and short-a-body in $alephe_root/www_f_<lng>.
! 1 2 3
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!![…]
z403-title Title:^
z403-f-filename Filename:^
z403-object-extension File Extension:^
z403-original-filename Original Filename:^
z403-object-size SIZE Object Size:^
z403-note-1 File type:^
z403-update-date DATE Last Update:^
THUMBNAIL-LINK=1
If a thumbnail is linked to an object, the object will be displayed by clicking on the thumbnail.
If no object is linked, the object will be displayed in the Full view.
You may design different pages for Copyright Notices by copying the file “media-
permission” and adding specific suffixes, e. g. media-permission-free.
The field Copyright Notice Type in the GUI (Copyright Tab) defines which notice will be
displayed. The field is connected to the table ./[ADM_library]/tab/pc_tab_exp_field.<lng>.
The internal code is “OBJECT-COPY-NOTICE-T“:
! 1 2 3 4
!!!!!!!!!!!!!!!!!!!!-----!-!!!!!!!!!!!!!!!!!!!!!![…]-!!!!!!!!!!!!!!![…]
The entry in Column 4 must be identical with the suffix of the file “media-permission”.
! 2 3 4 5 6 7 8 9 10 11
!-!!!!!-!!!!!-!-!!-!!-!-!---!!-!!!!!-!!!!!!!!!!!!!!!!!!!!
[…]
H TXT W-nnn 00 01 W-Full text
H BASE W-nnn 00 00 Base
The size of full text indexing for files given by the URL is limited to 500KB. You may
increase the size by adding the following parameter to $alephe_root/pc_server_defaults:
This value defines which character set is chosen as a default when creating indexes on text
objects if no other value is entered in tab “Technical Data” of the object forms. The value for
ADAM-INDEX-CHAR-SET in tab100 may be up to 20 characters. The default character set
that is ISO 8859-1 (ISO-Latin).
Both import and export are based on XML-Files that contain specific sections for descriptive
metadata and technical metadata.
To upload objects into the system, it is usually necessary to run two services (adam-01 and
adam-02). Both are part of the services menu in the Cataloging module.
This service is used to create an XML-file which is required to upload files into the system
that do not have descriptive metadata (bibliographic records) or technical metadata (z403).
The XML-File created by this service contains descriptive and technical metadata generated
by using a template (z403_template.xml) that may be edited by the user.
The XML-file created by this service may be taken to load objects and metadata into the
system using service adam-02. An example of an XML template that can be edited by the user
can be found in ./[BIB_library]/tab.
The XML-File contains different sections for descriptive (<record>) and technical metadata
(<z403>).
<z403>
<z403-doc-number></z403-doc-number>
<z403-sequence></z403-sequence>
<z403-derived-from-sequence></z403-derived-from-sequence>
<z403-title></z403-title>
<z403-f-directory></z403-f-directory>
<z403-f-filename></z403-f-filename>
<z403-original-file-name></z403-original-file-name>
<z403-object-extension></z403-object-extension>
<z403-object-size></z403-object-size>
<z403-u-path></z403-u-path>
<z403-usage-type>VIEW</z403-usage-type>
[…]
</z403>
</file>
Note that the XML file will contain the digital object’s file name as the title if no explicit title
is specified in the <record>section of the template.
The standard is that per each object one descriptive record will be created. Uploading multiple
objects with just one descriptive record can be done by editing the XML file. Limit the
<record> section to only one appearance within the XML file by deleting further
<record>sectors.
This service takes the XML file generated with adam-02 or any other XML file with
appropriate format and content and runs the upload into the system. This service creates
records in z00 (bibliographic) and z403 (technical metadata) according to the definitions in
the XML file.
Note that the XML file to be loaded is required to have the same name of the directory it is in
plus the file extension “XML”, otherwise it will not be loaded.
It is possible to upload digital objects to existing bibliographic records without changing the
descriptive metadata (bibliographic). For this purpose, edit the XML file generated with
Note that if the system-number does not exist in the catalog, no object will be uploaded.
You can limit this service on a range of records contained in an input file created by service p-
ret-01. Note that the output directory will automatically be created as subdirectory to the
library’s export directory.
To run this service you can define a range of records or use an input file that may be created
by ret-01.
6.2.5 Create Digital Objects Upload File from DigiTool Export (adam-08)
This service can be used to convert exported DigiTool data (digital entities) into a format
which can be handled by adam-02 service. The objects and XML files have to be transferred
to the ADAM import directory in order to be available for adam-08. It is only possible to
convert data of usage type "VIEW".
The table pc_tab_exp_field.<lng> contains selective lists for fields of the service. The
following values can be user-defined:
!!
!! For P-ADAM-10-SORT you can use (= Z403-......)
!! REC-KEY, F-FILIE-NAME, OPEN-DATE, UPDATE-DATE, EXPIRY-DATE
!! and all values of COL.4 of P-ADAM-10-FIELD
!! in any combinations to define a set of sort-keys
!!
P-ADAM-10-SORT L Record Key REC-KEY
P-ADAM-10-SORT L Storage directory | File Name F-DIRECTORY|F-
FILENAME
P-ADAM-10-SORT L Cataloger | Usage type | Object title CATALOGER|USAGE-
TYPE|TITLE
P-ADAM-10-SORT
The entries define the dropdown list for the sort type
P-ADAM-10-USAGE
The entries define the dropdown list for the different object types.
P-ADAM-10-FIELD
The entries define the dropdown list for the different fields.
• Rebuild entire Full Text index - rebuilds the entire Full Text index, deleting and
rebuilding the tables.
• Update Full Text index - updates the Full Text index without deleting the tables.
7.1 Z403
The technical metadata of the digital objects are handled by the z403 table. The z403 is
created in the BIB library.
7.2 Z91
The z91 table is also created in the BIB library, as well as in all other bases where the
indexing process UE-01 is running. This table contains the indices of the fulltext indexing of
text-based objects like MS Word or PDF files.
7.3 Z56
The z56 table is created in the vir01 library and limits access for the object by allowing only a
certain number of simultaneous accesses of digital objects in the OPAC.
If an object is opened in the OPAC, a session will be registered and any further session will
be compared to the entry in the field, z403_NO_OF_COPIES. If the defined limit is
exceeded, the patron cannot open the object. A session will be automatically terminated after
10 min., if it is not terminated by the patron before that.
The following configurations are required in order to implement the ADAM Scan Jobs
functionality:
• tab100
To activate the ALEPH Scan Interface, add the following parameter to the tab100 table of the
BIB library:
CREATE-SCAN-JOB=Y
• pc_tab_exp_field.lng
The selection menus for scan parameters have to be added to the pc_tab_exp_field.lng table of
the BIB library. For example:
! 1 2 3 4
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-----!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!
OBJECT-RESOLUTION L High Resolution high
System Librarian’s Guide - ADAM 29
October 5, 2010
OBJECT-RESOLUTION L Low Resolution low
OBJECT-RESOLUTION L Medium Resolution medium
• edit_doc_999.lng
To display the tag "SCJ" in the record's full view, a definition for SCJ tag has to be added to
the edit_doc_999.lng table of the BIB library. For example:
Scan Job Details are displayed in a separate window which can be opened from the Search
Tab’s Full Record display, by double-clicking the tag SCJ. The display is based on XML
format. Definitions are in the form "scan-job-expand".
• tab_expand
Information about the scan job must not be provided in internal format, but rather in external
format, for example to replace the codes of the sublibrary into normal text. The new expand
routine "expand_doc_bib_scj" must be used to create an external field (e.g. 076) which
contains the following subfields:
The "expand_doc_bib_scj" routine must be defined in the tab_expand table of the BIB library,
for expand menu "WWW-X". The parameter CODE= can be used to define the external field
which will contain the scan job details. For example:
! 1 2 3
!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!![!!!
WWW-X expand_doc_bib_scj CODE=076