introducing aleph version 20.0 ex libris technical seminar march 10, tel aviv 14:00 to 15:30 yoel...

Introducing Aleph Version 20.0

Ex Libris Technical SeminarMarch 10, Tel Aviv14:00 to 15:30

Yoel KortickAleph support team leader

2

Copyright Statement

All of the information and material inclusive of text, images, logos, product names is either the property of, or used with permission by Ex Libris Ltd. The information may not be distributed, modified, displayed, reproduced – in whole or in part – without the prior written permission of Ex Libris Ltd.

TRADEMARKS Ex Libris, the Ex Libris logo, Aleph, SFX, SFXIT, MetaLib, DigiTool, Verde, Primo, Voyager, MetaSearch, MetaIndex and other Ex Libris products and services referenced herein are trademarks of Ex Libris, and may be registered in certain jurisdictions. All other product names, company names, marks and logos referenced may be trademarks of their respective owners.

DISCLAIMER The information contained in this document is compiled from various sources and provided on an "AS IS" basis for general information purposes only without any representations, conditions or warranties whether express or implied, including any implied warranties of satisfactory quality, completeness, accuracy or fitness for a particular purpose.

Ex Libris, its subsidiaries and related corporations ("Ex Libris Group") disclaim any and all liability for all use of this information, including losses, damages, claims or expenses any person may incur as a result of the use of this information, even if advised of the possibility of such loss or damage.

© Ex Libris Ltd., 2008

3

Agenda

• Overview of Aleph version 20.0 • Specific developments - effecting a

wide customer/user group base

4

Additional V20.0 Sessions • Acquisitions developments - Tuesday March

10th at 16:00 • OPAC and cataloging developments -

Thursday March 12th at 9:00 • A Closer Look at Service Pack Enhancements

- Thursday March 12th at 14:00

5

Acquisitions highlights• Bulk Ordering and Arrival - New bulk ordering

and arrival functionality enables ways of handling orders and receipts in bulk for speed and efficiency.

• Automatic Creation of Monograph - Type Items dependent on order type

• Load Invoice and Line Items (acq-32). A service which allows Aleph to create general invoice and line items from an xml input file.

• General invoice payment log - A new acquisitions log has been created to enable the recording and displaying of invoice payment statuses.

6

Authorities Highlights• Update of authority records from the

bibliographic library browse screen.• Correct headings in bibliographic library from

browse list is now possible for headings which have an associated authority record.

7

Cataloging Highlights• New list of values in pull down box for fixed

fields.• Support of UNIMARC update 5 for UNIMARC 4XX

field parallel links.• Service “Retrieve Records by Direct Index (ret-

06)” which works on input file of direct index values.

• Item management tool – allows for specific items to be chosen from a long item list to be edited and saved separately off-line

8

Circulation Highlights• Rush hold requests – ability for patrons to create

rush hold requests for items in Cataloging process• Audio warning for the return of items with hold

request• Ability to change due dates of multiple items in

loan session and in loan list

9

Web OPAC Highlights

• Security enhancements to prevent XSS breakthrough (Cross Site Scripting)

• Patron notification in web OPAC – Patron can receive warning for each, delinquency and overdue items upon logging in to web OPAC

• Patron can view accrued fines for items not yet returned

• Search Keywords in headings – ability to search for keywords within the browse heading list

10

Customer Collaboration

All developments have been done in close collaboration with one or more of the following

• User’s groups/Product Working Groups• Specific customers• Ex Libris offices and distributors• Product Management

11

Customer collaboration• This is an approval letter from a customer representing a

user’s group regarding the changes to manage-70• All names have been removed for privacy purposes

12

Customer collaboration• This is an approval letter from the IGeLU Aleph PWG

regarding the “multi line change date” development• All names have been removed for privacy purposes

13

Specific developments• For a full list of developments see the Doc

Portal: Aleph > Tree Search > 20

• Let’s take a brief look at this document

14

Overall Technical Information • Oracle 11

aleph_start: setenv ORACLE_VERSION 11 • Linux Red Hat AS/ES 5 – 64 bit

Advanced Server and Enterprise Server 5 • Google Books Service – also downgraded to lower

versions via service pack• SMTP mail compatibility – also downgraded to

lower versions• Automatic implementation notes mechanism

added to the SP

15

Overall Technical Data - StandardsSupport for standards:• UNIMARC update 5• Danzig profile

• The DanZIG profile specifies the guidelines for systems interconnection between library applications in Denmark

• Primarily based on the ANSI/NISO Z39.50, a.k.a. ISO 23950

17

Table of contents part 1 Cataloging and authority maintenanceSearch / Correct Headings in Cataloging ModuleHeadings link to AUT recordExpedite editing of long lists of item recordsCataloging aid for fixed field coded value

Circulation and web OPACSelecting multiple loans for change dateDelinquency warning in the WWW OPACAccrued Patron Fines in the WWW OPACServices Item status filterAudio Warning for return of item on hold

18

Table of contents part 2AcquisitionsItem default values for monograph orders

System and multi-moduleSearch Keywords in HeadingsRetrieve Record Keys Manage-70Changes to email authentication optionsRush cataloging requestX-Service for ItemsService ret-06 to retrieve records from list of direct index

19

Search Headings in Cataloging Module

