1. Presenter: Yoel Kortick
AlephPublishing services How to define available items with process status and how to use the threshold version 18 and up
Presenter: Yoel Kortick

2. Introduction
This presentation assumes a prior knowledge of how to use the publishing services.
For information specifically on publishing see the files on the Doc Portal relating to Aleph Publishing services
This presentation will focus specifically on
How to define items as available even though they have an item process status
How to use the THRESHOLD parameter

3. The general rule The general rule:
Any item which has a process status will be considered unavailable when appearing as a result of publish_06 unless otherwise specified in column 3 of tab_expand
Any item on loan will be considered unavailable when appearing as a result of publish_06
We will now analyze and demonstrate the general rule

4. Our example We will use the case of publishing set PRIMO-AVAIL
This set is defined as follows in $data_tab/tab_publish: !
!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!-!-!!!!!-!!!!!!!!!!!!!!!
PRIMO-AVAIL N AVA MARC_XML
The expand procedure AVA (column 4 of tab_publish) is defined (for now) as follows in $data_tab/tab_expand: !
!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
AVA expand_doc_bib_avail

5. Existing process statuses
The library has the following process statuses:
il-aleph02-18(1) USM50-YOELK>>grep ITEM-PROCESS $data_tab/pc_tab_exp_field.eng
ITEM-PROCESS-STATUS L Not in Process
ITEM-PROCESS-STATUS L At bindery BD
ITEM-PROCESS-STATUS L Bindery prep BP
ITEM-PROCESS-STATUS L Cancelled CA
ITEM-PROCESS-STATUS L Claimed CL
ITEM-PROCESS-STATUS L Cataloging CT
ITEM-PROCESS-STATUS L Missing MI
ITEM-PROCESS-STATUS L Lost MS
ITEM-PROCESS-STATUS L Not arrived NA
ITEM-PROCESS-STATUS L Not published NP
ITEM-PROCESS-STATUS L Order initiated OI
ITEM-PROCESS-STATUS L On order OR
ITEM-PROCESS-STATUS L Ordered--received RE
ITEM-PROCESS-STATUS L Depository HD
ITEM-PROCESS-STATUS L Planning Exhibit Loan PE
ITEM-PROCESS-STATUS L On Exhibit OE

6. Our examples
System number 52205: two items, one with process status CT ( ) and the other with no process status ( )
System number 52206: one item ( ), no process status
System number 52207: one item ( ) with process status BD
System number 52208: 18 items, no process status ( to )
System number 52209: one item ( ) with process status CT

7. Our examples All examples have been “picked up” by UTIL E 21
il-aleph02-18(1) USM01-YOELK>>grep 522 $data_scratch/run_e_ | tail -8
HANDLING DOC NO. - USM :48:48
HANDLING DOC NO. - USM :49:19
HANDLING DOC NO. - USM :49:49
HANDLING DOC NO. - USM :52:50
HANDLING DOC NO. - USM :53:20
HANDLING DOC NO. - USM :56:20
HANDLING DOC NO. - USM :57:51
HANDLING DOC NO. - USM :58:21

8. Publishing the records
The example system numbers to are published via publish_06 service

9. Results We will do as follows to view the results:
il-aleph02-18(1) USM01-YOELK>>cd /exlibris/users/yoelk/publishing_27_aug/PRIMO-AVAIL/tar/
il-aleph02-18(1) USM01-YOELK>>ls
aleph.PRIMO-AVAIL tar.gz
il-aleph02-18(1) USM01-YOELK>>mkdir open_file
il-aleph02-18(1) USM01-YOELK>>cp -p aleph.PRIMO-AVAIL tar.gz open_file/
il-aleph02-18(1) USM01-YOELK>>cd open_file/
il-aleph02-18(1) USM01-YOELK>>gzip -d aleph.PRIMO-AVAIL tar.gz
il-aleph02-18(1) USM01-YOELK>>tar xf aleph.PRIMO-AVAIL tar
il-aleph02-18(1) USM01-YOELK>>ls -1rt *xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
We will now examine the xml files to see what was produced regarding “availability”.

10. Results
52205 (2 items, 1 with process status CT, 1 with no process status)
<subfield code="e">available</subfield>
52206 (1 item with no process status)
<subfield code="e">available</subfield>
52207 (1 item with process status BD)
<subfield code="e">unavailable</subfield>
52208 (18 items all with no process status)
<subfield code="e">check_holdings</subfield>
52209 (1 item with process status CT)
<subfield code="e">unavailable</subfield>

11. Summary 52205 is considered available.
This is because at least one item (of the related two items) does not have a process status
52206 is considered available
This is because it has one item which does not have a process status)
52207 and are unavailable
This is because both have items which have a process status
52208 states “check_holdings”
This is because it has more items that the default THRESHOLD amount (default THRESHOLD amount is 10)

12. Reconfiguration We will now reconfigure the system as follows:
Items with process status BD or RE will be considered “available”
Bibliographic records with less than 20 items will not get message “check_holdings”
We will do this by defining the threshold and “available” item process statuses in column three of tab_expand.
The explanatory note here in the next slide will be helpful

