Presenter: Yoel Kortick There but not there: expand procedures in ALEPH 500 MELI Conference 2007 Presenter: Yoel Kortick

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 500, SFX, SFXIT, MetaLib, DigiTool, Verde, Primo, Voyager, Journals Onsite, 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 (the "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., 2007

Note Records appearing in this presentation from Library of Congress or other libraries may have been slightly altered for the purposes of this presentation and should not be considered as “official” records as they appear in the original library. Records appearing in this presentation do not necessarily conform to the strictest of MARC standards and should not be considered as such.

Why are there expand procedures? Libraries may want to display information from the non-bibliographic databases together with the linked bibliographic record. Libraries may want to reconstruct bibliographic data into new fields in the bibliographic record for display purposes. Both of the above may also be done for indexing purposes.

How does the expand work? ALEPH enables the installation to "expand" information from one database (library) record to another one record and back to the same record within the same database (library). This is possible because there are links between the records in the various databases.

How does the expand work? The "expand" function works with the tab_expand table located in the library's tab directory. Every library has such a table, although it is the bibliographic library that uses the table the most. The tab_expand table defines three aspects: The system function in which the expand program works. The expand program that defines which data from the record can be expanded. Additional parameters for the expand program, if required.

How does the expand work? The tab_expand table uses a combination of expand menus and expand procedures to accomplished the desired expand routine. For a full description of all menus and procedures see the indexing chapter of the System Librarian Guide “Expand routines” section In this presentation we will show the use and “effects” of selected menus and procedures.

From where is data expanded? As explained in the next slide, fields may be expanded into the bibliographic record from: The bibliographic record and back into the bibliographic record in a different format expand_doc_fix_abbreviation expand_doc_bib_type The AUT record expand_doc_bib_acc_ref The ADAM digital object expand_doc_bib_z403 The HOL record expand_doc_bib_loc_usm The item record

From where is data expanded? BIB Record Expand procedure AUT Record Expand procedure HOL Record ADAM Digital Object Items

For example (one of six) From bibliographic record back to bibliographic record MARC fields BIB Record Expand procedure expand_doc_fix_abbreviation Abbreviated text fields

For example (two of six) From bibliographic record back to bibliographic record MARC fields BIB Record Expand procedure expand_doc_type Type of record fields

For example (three of six) BIB Record From AUT record to bibliographic record Words from non preferred terms Expand procedure expand_doc_bib_acc_ref AUT Record

For example (four of six) From ADAM digital object to bibliographic record Digital object BIB Record Expand procedure expand_doc_bib_z403 Digital object title

For example (five of six) BIB Record From items to bibliographic record SBL $$a (sub library) PST $$d (status) PST $$c (collection) PST $$o (material type) Expand procedure expand_doc_bib_loc_usm Item A Sublibrary DOWNT Item status 01 Material Type CD ROM Item B Sublibrary MAIN Item status 01 Material Type FILM Item B Sublibrary MAIN Item status 01 Material Type FILM

For example (six of six) BIB Record From HOL record to bibliographic record LOC $$b (sub library) LOC $$c(collection) LOC $$h (call number) LOC $$o (material type) Expand procedure expand_doc_bib_loc_usm HOL Record 852 field

Table of contents expand_doc_fix_abbreviation expand_doc_type Each of the subjects below is a hyperlink which may be clicked in order to arrive to an explanation of the specific procedure The “Expand Procedures” link at the bottom of each slide will return to this page expand_doc_fix_abbreviation expand_doc_type expand_doc_bib_acc_ref expand_doc_bib_z403 expand_doc_bib_loc_usm

expand_doc_fix_abbreviation

expand_doc_fix_abbreviation The expand_doc_fix_abbreviation program is used to change abbreviations into full text. The routine can be used to replace any text string in a record with a different text string. There are two options: A new duplicate field is added to the record with the non-abbreviated form of the text. The abbreviated form of the text is changed into full text in the original field.

expand_doc_fix_abbreviation First we will define as follows in tab_abbrev Original text Additional new text ! 1 2 3 4 !!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2#### Y 1st first 2#### Y 2nd second 2#### Y 3rd third 2#### Y 4th fourth 2#### Y 5th fifth 2#### Y Center Centre 2#### Y center centre Note that this is case sensitive

expand_doc_fix_abbreviation Then we will define as follows in tab_expand ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> ABBR expand_doc_fix_abbreviation ADD WORD expand_doc_fix_abbreviation ADD Expand menu ABBR has been created so we can see what the procedure does using UTIL F 4 doc_expand Expand menu WORD has been used so we can have the new words indexed.

expand_doc_fix_abbreviation We have this record, system number 50786:

expand_doc_fix_abbreviation Two words will be added to the record, one for “1st” and one for “center” ! 1 2 3 4 !!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2#### Y 1st first 2#### Y 2nd second 2#### Y 3rd third 2#### Y 4th fourth 2#### Y 5th fifth 2#### Y Center Centre 2#### Y center centre USA spelling to UK spelling

expand_doc_fix_abbreviation enter file name (or q to exit) doc_expand Enter expand_menu [No Expand]: ABBR Load: /exlibris/aleph/a18_1/alephe/unicode/unicode_case ENTER DOC NUMBER : 50786 -------------------------------------------------------------- Load: /exlibris/aleph/a18_1/alephe/tab/tab100 Load: /exlibris/aleph/a18_1/usm01/tab/tab100 Reading doc : 000050786 Load: /tmp/utf_files/exlibris/aleph/a18_1/usm01/tab/tab_expand Load: /tmp/utf_files/exlibris/aleph/a18_1/usm01/tab/tab_abbrev FMT L BK LDR L 00000nam^a22^^^^^^u^4500 005 L 20070404163213.0 008 L 070404s2004^^^^cau^^^^^r^^^^^000^0^eng^d 1001 L $$aKortick, Yoel 24514 L $$aThe 1st new center in Europe. OWN L $$aPUBLIC 24514 L $$aThe first new centre in Europe. Original field Added field In the Added field 1st became first and center became centre

expand_doc_fix_abbreviation We also have the expand_doc_fix_abbreviation in tab_expand WORD expand menu ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> ABBR expand_doc_fix_abbreviation ADD WORD expand_doc_fix_abbreviation ADD In this way the words of the new field will be indexed

expand_doc_fix_abbreviation We search for the words “first” and “centre”, neither of which are in the actual data:

expand_doc_fix_abbreviation And we find the record which has “1st” and “center”, neither of which are in the actual data: “first” and “centre”, are there (in the indexed words) but not there (in the actual data). Data has “1st” and “center”

expand_doc_type expand_doc_type

expand_doc_type This Expand procedure can be used to create a new field according to the specifications defined in a configuration table. The name of the configuration table is also a parameter that must be defined in the parameters column of the tab_expand table. In default setup this table is called tab_type_config.eng.

expand_doc_type This Expand procedure, together with the corresponding configuration table, can be used to create a new field TYP which states the “type” or “format” of record. The new field is based on the contents of specific positions of field(s) present in the record (for example, a combination of the LDR and the 008 field) Specific words which might be present in specific fields Whether or not specific fields exist

Expand procedure expand_doc_type BIB Record Data leaves the bibliographic record, undergoes the expand procedure, and then returns to the bibliographic record. Expand procedure expand_doc_type

expand_doc_type Virtual field “TYP” In this example we will show how the virtual fields TYP are created How the virtual fields may be used for indexing purposes

expand_doc_type In the table tab_type_config.eng the system librarian may define whether a field, or position of a field, matches (or does not match) a certain value. For a full description of the table see the table header and the systems librarian guide, chapter on indexing, section “Expand-related tables” Here we will show several examples and discuss column 6

expand_doc_type Column 6 the table tab_type_config.eng is used to define the match criteria in relation to the contents of the subfield or the fixed field positions defined in column 5. The following are the available options: EQUAL and N-EQUAL EXIST and N-EXIST MATCH and N-MATCH

expand_doc_type Usage of column 6 parameters: EQUAL (N-EQUAL) - checks for direct match EXIST (N-EXIST) - checks if the field exists without checking the field contents. For example, if a record has a 027 MARC 21 field, then the record is a technical report (contents are irrelevant). MATCH (N-MATCH) - checks for a match that is not case-sensitive. Use [] to enclose multiple values to match on.

expand_doc_type Here we have “expand_doc_type” in tab_expand with three different Expand Menus TYPE (home made so we can see the procedure via UTIL F 4 doc_expand) WORD (for word building procedures) WEB-FULL (for web OPAC full view) TYPE expand_doc_type tab_type_config WORD expand_doc_type tab_type_config WEB-FULL expand_doc_type tab_type_config We add TYP to tab11_word and send it to WRD index TYP a 03 WRD

expand_doc_type In our examples we will create an expanded field TYP which will be visible in full view of web OPAC because we have this line in edit_doc_999.eng: ! 1 1 1 !1 2 3 4 5 6 7 8 9 0 11 2 13 4 15 16 !!-!!!!!-!-!!!!!!!!!!-!-!-!!!!!!!!!!!!!!!!!!!!-!-!-!!!-!-!!!!!-!-!!-!! ## TYP## D LRecord Format Y E

expand_doc_type We will now create a virtual field TYP based on pos. 6 of the LDR field. Position 6 of the LDR field describes the type of record. A full description of position 6 of the LDR field may be found at http://www.loc.gov/marc/bibliographic and click on "Leader"

expand_doc_type Partial list from http://www.loc.gov/marc/bibliographic/ecbdldrd.html

expand_doc_type Based on the meaning of pos 6 of the LDR field we will now set up the table tab_type_config.lng to create corresponding TYP fields. In this case we will use the EQUAL parameter in column 6 We will say “If position 6 of LDR field is EQUAL to value in position 7 then create TYP field with text of position 3.

expand_doc_type tab_type_config.eng In the highlighted line we say “If pos. 6 of LDR is e then make TYP field with text Cartographic Material” ! 1 2 3 4 5 6 7 !!!!!-!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!! TYP Notated music LDR F06-01 EQUAL c TYP Manuscript notated music LDR F06-01 EQUAL d TYP Cartographic material LDR F06-01 EQUAL e TYP Manuscript cartographic materi LDR F06-01 EQUAL f TYP Projected medium LDR F06-01 EQUAL g TYP Nonmusical sound recording LDR F06-01 EQUAL i TYP Musical sound recording LDR F06-01 EQUAL j TYP Two-dimensional graphic LDR F06-01 EQUAL k TYP Computer file LDR F06-01 EQUAL m TYP Kit LDR F06-01 EQUAL o TYP Mixed material LDR F06-01 EQUAL p TYP Three-dimensional artifact LDR F06-01 EQUAL r

expand_doc_type We have this record Pos. 06 of LDR field is e

expand_doc_type If we view this record via UTIL F 4 doc_expand using TYPE (the expand menu we created for this purpose) then we will see a new field TYP The new field TYP Is not part of the actual data in the record (Z00 Oracle table) Is created via the expand procedure Is based on the contents of pos. 06 of the LDR field

expand_doc_type FMT L MP LDR L 00000nem^^2200385^^^4500 001 L EXL01-000048933 005 L 20070508072215.0 007 L ad^canzn 008 L 870224s1987^^^^vtu^^^^^^^e^^^^^^^^^eng^^ 010 L $$a87050303 020 L $$a096067389X (pbk.) :$$c$11.95 05000 L $$aG1226.E63$$bN6 1987 08200 L $$a912/.17991755$$219 1102 L $$aNorthern Cartographic, Inc. 24514 L $$aThe atlas of Vermont trout ponds. 250 L $$a2nd ed. 255 L $$aScales differ. 260 L $$aBurlington, Vt. :$$bNorthern Cartographic,$$cc1987. 300 L $$a1 atlas (174 p.) :$$bill., maps (some col.) ;$$c22 cm. 500 L $$a"Illustrated by Dick Leyden"--Cover. 504 L $$aBibliography: p. 168-169. 500 L $$aIncludes index. 650 0 L $$aTrout fishing$$zVermont$$xMaps. 650 0 L $$aFishing$$xAccess roads$$zVermont$$xMaps. 650 0 L $$aLakes$$zVermont$$xMaps. 650 0 L $$aPonds$$zVermont$$xMaps. OWN L $$aEXLYOEL SID L $$aZ39$$bLOC TYP L $$aCartographic material

expand_doc_type We sent TYP top WRD index via tab11_word so now we can search for the record via the WORD index

expand_doc_type We find the record even though no where in the record (Z00) does the string “catrographic material” appear. This string appears only in the expanded virtual field The TYP field appears in the full view because we added it to edit_doc_999.lng

expand_doc_type We will now do an example of tab_type_config.lng configuration using the EXIST parameter ! 1 2 3 4 5 6 7 !!!!!-!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!! TYP Dissertation 502## EXIST TYP Electronic Resource 856## EXIST This means: If field 502 exists in record then create TYP field with text Dissertation If field 856 exists in record then create TYP field with text Electronic Resource

expand_doc_type We have this record Has 502 field

expand_doc_type Via UTIL F 4 doc_expand on procedure TYPE we see the new field: FMT L BK LDR L 00000nam^^2200289^a^4500 001 L EXL01-000048934 005 L 20070508081012.0 008 L 070508s1984^^^^^^^^^^^^r^^^^^000^0^eng^d 020 L $$a0262181150 041 L $$aENG 090 L $$a005.13 REP 1001 L $$aReps, Thomas W.$$q(Thomas William) 24510 L $$aGenerating language-based environments /$$cThomas W. Reps. 260 L $$aCambridge, MA :$$bMIT Press,$$cc1984. 300 L $$a138 p. :$$bill. 440 0 L $$aACM doctoral dissertation award ;$$v1983 502 L $$a"Thesis (Ph.D.)--Cornell University, 1983"--t.p. verso (CIP) 61020 L $$aCornell University$$xDissertations (Ph.D.) 650 0 L $$aProgramming languages (Electronic computers) 650 0 L $$aText editors (Computer programs) OWN L $$aEXLYOEL SID L $$aZ39$$bULI TYP L $$aDissertation

expand_doc_type If we search for the word Dissertation… We find the record…

expand_doc_type The TYP field appears in the full view because we added it to edit_doc_999.lng

expand_doc_type We have this record Has 856 field

expand_doc_type In this case two TYP fields are created FMT L CF LDR L 00000nmm^a2200361^a^4500 001 L EXL01-000048935 005 L 20070508082519.0 008 L 060309m20069999cau^^^^^^^^m^^^^^^^^eng^d 0410 L $$aeng 24500 L $$aNARA on Google video. 2463 L $$aNational Archives and Records Administration on Google video 2463 L $$aNational Archives video sections 2463 L $$aNASA History of space flight motion pictures 260 L $$aMountain View, Calif. :$$bGoogle,$$c2006-. 500 L $$aTitle from title screen (viewed on March 29, 2006). 538 L $$aMode of access World Wide Web. 538 L $$aSystem requirememts: Real audio and Video programs. 650 0 L $$aDocumentary films$$vComputer network resources 650 0 L $$aSpace flight$$xHistory$$xSources$$vComputer network resources 7101 L $$aUnited States.$$bNational Aeronautics and Space Administration 7101 L $$aUnited States.$$bDept. of the Interior 85645 L $$uhttp://video.google.com/nara.html$$zClick here to view SID L $$aZ39$$bULI TYP L $$aComputer file TYP L $$aElectronic Resource In this case two TYP fields are created TYP Computer file LDR F06-01 EQUAL m TYP Electronic Resource 856## EXIST

expand_doc_type If we search for the words Electronic Resource We find the record…

expand_doc_type The words we searched for appear only in the expanded field

expand_doc_type We will now do an example of tab_type_config.lng configuration using the MATCH parameter ! 1 2 3 4 5 6 7 !!!!!-!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!! TYP Thesis 500## a MATCH *thesis* TYP Thesis 500## a MATCH *theses* This means: If field 500 exists in record and has either thesis or theses in sub field a then create TYP field with text Thesis

Has thesis in sub field a of 500 field expand_doc_type We have this record Has thesis in sub field a of 500 field

expand_doc_type Via UTIL F 4 doc_expand on procedure TYPE we see the new field: FMT L BK LDR L 00000cam^^22002411^^4500 001 L EXL01-000048941 005 L 20070508095545.0 008 L 050407s1969^^^^enka^^^^^b^^^^000^0^eng^^ 010 L $$a76437254 040 L $$aDLC$$cDLC$$dDLC 05000 L $$aPR2110$$b.A1 1969 1300 L $$aPatience (Middle English poem) 24510 L $$aPatience; /$$cedited by J. J. Anderson. 260 L $$aManchester,$$aNew York, :$$bManchester U. P.;$$bBarnes and Noble,$$c1969. 300 L $$aviii, 112 p. :$$billus. ;$$c18 cm. 440 0 L $$aOld and Middle English texts 500 L $$aBased on thesis, Univ. of Adelaide. 500 L $$aEnglish and Middle English. 504 L $$aBibliography: p. 24-29. 7001 L $$aAnderson, J. J.,$$eed. SID L $$aZ39$$bLOC TYP L $$aThesis

expand_doc_type Here is the record in full view

Has theses in sub field a of 500 field expand_doc_type We have this record Has theses in sub field a of 500 field

expand_doc_type Via UTIL F 4 doc_expand on procedure TYPE we see the new field: FMT L BK LDR L 00000cam^^22002774a^4500 001 L EXL01-000048942 005 L 20070508110443.0 008 L 040705s2004^^^^it^^^^^^^b^^^^000^0^ita^d 010 L $$a2005455520 020 L $$a8888684662 24500 L $$aAdolescenti e donne nell'immigrazione :$$bproblematiche e conflitti : premio Luciana Sassatelli per tesi di laurea sull'immigrazione straniera in Italia, edizione 2002- 2003 /$$ca cura di Osservatorio provinciale delle immigrazioni. 260 L $$aTorino :$$bL'Harmattan Italia,$$c2004. 300 L $$a156 p. ;$$c21 cm. 440 0 L $$aMetissage ;$$v39 500 L $$a3 theses on immigration, winners of the Luciana Sassatelli prize, 2002-2003. 500 L $$aContains bibliography and notes. 500 L $$aNumber of series appears on spine. L $$aIncludes bibliographical references. SID L $$aZ39$$bLOC TYP L $$aThesis

Virtual word (not in actual document) expand_doc_type Now we search for the record: Actual word from title Virtual word (not in actual document)

expand_doc_type The record is found even though no where in the record does the word “Thesis” appear.

expand_doc_type There but not there The words from the TYP field are there (indexed with the bibliographic record and appearing in full view) but not there (in the actual bibliographic record data Z00)

expand_doc_bib_acc_ref

expand_doc_bib_acc_ref In this example we will show the use of the menu WORD and the procedure expand_doc_bib_acc_ref in $data_tab/tab_expand of the bibliographic library. ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> WORD expand_doc_bib_accref Expand Menu Expand Procedure

expand_doc_bib_acc_ref expand_doc_bib_acc_ref is an expand procedure which “expands” the related authority heading into the bibliographic heading WORD menu is used when words are created in the index Thus for example the words of a non preferred term may be indexed with a record which contains the preferred term

expand_doc_bib_acc_ref BIB Record Expand procedure expand_doc_bib_acc_ref with menu WORD AUT Record

expand_doc_bib_acc_ref If we search database USM01 for the word “grilling” …

expand_doc_bib_acc_ref We find system number 50752 even though the word “grilling” does not appear in the record:

expand_doc_bib_acc_ref If we search database USM01 for word from author “kimbell” …

expand_doc_bib_acc_ref We find system number 50752 even though the word “kimbell” does not appear in the record:

expand_doc_bib_acc_ref “Kimbell” and “grilling” are not words in record with system number 50752 even though we found this record when searching for these words.

expand_doc_bib_acc_ref System number 50752 contains library of congress subject heading “Barbecue cookery” Added entry surname “Griffiths, Joan”

expand_doc_bib_acc_ref Both headings have related authority records

expand_doc_bib_acc_ref library of congress author heading “Griffiths, Joan” is linked to authority record with word “Kimbell” 50008 in USM10 50752 in USM01

expand_doc_bib_acc_ref library of congress subject heading “Barbecue cookery” is linked to authority record with word “grilling” 50009 in USM10 50752 in USM01

expand_doc_bib_acc_ref 50008 in USM10 50009 in USM10 We searched for “Kimbell” and “Grilling”

expand_doc_bib_acc_ref We have this line tab_expand: ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> WORD expand_doc_bib_accref Word indexes are thus built for each record not only from the words in the actual bibliographic record (Z00) but also from fields of non preferred terms of headings related to the record. “Grilling” and “Kimbell” appear as words in non preferred terms of headings which are in system number 50752, and as a result a search on these words found record 50752.

expand_doc_bib_acc_ref There but not there The words from the non preferred term are there (indexed with the bibliographic record) but not there (in the actual bibliographic record)

expand_doc_bib_z403 expand_doc_bib_z403

expand_doc_bib_z403 The expand_doc_bib_z403 program is functional with ADAM. It can be used to expand the object's data information into the bibliographic record. The expand_doc_bib_z403 program is used with the expand_doc_bib_z403 table of the library's tab directory. The expand program creates a new virtual field, Z403, that contains the object's information. The table also determines the subfield structure of the new expanded field.

Expand procedure expand_doc_bib_z403 BIB Record Expand procedure expand_doc_bib_z403 ADAM digital object

expand_doc_bib_z403 Here is an example of the expand_doc_bib_z403 table in the bibliographic library's tab directory. ! 2 3 4 5 !-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!-! # z403-title y space X # z403-sub-library l space Y # Z403-usage-type t space N Now we will see how it works, with examples

expand_doc_bib_z403 Bibliographic record system number 50765 has title “Classic TV pictures”. It has object which is type view with object title “Full Cast of Gilligan's Island with autographs“

expand_doc_bib_z403 Bibliographic record system number 50774 has title “And then they were stranded”. It has object which is type view with object title “First season opening show title“.

expand_doc_bib_z403 Bibliographic record system number 50776 has title “That's the day we became the Brady Bunch.”. It has object which is type view with object title “Bobby Brady in 1969 series“.

expand_doc_bib_z403 Bibliographic record system number 50777 has title “Sam the butcher”. It has object which is type view with object title “Brady family portrait 1970“.

expand_doc_bib_z403 System number 50765 in web

expand_doc_bib_z403 System number 50774 in web

expand_doc_bib_z403 System number 50776 in web

expand_doc_bib_z403 System number 50777 in web

expand_doc_bib_z403 Now using expand_doc_bib_z403 we will build a new access for end users to browse in the web. This new access will be the title of the diogital object The bibliographic record does not contain the title of the digital object, thus it must be expanded from the digital object to the bibliographic record Let’s first see what the expand_doc_bib_z403 does by making a new expand menu which will include only expand_doc_bib_z403. This way we will be able to view our records via UTIL F 4 doc_expand to see what happens.

expand_doc_bib_z403 Here we have a made a new expand menu in tab_expand table called ADAM which does only expand_doc_bib_z403 ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> ADAM expand_doc_bib_z403

expand_doc_bib_z403 Here is system number 50765 viewed using expand menu ADAM Bibliographic record title Expanded Object title

expand_doc_bib_z403 The virtual field Z403 is made according to the expand_doc_bib_z403 table in the bibliographic library's tab directory. ! 2 3 4 5 !-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!-! # z403-title y space X # z403-sub-library l space Y # Z403-usage-type t space N

expand_doc_bib_z403 The object title “Full Cast of Gilligan's Island with autographs” is not part of the bibliographic record: The object title “Full Cast of Gilligan's Island with autographs” appears with the bibliographic record when expand procedure expand_doc_bib_z403 is used.

expand_doc_bib_z403 We will now make this object title “browsable” for end users The expand menu ACC is used for creating headings when manage_02 (create headings Service) is run or when a record is updated in the GUI. Thus, we will now put expand_doc_bib_z403 together with ACC: ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> ACC expand_doc_bib_z403

expand_doc_bib_z403 Now we will define an access in tab00.eng for the Object Title: ! 2 3 4 5 6 7 8 9 10 11 !-!!!!!-!!!!!-!-!!-!!-!-!---!!-!!!!!-!!!!!!!!!!!!!!!!!!!! H OBJ ACC 11 00 00 Object Title Via tab11_acc we will send the Z403 field sub field y to the index: ! 1 2 3 4 5 6 7 8 !!!!!-!!!!!-!-!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!-!-! Z403 OBJ y

expand_doc_bib_z403 And then we will make the new access browsable via the web and the GUI GUI: $data_tab/pc_tab_sear.eng ! 2 3 4 5 !!--!!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!! SC USM01 L ADAM Object title OBJ WEB: $alephe_root/www_f_eng/scan-include-2 <option value=OBJ $$5000-S"OBJ">Digital Object Title</option> Or WEB: $alephe_root/www_f_eng/find-e-code-include <option value=SCAN_OBJ $$FXX-S"SCAN_OBJ">Browse >Digital Object Title</option>

expand_doc_bib_z403 User browses for and finds object title “Brady family portrait 1970 “

expand_doc_bib_z403 In the previous slide a browse for “Brady family portrait 1970” finds system number 50777. “Brady family portrait 1970 “ appears no where in the document:

expand_doc_bib_z403 The object title has been “expanded” to the document from the object and then indexed

expand_doc_bib_z403

expand_doc_bib_z403 There but not there The object title is there (indexed with the bibliographic record) but not there (in the actual data)

expand_doc_bib_z403 We will now add the object title to a printout format of the service “columnar printout (print-08)” In order for an expand procedure to be included in the print-08 service it should be added to tab_expand in the PRINT-COL Expand Menu.

expand_doc_bib_z403 Here is the expand procedure in tab_expand table: Here is the header explanation for PRINT-COL Expand Menu in tab_expand table: ! PRINT-COL - p_print_08_a - columnar printout (Service) Here is the expand procedure in tab_expand table: ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> PRINT-COL expand_doc_bib_z403

expand_doc_bib_z403 The table $data_tab/rep_tab_short.eng states which fields are printed via the service print-08. Here we can specify the Z403 virtual field and desired sub fields (because it was included in the PRINT-COL menu of tab_expand): 006 L Doc. No. SYS 010 02 C01 006 L Author 1#### 025 03 C02 --- Y 006 L Document Title 245## 030 02 C01 --- 006 L Digital Object Title Z403#y 029 02 C01 --- 006 L Digital Object Usage Z403#t 006 02 C01 --- Format 006

expand_doc_bib_z403 The format made in rep_tab_short.eng is then added to $aleph_root/pc_b_eng/p-print-08.xml In our example it was format 006 <cbitem> <value>006</value> <display> Document no. | Author | Document Title| Digital Object Title | Digital Object Usage </display> </cbitem>

expand_doc_bib_z403 Now we can run print-08 with our new format which takes advantage of the expanded fields

expand_doc_bib_z403 Digital Object Title is in the printout but not in the actual bibliographic record - there but not there

expand_doc_bib_z403 There but not there The object title is there (displaying in format with the bibliographic record) but not there (in the actual bibliographic data Z00 table)

expand_doc_bib_loc_usm

expand_doc_bib_loc_usm The expand procedure expand_doc_bib_loc_usm might appear as follows in $data_tab/tab_expand: ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> U39-DOC expand_doc_bib_loc_usm WORD expand_doc_bib_loc_usm ACC expand_doc_bib_loc_usm INDEX expand_doc_bib_loc_usm SORT-DOC expand_doc_bib_loc_usm WEB-FULL expand_doc_bib_loc_usm WEB-BRIEF expand_doc_bib_loc_usm WEB-FULL-1 expand_doc_bib_loc_usm GUI-BRIEF expand_doc_bib_loc_usm CREATE-Z13 expand_doc_bib_loc_usm PRINT-COL expand_doc_bib_loc_usm PRINT-CAT expand_doc_bib_loc_usm TAB33-DOC expand_doc_bib_loc_usm Z39_SERVER expand_doc_bib_loc_usm RET expand_doc_bib_loc_usm SECTION1 expand_doc_bib_loc_usm EXPORT-03 expand_doc_bib_loc_usm Z39_HOL expand_doc_bib_loc_usm WEB-MAIL expand_doc_bib_loc_usm PUBLISH expand_doc_bib_loc_usm

expand_doc_bib_loc_usm The expand_doc_bib_loc_usm program builds four fields: SBL LOC STS PST Fields are built from: the Z30 (item record) the Z16 (subscription record) the 852 field (location) of the holdings record

expand_doc_bib_loc_usm Often the fields which are built via the expand_doc_bib_loc_usm program are referred to as “virtual” fields. They have a specific structure (sub fields) and may be used in a variety of ways depending on the expand menu with which they are used.

expand_doc_bib_loc_usm BIB Record Expand procedure expand_doc_bib_loc_usm with multiple menus Z30 item Record HOL Record Z16 Subscription

expand_doc_bib_loc_usm Virtual field “SBL” The SBL field has no indicators and one subfield (a) which contains the sub library code.

expand_doc_bib_loc_usm Virtual field “LOC” The LOC has first indicator 0-8 depending on the call number type. The second indicator is blank. It also has these sub fields: $b [sublibrary code] $c [collection code] $h [call number] if call number type is 0-3 or 6-8. $j [call number] if call number type is 4. $l [call number] if call number type is 5. $o [material type] .

expand_doc_bib_loc_usm Virtual field “STS” The STS field has no indicators and one subfield (a) which contains the item status code.

expand_doc_bib_loc_usm Virtual field “PST” – part 1 1st indicator: call number type (0-8). 2nd indicator: undefined, contains a blank.

expand_doc_bib_loc_usm Virtual field “PST” – part 2 $$0 [origin of the PST field]. If the field originates from an item record, then the subfield contains Z30 ($$0Z30). If the field originates from a holdings record, then the subfield contains HOL ($$0HOL). $$1 [unique identifier of the record of origin] If the field originates from an item record, then the subfield contains the system number of the linked administrative record and the item sequence number (for example, $$11000005921000010). Format: <Z30-DOC-NUMBER> <Z30-ITEM-SEQUENCE> If the field originates from a holdings record, then the subfield contains the holdings library code and the system number of the holdings record (for example, $$1USM60-000001909). Format: <library code>60;holdings system number>

expand_doc_bib_loc_usm Virtual field “PST” – part 3 $$b [sublibrary code]. $$c [collection code]. $$d [item status] if there is no item process status. $$e [item process status] if there is an item process status in the item record. $$f [temporary location flag]. If the sublibrary, collection and call number information are temporary (the Temporary Location box is checked), then the subfield contains Y ($$fY). If the location is not temporary, then the subfield contains N ($$fN).

expand_doc_bib_loc_usm Virtual field “PST” – part 3 $$h [call number] if call number type is 0-3 or 6-8. $$j [call number] if call number type is 4. $$l [call number] if call number type is 5. $$n [call number type] $$o [material type - column 1 of the tab25.lng table] (for example, BOOK). $r [linked holdings record] contains the holdings library code and the system number of the holdings record linked to the item (for example, $$1USM60-000001909). Format: <library code>-<holdings system number>

expand_doc_bib_loc_usm Virtual field “PST” – part 4 $y [copy number] $$3 [material type - display form: column 3 of the tab25.lng table] (for example, Book). $$4 [sublibrary name] $$5 [collection name] $$6 [item loan status - display form] $$7 [item process status - display form]

expand_doc_bib_loc_usm We have system number 50756 in USM01

expand_doc_bib_loc_usm 50756 in USM01 is connected to HOL record 50487 in USM60

expand_doc_bib_loc_usm 50487 in USM60 is connected to item barcode 50756-10 in USM50

expand_doc_bib_loc_usm The administrative record in USM50 is 50756

expand_doc_bib_loc_usm We may view the results of expand_doc_bib_loc_usm in a variety of ways and places. If we add a specific procedure to tab_expand we can then choose the procedure via UTIL F 4 doc_expand Here we make a procedure called EDBLU (abbreviation of expand_doc_bib_loc_usm, but we can call it whatever we want): ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> EDBLU expand_doc_bib_loc_usm

expand_doc_bib_loc_usm From UTIL F 4 in USM01 we will choose “doc_expand” and choose expand procedure EDBLU and system number 50756

expand_doc_bib_loc_usm From UTIL F 4 in USM01 we will choose “doc_expand” and choose expand procedure EDBLU and system number 50756

expand_doc_bib_loc_usm The bibliographic fields are presented as well as the expanded (virtual) fields as created by the specific fix routine: Virtual fields

expand_doc_bib_loc_usm The item (z30) information:

expand_doc_bib_loc_usm The HOL information information:

expand_doc_bib_loc_usm And if we remove the item process status from the record …

expand_doc_bib_loc_usm The we also get item status information:

expand_doc_bib_loc_usm The fields created via expand_doc_bib_loc_usm can be used for both display and indexing purposes. Here is a sample of such fields. Notice tab11_word uses the virtual fields and sub fields: $data_tab/tab00.eng H WSL W-014 00 02 W-Sublibrary H WICOL W-030 00 00 W-Word from Item Collection H WIMTY W-031 00 00 W-Word from Item Material Type H WICOP W-032 00 00 W-Word from Item Copy Status $data_tab/tab11_word SBL 01 WSL PST## c 03 WICOL PST## o 03 WIMTY PST## d 03 WICOP

expand_doc_bib_loc_usm In order to be able to index the expanded fields built via expand_doc_bib_loc_usm, the expand procedure must appear with the WORD expand menu in tab_expand: ! 1 2 3 !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> WORD expand_doc_bib_loc_usm The WORD expand menu is used to create words via manage_01 (service to update word index) and via ue_01 (when item is updated in the GUI)

expand_doc_bib_loc_usm In the next slide we will search for the indexes which have been built via the expanded fields: WSL Word from Sublibrary WICOL Word from Item Collection WIMTY Word from Item Material Type WICOP Word from Item Copy Status Via these indexes it is possible to retrieve bibliographic records based on connected items.

expand_doc_bib_loc_usm Here we have retrieved bibliographic records via the indexes which are built from “expanded” item information

expand_doc_bib_loc_usm Similarly, it is possible to build logical bases according to the indexes which are built from expanded fields. Here is an example of a base built according to WSL (Word from Sub Library) ! 1 2 3 4 5 6 7 8 9 !!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!-!!!!!!!!!> MED Medicine Library USM01 USM01 Y wsl=med

expand_doc_bib_loc_usm There but not there The Word from Sub Library is there (indexed with the bibliographic record) but not there (in the actual data).