• A2001.1 (rpv # 015168) • Correct Heading Improvement

Link back to table of contents

20


• In GUI-SEARCH-BROWSE-Heading List, it is now possible to 'Correct Heading' for BIB records which have an associated Authority.

• Until now, the system enabled the 'Correct Heading' button only in cases where the selected entry is related to a BIB record/s (with no AUT associated).


21

Search Headings in Cataloging Module• In cases where the heading was linked

to both BIB/s and AUT, there was no option to correct the heading via GUI-Search-Browse-Headings List.

• This functionality has been enhanced so that the 'Correct Heading' button is now enabled also when a heading with an associated BIB/s and AUT record is marked.


22

Search Headings in Cataloging Module• When the 'Correct Heading' is called for

headings which are linked to an AUT record, a message pops-up: "Selected headings include authority related headings. Are you sure you want to correct the headings? Yes/No".

• Choosing Yes will open the 'Correct Heading' dialog; enabling the user to correct heading of the related BIB record/s.


23

Search Headings in Cataloging Module• Once the Correct Heading action is

completed, the system activates all related actions. I.e. Update is made on the headings of all related BIB documents and the AUT link is broken.

• The updated heading may or may not be linked to a different AUT records by ue_08 execution


24

Search Headings in Cataloging Module• A new user privilege has been added for this

action.

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cd $alephe_tab

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>grep CORRECT-HEAD-LINK user_function.eng

HEADINGS-UPDATE L Catalog Headings CORRECT-HEAD-LINK L Heading - Correction of AUT linked doc


25

Search Headings in Cataloging Module• This new access right should be set in the BIB

library access rights.• Here user A_YOEL has the permission in USM01


26

Search Headings in Cataloging Module• We have two records with general subject

heading “Library softwar”

• This heading is connected to an authority record


27

Search Headings in Cataloging Module• Here is the authority record:

• Note that in the authority record the word “softwar” is spelled wrong:


28


• Note that in the corresponding bibliographic records the word “softwar” is spelled wrong:


29

Search Headings in Cataloging Module• While logged in as user A_YOEL the staff user selects the

heading in the bibliographic library and clicks “correct heading”


30

Search Headings in Cataloging Module• The following message appears and the staff user selects Yes


31

Search Headings in Cataloging Module• The staff user changes the heading from “Library softwar” to

“Library software” and clicks “Accept”


32

Search Headings in Cataloging Module• Update is made on the headings of all related BIB

documents and the AUT link is broken. The updated heading may or may not be linked to a different AUT records by ue_08 execution

Both bibliographic records were updated


33

Search Headings in Cataloging Module• The link to the authority record was broken


34

Search Headings in Cataloging Module• The message which the user received when clicking

“Correct Heading” comes from the following line in AL500\Alephcom\Tab\Eng\Message.dat

CorrectHeadingAuthority #ALEPH GUI YN Q Selected headings include authority related headings. Are you sure you want to correct the headings?


35

Search Headings in Cataloging Module• Here is pre-version 20. When a heading with an authority link is

selected the “Correct Heading” option is not active

Not active

Has authority link


36

Headings link to AUT record

• A2003.3 (rpv # 015101 ) • Headings link to AUT record


37


• New button 'Catalog‘ has been added to GUI-Search-Browse-Reference List.

• The staff user arrives to the this button after doing

1. Browse2. selecting a heading which has a reference3. clicking expand 4. receiving the “Reference List” window.


38


• Clicking this button enables the staff user to directly transfer the Authority record to the Records tab of the Cataloging module.

• This allows the user to make changes in the authority cataloging record.


39

Headings link to AUT record• Here in a version earlier than 20 we have browsed for “Bible.O.T.

Pentateuch”, selected the heading, and clicked “expand”.• We receive the “Reference list” window


40

Headings link to AUT record• The “Reference list” window contains only

buttons “jump”, “close” and “help”.


41

• Now in version 20 we have browsed for “Bible.O.T. Pentateuch” and selected the heading.



42

• After clicking expand we receive the “Reference list” window with a new button “catalog”

Button added in version 20



43

• Clicking this button automatically opens the authority record in the cataloging edit mode.



44

• A2002.5 • Expedite editing of long lists of item records

Expedite editing of long lists of item records


45

• Why was this development requested?• Making corrections to specific item fields may

require working on many of the Item List items one by one.

• This kind of work may be excruciating with long lists of items.

• Identifying a large number of items in a long items list, and moving between the required items in the list can also very easily lead to mistakes caused by choosing the wrong item.

• This can be solved by supplying a tool for update of a items while working on a filtered list of items.

Expedite editing of long lists of item records


46

• This new development does the following:• Provides an item update interface which enables

the user to:1. Add items into a work set.2. View the work set.3. Carry out offline update work on the items of the

work set.4. Upload the offline items changes into the

database in a single upload action.

Editing long lists of item records


47

• From the cataloging module items tab item list one or more items may be selected and then the new “add to set” button may be clicked



48

• The user will get the following messageEditing long lists of item records


49

• When adding an item to the working set, the system will first check if the user already has a working set. The working set will be emptied before the new item is added in if the set is populated with items that are linked to another ADM record. A warning message will warn the user of this condition before the delete is done.

• If the working set exists and its items are linked to the same ADM record as the item that is being added - the item will simply be appended to the existing set.



50

• The items in the set may be edited offline by using the following menu:



51

• The following window will open allowing for the items to be edited off line



52

• One or more items may then be edited. • Clicking “Save set” will take the items which have

been edited and update them accordingly in the library and remove them from the set



53

• Here the user adds “ATLAS” collection for barcode 50239-70 and clicks “Save Set”



54

• The item is no longer in the setEditing long lists of item records


55

• The item has been updated on the serverEditing long lists of item records


56

• A2022 9 • Cataloging aid for fixed field coded value

Cataloging aid for fixed fields


57

Cataloging aid for fixed fields• Cataloging Forms- List of Values in Fixed-

Length Fields Forms• The Cataloging Forms of Fixed-length Fields

have been enhanced to support the option to display list of possible values and description for certain positions.

• A new expand button is displayed next to the fields for which the library decides to implement this option. Once the expand button is clicked, a pop-up dialog box appears with list of pre-defined values and descriptions.


58

Cataloging aid for fixed fields• For user convenience; the "Valid Values" list

can be sorted by value or description. • It also includes 'Jump to' and "Starting Point"

options.• For more information, refer to System Librarian

Guide-Cataloging: List of Values in Fixed-Length Fields Forms.


59

Cataloging aid for fixed fields• A new Oracle table, Z112, has been added to BIB

library. • This table defines valid values and descriptions

for cataloging forms of Fixed-Length fields. • For more information, refer to System Librarian

Guide-Cataloging: List of Values in Fixed-Length Fields Forms.


60

Cataloging aid for fixed fields• The list of valid values and their description is defined in

configuration table/s.• The table file name/s can be decided by the library. The

language extension <lng> must be part of the file name. There should be table/s per language.

• Exlibris sample demo table is located in ./usm01/tab directory and named as: tag_values.eng.

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>dt

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>ls -lrt tag_values.eng

-rw-rw-r-- 1 aleph exlibris 10656 Jul 28 14:42 tag_values.eng

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>


61

Cataloging aid for fixed fields• Table structure:• Col.1 – Identifier for the list (upper case string, up to 30

characters). The identifier represents list of values and description for certain martial type/tag/position. This identifier should be set in the 'Fixed-Length Form' file. Each field in the 'Fixed-Length Form' that calls the specific identifier will list all Values and Descriptions of the quoted identifier. Each library can decide its own identifier codes.

• Col. 2 – Value that is valid for the identifier (up to 10 characters)

• Col.3 – Description of the value (up to 50 characters)


62

• Let’s look at column 1 of tag_values.eng

! COL.1 defines the identifier that represent list of valid values.

! It can be any string defined by the library. For example, identifier

! "LANGUAGE" can be used to define list of valid codes and description for

! tag 008 position 35-37 (language).

! In order to use the "LANGUAGE" identifier list in GUI-Cataloging-008 form,

! the "LANGUAGE" identifier must be implanted it in the relevant

! 008 form (e.g. ./xxx01/pc_tab/catalog/008_xx.lng).

! Once the identifiers are set or updated in this table, their content should

! be loaded into an Oracle table: Z112. The load of the configuration table

! into Z112 can be done using the service: "Import Database Tables - With

! Checks (file-06)".



63

• Here is part of of $data_tab/tag_values.eng

! 1 2 3

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!->

PLACE-OF-PUBLICATION ag Argentina

PLACE-OF-PUBLICATION aku Alaska

PLACE-OF-PUBLICATION efr Efrat

LANGUAGE alb Albanian

LANGUAGE arm Armenian

FORM-OF-COMPOSITION-MU sn Sonatas

FORM-OF-COMPOSITION-MU wz Waltzes

ILLUSTRATION-CODE-BK a Illustrations

ILLUSTRATION-CODE-BK b Maps

We will see specifically what happens to this



64

• The table is transferred to $data_files directory and uploaded to Z112 via file-06

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>dt

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cp tag_values.eng $data_files/



65

• After running file_06 the Z112 is updated• Here is one line in upload file and in UTIL F 4

! 1 2 3

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!->

PLACE-OF-PUBLICATION efr Efrat



66

• Once the list of identifiers is set in the valid values table/s, and the data is loaded into Z112 Oracle table, the GUI "Fixed Length Forms" should be amended to call the relevant identifiers.

• This will cause the relevant list to be called-up when a "Fixed-length Form" is opened at GUI-Cataloging-Forms.

• For this purpose, each of the forms that should contain list of valid values and description must be adjusted to contain the relevant identifier.



67

• For example: • To enable the values and description list in 008 form

of BK format, the file $data_root/pc_tab/catalog/008_bk.eng must be set with relevant identifiers.

• The identifier should be set next to the fields. • Two percent signs (%%) should precede the

identifier code.



68

• The parameters • PLACE-OF-PUBLICATION • and LANGUAGE appear as • follows in file 008_bk.eng in• Directory • $data_root/pc_tab/catalog



69

• Anywhere where there are %% in the form there will be three dots.• Clicking the three dots will bring the values from the Z112 table



70

• A2001.4 • Select multiple Loans for the

Change Date function

Selecting multiple loans - change date


71

• The system will :• Allow the privileged staff to select more than one

loan, and change its date manually.• This option will be available from:

• The patron loan list.• The Loan Session interface.



72

• Here the circulation librarian has loaned 4 items to patron ID 942 and all 4 items appear in the loan session interface



73

• Currently all items are due on March 12, 2009 at 10:00 PM

• Using the control key and the mouse the circulation librarian selects the 1st, 3rd and 4th item and then clicks “Change date” in the loan session interface



74

• The circulation librarian selects a new date of March 3rd at 10:00 PM and click OK



75

• The three selected items have had their due dates changed.

• The items for which a change has occurred remain selected so the librarian may distinguish tem from those which have not changed.



76

• The same functionality exists in the loan listSelecting multiple loans - change date


77

• A2001.5 (rpv 15426)• OPAC delinquencies warning

Delinquency warning in WWW OPAC

• A2003.1 (rpv 15426) • OPAC cash and overdue warnings


78

Delinquency warning in WWW OPAC• When a patron who has delinquencies and/or

unpaid cash transaction and/or overdue loans, is logging into WWW OPAC he will be prompted by a screen with relevant alert.

• The "Patron Notice" screen will display the relevant alerts (delinquency warning and/or unpaid cash transaction and/or overdue items).

• Upon clicking the “Continue” button, the patron will have the option to proceed with WEB OPAC activity as usual.


79

Delinquency warning in WWW OPAC• To implement this new feature, the following should be set:• New HTML page: ./alephe/www_f_eng/patron-notice• Three new variables added to ./alephe/www_server.conf

1. patron_notice_delinq - value can be y/n 2. patron_notice_cash - value can be y/n3. patron_notice_overdue - value can be y/n

• Y – When patron logging into WWW OPAC, the system will check for patron delinquency/cash transaction/overdue items and show relevant notice if relevant.

• N – Default. No checks are done. The notice page will not be called at all.


80

• Here the first criteria exists: the web OPAC html screen is present in www_f_lng

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cd $alephe_root/www_f_eng

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>ls -lrt patron-notice

-rw-rw-r-- 1 aleph exlibris 2774 Nov 10 10:22 patron-notice



81

• Here the second criteria exists: the new variables are present in www_server.conf with value Y

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cd $alephe_root

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>grep patron_notice www_server.conf

setenv patron_notice_delinq Y

setenv patron_notice_cash Y

setenv patron_notice_overdue Y



82

• Patron “Jimmy Librarystein” has overdue items and owes money



83

• Patron “Jimmy Librarystein” logs into the web OPAC



84

• And then receives these messages



85

• The error messages on the screen are easily configurable because they come from the html

page patron-notice:<span class="text3">Dear $1000 !</span>

<p class="text1" style="display: $2000">You have delinquencies in library $2100.</p>

<p class="text1" style="display: $2500">You have pending cash transactions in library $2600.</p>

<p class="text1" style="display: $3000">You have overdue items currently on loan in library $3100.</p>

<p class="text1">Please check your library card for this information!<br> Your library</p>

86

• Note that when Jimmy Librarystein logged in he received messages for “pending cash transaction” and “overdue items”.

• He did not receive a message for delinquencies even though it appears on the html screen patron-notice.

• The system knows only to display lines for which are relevant for the particular patron.

• Now we will give Jimmy a delinquency



87

• He now has global block 02 “Disruptive behavior in library”

il-aleph07.corp.exlibrisgroup.com-20(1) USM50-YOELK>>grep "02 1" $data_tab/tab_delinq.eng

02 1 L Disruptive behaviour in library



88

• Now when he logs into web OPAC he also receives a message on the delinquency



89

Accrued Patron Fines in WWW OPAC

• A2003 2 • Web OPAC “Accrued” Patron

Fines


90


• In all versions before version 20 a patron could view his non paid cash transactions via the web OPAC.

• These would include only “registered” transactions, and as a result he would not know, for example, how much money he owes on a currently overdue loan which he has not yet returned.

• This is because Aleph would “register” the amount owed only after the item was returned.


91

• It is now possible to view “accrued” fines.• In this case an “accrued” fine is money owed

for an overdue item which has not yet been returned.

• For example, if an item is still on loan, but is late by 5 open days, and tab 16 is defined to make a fine of 1 dollar per open day, then the accrued fine would be 5 dollars.



92

• Patron Jimmy Smith owes 11.50 for a “Late return” which he has already returned.



93

• After logging into the web and clicking “My Library Card” he sees that he owes 11.50 and has no “accrued” fines



94

• Jimmy Smith has now loaned an item and currently owes 13.50 = 11.00 for the late return he already had and 2.00 for making the loan.

• His current loan is not yet overdue so he has no accrued fines.



95

• The situation is correctly updated in the web OPAC



96

usm50@ALEPH11> select Z36_LOAN_DATE,Z36_DUE_DATE from Z36 where Z36_ID = '9424969';

Z36_LOAN_DATE Z36_DUE_DATE

------------- ------------

20081113 20081211

1 row selected.

usm50@ALEPH11> update Z36 set Z36_LOAN_DATE = 20080813 where Z36_ID = '9424969';

1 row updated.

usm50@ALEPH11> update Z36 set Z36_DUE_DATE = 20080911 where Z36_ID = '9424969';

1 row updated.

usm50@ALEPH11> commit;

Commit complete.

• Via SQL we will make Jimmy Smith’s Loan be late, and he will not yet return it.

• We are using SQL so that we can simulate what will happen 3 months from now when Jimmy has not returned the item.

Below we move these dates back three months



97

• Here is the late item on loan

• He owes 13.50• He has so far accrued an additional 25.50 on his

current loan



98

He owes 13.50

He has so far accrued an additional 25.50



99

• The html screens which include this new development are bor-info and bor-info-single-adm in the $alephe_root/www_f_lng directory.



100

Services Item status filter

• A2002 3 (rpv 15187) • Services Item Status Filter


101


• Before version 18 many of the services allowed the staff user to choose only one item status at a time.

• This is because the item statuses came for a pull down box with one item status per line.


102

• For example, here is the item status option in the cir-04 service before version 20

Can only choose one item status



103

• The method of choosing the item status has now changed for the following services:

•Loan report (cir-04)•Hold Shelf Report (cir-06)•Report of “Lost” & “Claimed Returned” Items (cir-16)•Overdue and lost Billing Notices (cir-50)•Overdue and Lost Billing Summary (cir-51)•Overdue Summary Single Letter (cir-52)



104

• The Item Statuses field for these circulation batch services has been changed from a drop down menu (that allows selecting a single/All item status) to an expand check box menu that allows selecting single/few/All statuses.

• 'Include/Exclude Item Status' field precedes the "Item Statuses" field. This field indicates whether the selected statuses should be excluded or included by the batch.



105

• In version 20 the item statuses are chosen like this:



106

• Before version 20

• Version 20


Can choose multiple item statuses



107

• Before version 20

• Version 20


Can choose multiple item statuses



108

• It is now possible to set up an audio warning for the return of an item which is on hold.

• The parameter OnHoldReturn has been added to the [ErrorAction] section of circ.ini

Audio warning – return requested item


109

• If this is in the [ErrorAction] section of circ.iniOnHoldReturn=Y,F,has_hold.wav

• Then the file ..\AL500\alephcom\tab\sound\has_hold.wav will play when an item which has a hold request is returned.



110

• If this is in the [ErrorAction] section of circ.iniOnHoldReturn=Y,S,Beep

• Then the windows beep will play when an item which has a hold request is returned.



111

• Any standard windows sound may be activated or a personal sound file



112

Item default values - monograph orders

• A2002 1 (rpv 15218) • Automatic Creation of

Monograph-type Items in Acquisitions


113

Item default values - monograph orders• The flow of automatic creation of items when

monograph order is created has been enhanced.• It is now possible to define the item default values

based on the order material type.• In order to support this flow, a new column, Col. 2

– Order Material Type, has been added to tab36 of the ADM library.


114

• The new column should be populated with order material type code (up to 2 characters long, as defined in ACQ_ORDER_MATERIAL menu of the pc_tab_exp_field.lng of the ADM library).

• The enhanced tab36 table has now two filters (keys), Col.1 – Order Sublibrary and Col.2 – Order Material Type (new column).



115

• When the system automatically creates Monograph-type items in Acquisitions, it

1. reads all orders with sublibrary and order material type as defined in col. 1 and 2

2. sets the items with values as defined in col.3 and onwards: Col.3 – Item Status, Col. 4 – Item Material Type, Col.5 – Item Collection, Col.6 – Item Call Number and Col.7 – Item Call Number Type.



116

! COL 1. 5; ALPHA_NUM, UPPER; #;

! Sublibrary;

! Sublibrary;

! COL 2. 2; NUM; ;

! Item status;

! Item status;

! COL 3. 5; ALPHA, UPPER; ;

! Material type;

! Material type;

! COL 4. 5; ALPHA_NUM, UPPER; ;

! Collection;

! Collection;

! COL 5. 40; TEXT; ;

! Location;

! Location;

! COL 6. 1; NUM; ;

! Location type;

! Location type;

Item default values - monograph ordersTab36 before version 20


117

! COL 1. 5; ALPHA_NUM, UPPER; #;

! Sublibrary filter;

! Sublibrary filter;

! COL 2. 2; ALPHA_NUM; #;

! Order material type filter;

! Order material type filter;

! COL 3. 2; NUM; ;

! Item status;

! Item status;

! COL 4. 5; ALPHA, UPPER; ;

! Item material type;

! Item material type;

! COL 5. 5; ALPHA_NUM, UPPER; ;

! Item collection;

! Item collection;

! COL 6. 40; TEXT; ;

! Item call number;

! Item call number;

! COL 7. 1; NUM; ;

! Item call number type;

! Item call number type;

New


Tab36 version 20 and up


118

• We have these order material types

il-aleph07.corp.exlibrisgroup.com-20(1) USM50-YOELK>>grep ACQ_ORDER_MATERIAL pc_tab_exp_field.eng

ACQ_ORDER_MATERIAL L Monograph M

ACQ_ORDER_MATERIAL L Serial SE

ACQ_ORDER_MATERIAL L Data file DA

ACQ_ORDER_MATERIAL L Information record IN

ACQ_ORDER_MATERIAL L Microform MF

ACQ_ORDER_MATERIAL L Map MP

ACQ_ORDER_MATERIAL L Recording RE



119

• Here in tab36 we state that if the order is for 1. sub library MED and order material type MP (map) then it should get item

statues 01, item material type MAP and collection GEN.2. sub library MED and order material type M (Monograph) then it should get

item status 02, item material type BOOK and collection GEN.

! 1 2 3 4 5 6 7

!!!!!-!!-!!-!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!

MED MP 01 MAP GEN 0

MED M 02 BOOK GEN 0



120

• Here order number 51892 has material type MP and sub library MED


Version 20


121

• It therefore has item status 01 and item material type MAP


Version 20


122

• Here order number 51893 has material type M and sub library MED


Version 20


123

• It therefore has item status 02 and item material type BOOK


Version 20


124

Search keywords in headings

• A2001.3 (rpv # 015348 ) – Keyword search of headings


125


• The GUI and Web search- Browse screen has been enhanced to enable the users to search keywords in the subject headings.

• For this purpose, a new check box labeled “Search Keywords in headings” has been added to the screen.

Introduction


126


• Populating keywords in the “Enter Starting Text” text box and checking the new check box will trigger the system to return a list of headings that contain the requested keywords.

• When the new check box is checked in the GUI, the “Enter Include Text” text box will be disabled.

Introduction


127

Search keywords in headings• Here we have done browse for titles using the word

“science” and we have not checked the “Search keywords in headings” checkbox.

• We receive headings with the word science at the beginning of the title

Not checked


128


“science” and we have checked the “Search keywords in headings” checkbox.

• We receive headings with the word science somewhere in the title

checked


129


“Library” and we have not checked the “Search keywords in headings” checkbox.

• We receive headings with the word “Library” at the beginning of the title

Not checked


130


“Library” and we have checked the “Search keywords in headings” checkbox.

• We receive headings with the word “Library” somewhere in the title

checked


131


• In the GUI the option will by default appear and there is no need to do anything.

• The option comes from the file AL500\Alephcom\tab\eng\window.dat in the following line:

SearchBrowse.Check.Searchkeyword #Search keyword in headings


132


• In the web OPAC the “Search keyword in headings“ option has been added to the $alephe_root/www_f_lng/scan-include-2 screen.

• It appears as follows in the default setup:<table cellspacing=2 border=0 width =100%> <tr> <td class=td2 width=20% nowrap valign=middle>Type word or phrase: </td> <td class=td2 valign=top> <input size=29 name="scan_start“ maxlength=100 value="$0100"> <input type="checkbox"

name="scan_include“ value= "Y“ $$0800-C"Y"> Search keyword in headings </td> </tr> <tr> <td class=td2 valign=middle nowrap>Select index to browse: </td> <td class=td2 valign=top> <select name=scan_code> <option value=TIT $$5000-S"TIT">Title</option>


133


• In order to enable Keyword Search in Heading List, Z01x must be created for Z01- Access Heading records.

• Note that indexing Z01x required oracle user with “JOB CREATE” granted.

• Define Z01x in the file_list of the BIB Library (XXX01) as in the following sample of usm01/file_list

Step one


134


• After adding this you must build the table via util A 17 1

!1 2 3 4 5 6

!!!-!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!

TAB z01x 2M 0K ts0

IND z01x_id 1M 0K ts1

INX z01x_id1 1M 0K ts1

Step one


135


• In order to create Z01x for current Z01 heading records, in BIB library run the script : p_fill_z01x.

• Sample of running the script in USM01 library

Step two

il-aleph07 USM01-YOELK>>ap

il-aleph07 USM01-YOELK>>csh -f p_fill_z01x USM01


136


• This script performs the following actions:1. Lock library2. Drop indexes on z01x (if exist)3. For each Z01 record, create z01x records4. Create indexes for z01x5. Unlock library

Step two


137


• At this stage Z01x records are created and indexed and keyword search in heading is enabled via OPAC and GUI.

• Note that after updating/loading headings using a bulk mode (batch services), the Z01x script should be run.

• This means that after submitting the below batch services, the p_fill_z01x script should be run so that z01X records will be updated/created and indexed.

• Update Headings Index (manage-02)• Pre-Enrich Bibliographic Headings Based on the Authority

Database (manage-102)• Alphabetize Long Headings (manage-17)

Step two


138


• To ensure that the Z01x mechanism is optimized, the optimize procedure should be set in job_list.

• Following is a sample of setting Z01x optimize procedure for USM01 BIB library:

Step three

! 2 3 4 5 6 7

!!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!

05 12:20:00 Y USM01 optimize_z01x_context_index USM01


139


• We have the following subject heading:

Integrated Library Systems -- Easy to use and easy to configure -- Aleph 500 – [something more specific]

• This heading appears many times, and the user browsing the headings may want only those which contain specific text.

• We have the following subject heading:


140


Not checked

Four headings include the string “batch services”Link back to table of contents

141

Search keywords in headings• Now we will put the word “Services” in the

“Enter include text” and we will check the box “Search keyword in headings”.

• We will then see that the user easily and conveniently sees only those headings which have Integrated Library Systems -- Easy to use and easy to configure -- Aleph 500 – [something more specific] and also contain the string “batch services”.


142


Now the user has found only those subject headings with the string “batch services”


143

Retrieve Record Keys Manage-70

A2002.4 (rpv 15214) Retrieve Record Keys Manage-70


144

• Nine new convert routines have been added to the existing service “manage-70 retrieve record keys”:

• BIB-TO-HOL - converts BIB record numbers to HOL record numbers • ITEMS-TO-HOL - converts item record keys to HOL record numbers• BARCODE-TO-HOL - converts item BARCODE identifiers to HOL record

numbers• HOL-TO-BIB - converts HOL record numbers to BIB record numbers• HOL-TO-ITEM - converts HOL record numbers to item record keys• HOL-TO-BARCODE - converts HOL record numbers to item BARCODE

identifiers• BARCODE-TO-BIB - converts item BARCODE identifiers to BIB record numbers• BIB-TO-BARCODE - converts BIB record numbers to item BARCODE identifiers• ADM-TO-BIB – converts ADM record numbers to BIB record numbers



145

• These are the convert routines that existed before version 20:

il-aleph02-a18(1) >>cd $aleph_root/pc_b_eng

il-aleph02-a18(1) >>grep display p-manage-70.xml

<display>ADM-TO-ITEM</display>

<display>ADM-TO-ORDER</display>

<display>BARCODE-TO-ITEM</display>

<display>BIB-TO-ADM</display>

<display>BIB-TO-ITEM</display>

<display>BIB-TO-ORDER</display>

<display>ITEM-TO-BIB</display>

<display>ORDER-TO-BIB</display>



146

• These are the convert routines that exist in version 20:

il-aleph02-a18(1) >>cd $aleph_root/pc_b_eng

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>grep display p-manage-70.xml

<display>ADM-TO-ITEM</display>

<display>ADM-TO-ORDER</display>

<display>BARCODE-TO-ITEM</display>

<display>BIB-TO-ADM</display>

<display>BIB-TO-ITEM</display>

<display>BIB-TO-ORDER</display>

<display>ITEM-TO-BIB</display>

<display>ORDER-TO-BIB</display>

<display>BIB-TO-HOL</display>

<display>ITEM-TO-HOL</display>

<display>BARCODE-TO-HOL</display>

<display>HOL-TO-BIB</display>

<display>HOL-TO-ITEM</display>

<display>HOL-TO-BARCODE</display>

<display>BARCODE-TO-BIB</display>

<display>BIB-TO-BARCODE</display>

<display>ADM-TO-BIB</display>

New in version 20



147

• In this brief presentation we will show two of these new procedures:

• BARCODE-TO-BIB• BIB-TO-HOL



148

• Here we run a standard retrieval service



149

• Now we want all of the Holding records for these Bibliographic records

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cd $alephe_scratch

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cat yoel

000063075USM01

000063076USM01

000063077USM01

000063078USM01

000063079USM01

000063080USM01

000063081USM01

000063082USM01

000063083USM01

000063084USM01

000063085USM01

000063086USM01

000063087USM01

000063088USM01



150

• Now we run the conversion:



151

• These are the HOL records for the BIB records of the input file:

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cd $alephe_scratch

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cat yoel_hol

000050107USM60

000050108USM60

000050109USM60

000050110USM60

000050111USM60

000050112USM60

000050113USM60

000050114USM60

000050115USM60

000050116USM60

000050117USM60

000050118USM60

000050119USM60

000050120USM60



152

• The library can also use the barcode-to-bib option to take an input file of barcodes to retrieve bibliographic data.

• We have this input file of barcodes:

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cat $alephe_scratch/barcodes

63075-10

63076-10

63077-10

63078-10

63079-10

63080-10

63081-10

63082-10

63083-10

63084-10

63085-10

63086-10

63087-10

63088-10

63088-20



153

• We convert the barcodes file to bibliographic system numbers so that it can be used to make a bibliographic report



154

• We get an output file of bibliographic records

il-aleph07.corp.exlibrisgroup.com-20(1) USM01-YOELK>>cat $alephe_scratch/yoel_bib

000063075USM01

000063076USM01

000063077USM01

000063078USM01

000063079USM01

000063080USM01

000063081USM01

000063082USM01

000063083USM01

000063084USM01

000063085USM01

000063086USM01

000063087USM01

000063088USM01

This file can then be used for making a bibliographic report



155

• We make a bibliographic report

Output file of manage-70



156

• This report began as a file of barcodes



157

• A2006 • Enhancements to email

capabilities

Email authentication options


158

• To comply with e-mail authentication standard • Universities are getting more restrictive in the use

of unauthenticated SMTP. • To combat viruses that infect computers via e-

mails, systems across the world are rapidly moving towards setting up their mail servers to only accept authenticated messages from clients.



159

• Via the ALEPHADM module it is possible to configure SMTP type email protocol usernames and passwords.

• In this way the email may be sent in coordination with the institutions SMTP (Simple Mail Transfer Protocol) mail server



160

• After choosing the “Email settings” menu option the staff user is prompted to enter the following information.



161

• After filling in the “E-Mail settings and options” dialog box the following two files are updated on the PC”


..\AL500\Alephcom\Tab\EMailPwd.dat

..\AL500\Alephcom\Tab\Alephcom.ini


162

• The Alephcom.ini file includes a parameter AuthMethod which corresponds to whatever is entered in the Authentication Type in the “E-Mail settings and options” dialog box


[Mail]MailServer=IL-EX01FromAddress=Circulation@ylk_library.eduMailerName=YLK Library Library Circulation DeptCharset=windows-1252CharsetBody=UTF-8AuthMethod=LOGIN


163

• The EMailPwd.dat file includes the username and password which are entered in the the “E-Mail settings and options” dialog box

• The information is encrypted



164

• If the username and password do not match the SMTP server then the following error message will appear:



165

Rush Cataloging Request• Cataloging A2022 7 • Rush cataloging request


166

Rush Cataloging Request• A new Hold Type will be defined in tab15 and will

serve as an indicator for the system to follow a hold request creation.

• This special hold request will be created with the creation of a trigger in the BIB library.

• The trigger will serve as an indicator that the requested item requires additional cataloging work before being processed.


167

Rush Cataloging Request• The hold requests will be handled by standard

Circulation procedures such as the “Request Handling (ue_06) ” daemon and the “Call Slips for Requests (cir-12)” service.

• The BIB library triggers will be handled using standard trigger management tools such as the GUI interface and the Print Trigger Report (com-01) batch service.


168

Rush Cataloging Request

• The library catalog many times includes items which have arrived at the library but are not available for circulation due to pending cataloging procedures that still have to take place.

• The library many times cannot provide speedy cataloging, causing library items to be unavailable for circulation for a long time.

• Rush Cataloging is a service that enables patrons to speed up the item cataloging process, helping the catalogers prioritize required items for a quicker cataloging process.

• The requested items will have high priority in the library’s cataloging department.

Why is the development needed?


169

Rush Cataloging Request! COL 8. 1; ALPHA {Y,N,C,T}, UPPER; ;

! Hold request;

! N - item cannot be requested

! Y - item can be requested. In addition, item availability

! is checked when a hold request is placed.

! If a copy is available, and the patron does not have permission

! for requesting an available item, a message displays.

! C - Item can be always be requested, there is no availability

! check because hold requests are always allowed (e.g. closed

! stack)

! T - item availability is not checked when hold request is placed,

! because hold requests are always allowed (e.g. short-term loan,

! lost, on order, etc.). However, for p_cir_12 (print request

! slips) and ue_06 (online printing of request slips),

! item is not considered "requestable" and does not print

! R - Rush Cataloging item. When a privileged patron requests

! the item, a cataloging trigger will be created, prompting

! the Cataloging Department to prioritize the cataloging process.

! Item availability issues are managed just like T, except that if

! there are available like items that are not "R" the request will

! be blocked;

New option in col. 8 of tab15.lng


170


! COL 23. 1; ALPHA {Y,N}, UPPER; ;

! Rush Cataloging permission;

! Rush Cataloging permission

! A patron that has Y in this permission will be allowed

! to create a cataloging trigger along with the hold request

! (if the item is defined as a Rush Cataloging item

! in tab15);

New col. 23 in tab31


171

Rush Cataloging Request• Here patron Jimmy Librarystein has the permission


172

Rush Cataloging Request• Here we state that any item with process status CT

can receive Rush request.• Normally a process status CT would not be loanable

or requestable.

! 1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1

! 0 1 2 3 4 5 6 7

!!!!!-!!-!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!-!-!-!-!-!-!-!-!-!!-!-!

15H ## CT L Cataloging N Y R N Y Y N N N 00 Y A

Can not be loaned Can be rush requested


173

Rush Cataloging Request• Barcode 63091-10 is rush requestable but not

loanable


174

Rush Cataloging Request• Util E 6 “Request Handling” is running

*** util_c_01 - check USM50 batch queue ***

21183 ? S 0:02 /exlibris/aleph/a20_1/aleph/exe/lib_batch USM50

31849 pts/2 S 0:00 /exlibris/aleph/a20_1/aleph/exe/rts32 ue_06_a USM50.a20_1

Enter to continue


175

Rush Cataloging Request• Patron Jimmy Librarystein logs into web OPAC and

searches for “Libraries of London”

He now views the items


176

Rush Cataloging Request• The item is non-circulating but can be requested


177

Rush Cataloging Request• Jimmy Librarystein makes the request

Rush handling


178

Rush Cataloging Request• Request is confirmed


179

Rush Cataloging Request• The request appears as a Rush request in “My

Library Card”


180

Rush Cataloging Request• The request appears as a Rush request in the GUI

Ue_06 printed the letter


181

Rush Cataloging Request• Util E 06 printed the letter


182

Rush Cataloging Request• The trigger appears in the cataloging module


183

Rush Cataloging Request• The library may periodically print the trigger report


184



185

Rush Cataloging Request• In the previous slide we were able to retrieve by

department “Rush Request” because of this line in usm01/tab/pc_tab_exp_field.eng

! 1 2 3 4

!!!!!!!!!!!!!!!!!!!!-----!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>

TRIGGER-DEPARTMENT L Rush Request RUSH


186


• The catalogers can retrieve a report like this regularly, finish cataloging the item, remove the CT process status, and loan the item to the requester.

• The rest of the behavior will be like standard request and loan.


187

X-Service for Items

• A2042• TOP - X-Service for Items


188

X-Service for Items - Introduction• Four new X services have been created:1. create-item2. read-item3. update-item4. delete-item

• Here we will show all four X services by creating an item, updating it, reading it, and deleting it

• We will thus use all four X services


189

X-Service for Items - create-item

Details regarding this X service can be seen on the open platform at:http://www.exlibrisgroup.org/display/Aleph/create_item


190

X-Service for Items - create-item • We will now look at a sample input file and

sample perl program which runs the X service “create-item”

• We will then use both to create an item with the X service.

• The input file should be in xml format in the $data_scratch directory of the ADM library.

• The perl program may be wherever you want (as long as you call it from its correct location)


191


il-aleph07.corp.exlibrisgroup.com-a20(1) >>cat $usm50_dev/usm50/scratch/yoel_new_item_works.xml

<?xml version="1.0" encoding="UTF-8" ?>

<z30>

<z30-doc-number>000238781</z30-doc-number>

<z30-item-sequence>000000</z30-item-sequence>

<z30-barcode>238781-20</z30-barcode>

<z30-sub-library>HIL</z30-sub-library>

<z30-material>BOOK</z30-material>

<z30-item-status>02</z30-item-status>

<z30-open-date>20081213</z30-open-date>

<z30-update-date>20081213</z30-update-date>

<z30-cataloger>YOEL</z30-cataloger>

<z30-date-last-return></z30-date-last-return>

<z30-hour-last-return></z30-hour-last-return>

<z30-ip-last-return></z30-ip-last-return>

<z30-no-loans>001</z30-no-loans>

<z30-alpha>L</z30-alpha>

<z30-collection>GEN</z30-collection>

<z30-call-no-type>0</z30-call-no-type>

This file is on the open platform previously referred to

Sample input file part 1


192


<z30-call-no>$$hHD87$$i.C37$$mv. 34-</z30-call-no>

<z30-call-no-key>0 hd87 c37 v 34</z30-call-no-key>

<z30-call-no-2-type />

<z30-call-no-2 />

<z30-call-no-2-key /> <z30-description>Vol. 01</z30-description>

<z30-note-opac />

<z30-note-circulation />

<z30-note-internal />

<z30-order-number />

<z30-inventory-number />

<z30-inventory-number-date>00000000</z30-inventory-number-date>

<z30-last-shelf-report-date>00000000</z30-last-shelf-report-date>

<z30-price />

<z30-shelf-report-number />

<z30-on-shelf-date>00000000</z30-on-shelf-date>

<z30-on-shelf-seq>000000</z30-on-shelf-seq>

<z30-doc-number-2>000000450</z30-doc-number-2>

<z30-schedule-sequence-2>00000</z30-schedule-sequence-2>



193


z30-copy-sequence-2>00000</z30-copy-sequence-2>

<z30-vendor-code />

<z30-invoice-number />

<z30-line-number>00000</z30-line-number>

<z30-pages />

<z30-issue-date>00000000</z30-issue-date>

<z30-expected-arrival-date>00000000</z30-expected-arrival-date>

<z30-arrival-date>00000000</z30-arrival-date>

<z30-item-statistic />

<z30-item-process-status /> <z30-item-process-status />

<z30-copy-id />

<z30-hol-doc-number></z30-hol-doc-number>

<z30-temp-location>N</z30-temp-location>

<z30-enumeration-a />

<z30-enumeration-b />

<z30-enumeration-c />

<z30-enumeration-d />

<z30-enumeration-e />



194


<z30-enumeration-f />

<z30-enumeration-g />

<z30-enumeration-h />

<z30-chronological-i />

<z30-chronological-j />

<z30-chronological-k />

<z30-chronological-l />

<z30-chronological-m />

<z30-supp-index-o />

<z30-85x-type />

<z30-depository-id />

<z30-linking-number>000000000</z30-linking-number>

<z30-gap-indicator />

<z30-maintenance-count>000</z30-maintenance-count>

</z30>



195


il-aleph07.corp.exlibrisgroup.com-a20(1) >>cat ~yoelk/scripts/x_services/create_new_item.pl

use strict;

require LWP::UserAgent;

$| = 1; # unbuffered output

my $ua = LWP::UserAgent->new;

$ua->timeout(30);

$ua->env_proxy;

my $data;

my $in_file = shift or die "input XML file needed\n";

open( IN_F, $in_file) or die "Cannot open file as input\n" ;

while (<IN_F>) { $data.=$_; }

my $url = 'http://localhost:'.$ENV{'HTTPD_PORT'}.'/X';

This script is on the open platform previously referred to

Sample perl program part 1


196


my %form;

$form{'xml_full_req'} = $data ;

$form{'op'} = 'create_item' ;

$form{'adm_library'} = 'usm50' ;

$form{'bib_library'} = '' ;

$form{'adm_doc_number'} = '000000015' ;

$form{'bib_doc_number'} = '' ;

print "Sending $url\n";

my $res = $ua->post("$url",\%form);

if ($res->is_success) {

print ($res->content);

printf "\n--------------------\nfetched %d bytes\n", length($res->content);

} else {

print "\nError: " . $res->code . " " . $res->message;

}



197

X-Service for Items - create-item• The previous perl program may be used to run the X

service using the previous input file as follows

Input file must be in $data_scratch of ADM library and user should dlib to the library

perl ~yoelk/scripts/x_services/create_new_item.pl yoel_new_item_works.xml


198

X-Service for Items - create-item• Here is an example of a successful run

il-aleph07.corp.exlibrisgroup.com-20(1) USM50-YOELK>>perl ~yoelk/scripts/x_services/create_new_item.pl yoel_new_item_works.xml

Sending http://localhost:8991/X

<?xml version = "1.0" encoding = "UTF-8"?>

<create-item>

<z30>

[The z30 xml appears here]

<error>Item has been created successfully.</error>

<session-id>956KQDF2G6IJ6SLAMXREAFRQ9269Q9TGBGSK2HX3CN7F4N3682</session-id>

</create-item>

--------------------

fetched 3126 bytes


199

X-Service for Items - create-item• Here is the item in the GUI and in input file

• Values from the input file are in the item


200

X-Service for Items - create-item• Here are some reasons why the item might not get created

<error>There is already an item matching given barcode. Cannot create item.</error>

<error>Sublibrary does not exist.</error>

<error>Invalid Item Status</error>


201

X-Service for Items - update-item• We will now begin to focus on X service “update-item”• Details regarding this X service can be seen on the open

platform at:• http://www.exlibrisgroup.org/display/Aleph/update_item


202

X-Service for Items - update-item• Like “ create-item”, update-item works with a z30

xml file in $data_scratch of the ADM library.• It may be activated via a perl script while being

dlibbed to the ADM library• The next slide shows an example of such a perl

script


203

X-Service for Items - update-item

il-aleph07.corp.exlibrisgroup.com-20(1) USM50-YOELK>>cat ~yoelk/scripts/x_services/update_item.pl

use strict;

require LWP::UserAgent;

$| = 1; # unbuffered output

my $ua = LWP::UserAgent->new;

$ua->timeout(30);

$ua->env_proxy;

my $data;

my $in_file = shift or die "input XML file needed\n";

open( IN_F, $in_file) or die "Cannot open file as input\n" ;

while (<IN_F>) { $data.=$_; }



204

X-Service for Items - update-item

my $url= 'http://localhost:'.$ENV{'HTTPD_PORT'}.'/X';

my %form;

$form{'xml_full_req'} = $data;

$form{'op'} = 'update_item' ;

$form{'library'} = 'usm50' ;

my $res = $ua->post("$url",\%form);

if ($res->is_success) {

print ($res->content);

printf "\n--------------------\nfetched %d bytes\n", length($res->content);

} else {

print "\nError: " . $res->code . " " . $res->message;

}



205

X-Service for Items - update-item• The input file is a regular z30 xml like the input file

for “create-item”• Here is part of an example:il-aleph07.corp.exlibrisgroup.com-20(1) USM50-YOELK>>cat yoel_update_item_works.xml

<?xml version="1.0" encoding="UTF-8" ?>

<z30>

<z30-doc-number>000000015</z30-doc-number>

<z30-item-sequence>000080</z30-item-sequence>

<z30-barcode>238781-40</z30-barcode>

<z30-cataloger>YOEL</z30-cataloger>

<z30-collection>LIBNO</z30-collection>

The collection is different than the actual data and will thus get updated


206

X-Service for Items - update-item• The file on the previous page will update this item because it

has z30-doc-number 000000015, z30-item-sequence 000080 and z30-barcode 238781-40.

• The collection will be changed from GEN (General) to LIBNO (Librarian’s Office)


207

X-Service for Items - update-item• Now we update the item:

perl ~yoelk/scripts/x_services/update_item.pl yoel_update_item_works.xml

<error>Item has been updated successfully</error>

• And we receive this message:


208

X-Service for Items - update-item• The collection has been changed from GEN

(General) to LIBNO (Librarian’s Office)


209

X-Service for Items - read-item• We will now begin to focus on X service “read-item”• Details regarding this X service can be seen on the open

platform at:• http://www.exlibrisgroup.org/display/Aleph/read_item


210

X-Service for Items - read-item• The read-item does not use an input file and may

be done via a URL• The URL may work according to either of the

following two options:1. doc_number and item_sequence 2. item_barcode.• We will now show two URLs which will retrieve ADM

doc number 000000015, sequence number 000080, barcode 238781-40 (the item we update previously)


211

X-Service for Items - read-itemhttp://il-aleph07:8991/X?op=read-item&library=usm50&doc_number=000000015&item_sequence=000080

http://il-aleph07:8991/X?op=read-item&library=usm50&item_barcode=238781-40

ADM doc number 000000015, sequence number 000080

barcode 238781-40


212

X-Service for Items - read-item• Here is the Z30 when using the ADM doc number 000000015 and sequence

number 000080


213

X-Service for Items - read-item• Here is the Z30 when using the barcode 238781-40


214

X-Service for Items - delete-item• We will now run the X service “delete-item” on ADM doc

number 000000015 and sequence number 000080 (barcode 238781-40).

• We will also run it on barcode 238781-30• Barcode 238781-40 is the item we have created and updated

via the services “create-item” and “update-item”.• Details regarding this X service can be seen on the open

platform at:• http://www.exlibrisgroup.org/display/Aleph/delete_item


215

X-Service for Items - delete-item• Here is the item list for ADM doc number

000000015 before the deletion

We will delete these twoLink back to table of contents

216

X-Service for Items - delete-item• The delete-item does not use an input file and may

be done via a URL (like the read-item)• The URL may work according to either of the

following two options (like the read-item):• doc_number and item_sequence • item_barcode.• We will now show two URLs which will delete ADM

doc number 000000015, sequence number 000080, barcode 238781-40 (the item we update previously)


217

X-Service for Items - delete-itemhttp://il-aleph07:8991/X?op=delete-item&library=usm50&doc_number=000000015&item_sequence=000080

http://il-aleph07:8991/X?op=delete-item&library=usm50&item_barcode=238781-40

ADM doc number 000000015, sequence number 000080

barcode 238781-40


218

X-Service for Items - delete-item• Here is the URL and results for deleting an item

using ADM doc number and sequence number


219

X-Service for Items - delete-item• Here is the end of the resulting XML when deleting

an item successfully


220

X-Service for Items - delete-item• Here is the resulting XML when trying to delete an

item which does not exist


221

X-Service for Items - delete-item• Here we delete an item via the barcode, in this

case barcode 238781-30


222

X-Service for Items - delete-item• Both of the items we deleted are now gone

Before

After


223

• The ret-06 service retrieves records based on an input file of direct index values. For example, the input file may be a list of ISBN or ISSN numbers.

• The input file includes the list of direct index values.

• The input file must be found in the $alephe_scratch directory.

Retrieve records by direct index service


224

• The output file will include the record numbers of the matching bibliographic records.

• The output file can be found in the $alephe_scratch directory.

• Input direct index values for which no matching record was found will be reported in a rejects file, for example sample_output_rejected.



225

• Here we have an input file of isbn numbersyoelk@il-aleph07(a20_1) USM01> cat $alephe_scratch/isbnnumbers08240887940226096149022609615778514376130824088646071020503109318282950931828139093182805891734615986139424969270781081904718765260471876534201010956227078107972234017513031324281X27158058029061962846

Two of these numbers are ISBN numbers which are not in the library database



226

• ISBN is defined as a direct index

yoelk@il-aleph07(a20_1) USM01> dtyoelk@il-aleph07(a20_1) USM01> grep ISBN tab01.eng D 020 00 0000 020 LISBNyoelk@il-aleph07(a20_1) USM01> grep ISBN tab11_ind020 ISBN a yoelk@il-aleph07(a20_1) USM01>



227

• Ret-06 is run using the input file of ISBN numbers in $alephe_scratch and the ISBN index

• Output file is called ret_06_yoel



228

• In $alephe_scratch we have:• Output file ret_06_yoel with bibliographic

system numbers of the records which have ISBN index from the index file

• Output file ret_06_yoel_rejected for which no matching record was found



229

yoelk@il-aleph07(a20_1) USM01> cd $alephe_scratchyoelk@il-aleph07(a20_1) USM01> cat ret_06_yoel_rejected78514376136139424969

yoelk@il-aleph07(a20_1) USM01> cat ret_06_yoel000006542USM01000006544USM01000006544USM01000006546USM01000006559USM01000006563USM01000006564USM01000006565USM01000006572USM01000006616USM01000006641USM01000006641USM01000006643USM01000006674USM01000006675USM01000006693USM01000006696USM01000006704USM01yoelk@il-aleph07(a20_1) USM01>

ISBNs which were in input file but not in database

ISBNs which were in input and in database. This file can now be used to print a report



Thank [email protected]

introducing aleph version 20.0 ex libris technical seminar march 10, tel aviv 14:00 to 15:30 yoel...

Documents