13. Reconfiguration !
!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
!* By default any item with a process status is considered unavailable
!* To define a process status as available it should be listed as follows
!* in column three !*
!* By default the THRESHOLD is 10. This means that and record with more
!* than 10 items will get message "check_holdings". To define a
!* different number, such as 20, it should be listed as follows in
!* column three
AVA expand_doc_bib_avail THRESHOLD=020;AVA=BD,RE
Now system number (with 18 items) will not get “check_holdings”
Now system number (with 1 item which has process status BD) will not get “unavailable”

14. Reconfiguration and UTIL E 21
After making a change of this nature UTIL E 21 should be restarted and the system numbers reupdated.
il-aleph02-18(1) USM01-YOELK>>grep 5220 run_e_
HANDLING DOC NO. - USM :00:04
HANDLING DOC NO. - USM :00:04
HANDLING DOC NO. - USM :00:04
HANDLING DOC NO. - USM :00:04
HANDLING DOC NO. - USM :00:04

15. Testing new configuration
We run publish_06 as we did previously, except that we send the results to a different directory and have different configurations on the server.

16. Testing new configuration
We will check the new files as follows:
il-aleph02-18(1) USM01-YOELK>>cd /exlibris/users/yoelk/publishing_27_aug_second
il-aleph02-18(1) USM01-YOELK>>cd /exlibris/users/yoelk/publishing_27_aug_second/PRIMO-AVAIL/tar
il-aleph02-18(1) USM01-YOELK>>ls -lrt
total 8
-rw-rw-r aleph exlibris Aug 27 14:06 aleph.PRIMO-AVAIL tar.gz
il-aleph02-18(1) USM01-YOELK>>mkdir open_file
il-aleph02-18(1) USM01-YOELK>>cp -p aleph.PRIMO-AVAIL tar.gz open_file/
il-aleph02-18(1) USM01-YOELK>>cd open_file/
il-aleph02-18(1) USM01-YOELK>>gzip -d aleph.PRIMO-AVAIL tar.gz
il-aleph02-18(1) USM01-YOELK>>tar xf aleph.PRIMO-AVAIL tar
il-aleph02-18(1) USM01-YOELK>>ls -1rt
aleph.PRIMO-AVAIL tar
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml
USM PRIMO-AVAIL.xml

17. Results
52205 (2 items, 1 with process status CT, 1 with no process status)
<subfield code="e">available</subfield>
52206 (1 item with no process status)
<subfield code="e">available</subfield>
52207 (1 item with process status BD) CHANGED
<subfield code="e">available</subfield>
52208 (18 items all with no process status) CHANGED
<subfield code="e">available</subfield>
52209 (1 item with process status CT)
<subfield code="e">unavailable</subfield>

18. Summary
52207 (1 item with process status BD) changed from unavailable to available because after the first run of publish_06 BD was added to tab_expand to be an available item process status.
52208 (18 items all with no process status) changed from check_holdings to available because the threshold was changed from the default 10 to 20 via tab_expand.

19. Summary Review of “general rule”:
Any item which has a process status is unavailable unless otherwise defined in tab_expand
Any record which has more than the threshold amount of items will automatically get check_holdings
The threshold is 10 unless otherwise defined in tab_expand

20. Serials 52213 format Serial, one item not on loan no process status
52214 format Serial, one item not on loan has process status CT
52215 format Serial, one item on loan no process status
52216 format Serial, one item not on loan has process status BD (which is available according to tab_expand)
All records have been updated by UTIL E 21
il-aleph02-18(1) USM01-YOELK>>grep run_e_
HANDLING DOC NO. - USM :17:07
HANDLING DOC NO. - USM :17:37
il-aleph02-18(1) USM01-YOELK>>grep run_e_
HANDLING DOC NO. - USM :18:37
HANDLING DOC NO. - USM :19:07
il-aleph02-18(1) USM01-YOELK>>grep run_e_
HANDLING DOC NO. - USM :19:37
HANDLING DOC NO. - USM :20:08
HANDLING DOC NO. - USM :20:38
il-aleph02-18(1) USM01-YOELK>>grep run_e_
HANDLING DOC NO. - USM :22:38

21. Serials
Publish_06 is run for the range of documents

22. Serials
52213 format Serial, one item not on loan no process status. publish_06 states available
52214 format Serial, one item not on loan has process status CT. publish_06 states unavailable
52215 format Serial, one item on loan no process status. publish_06 states unavailable
52216 format Serial, one item not on loan has process status BD (which is available according to tab_expand). publish_06 states available

23. Check_holdings
There is an additional case where the AVA $$e may state “check_holdings” even though the total number of items is less than the threshold.
Here is the case.
The record has multiple items with at least two of the items having enumeration level a (volume) filled in and at least one (but not all) items are on loan. The item which is on loan must be one of those which has an enumeration level.

24. Check_holdings
Here are three items (less than the threshold amount). Two items have enumeration level a filled in, and one of the items which has an enumeration level is on loan
One item is on loan
Enumeration level a filled in

25. check_holdings
The AVA subfield “e” states “check_holdings”

26. check_holdings
But … if we were to remove the enumeration levels and leave one item on loan…
Then now we have “Available”