Deleting (old, inactive) patrons who still have SSN's
- Article Type: General
- Product: Aleph
- Product Version: 17.01
Description:
Over the last few months we have successfully implemented Banner and done away with SSNs in ALEPH for active patrons.
A quick check using the query
select count(z308_rec_key) from z308 where z308_rec_key like '02%' and z308_rec_key not like '02R%' ;
shows that we still have 70,109 SSNs (Banner IDs are 9 characters beginning with "R").
I can easily extract the system key, barcode, etc for these patrons, whom we will consider all to be expired. (They are not being deleted by Circ tools, since their expiration date has been set previously well into 2010.)
I have experimented with creating a PLIF type record to delete these, but I run into snags. There is somethng in the instructions I am not understanding correctly. My goal would be to write a short trasaction beginning with "D" followed by "02" for the type and then the SSN Nothing else on the line. That fails.
I am following the notes on the PLIF loader document for v. 17, page 16 (last update: August 23, 2006), which reads:
--------------------------------
When "D"eleting a patron, there is no need to specify all of the Znnn records to be deleted. Only the Z303 (the global-user information record) should be included. In other words, the input- line for the patron to be deleted should include only the matching data and the global user record (required only because it has the "D" flag in it). If other records are included in the
input file they should appear with the action flag X or D, otherwise they will cause the input-line to be rejected.
---------------------------------
Here is an example of what I did followed by the various log files generated for the failing transaction (all in TEST).
--------------------------------------------PLIF RECORD I created (entire) BELOW------------------------------
D02564608398
--------------------------------------------------------END-------------------------------------------------
The tail end of the log file is:
---------------------------------------------
Load: /exlibris/aleph/u17_1/utf_files/exlibris/aleph/u17_1/alephe/error_eng/p_file_20
1 END READING AT 16:28:08
-----------------------------
Processed RECORD 000001
Processed MATCHED 000001
-----------------------------
end
---------------------------------------------------------
And the report file is:
--------------------------------------------------------
## - XML_XSL
<?xml version="1.0"?>
<printout>
<form-name>patron-loader</form-name>
<form-language>ENG</form-language>
<form-format>00</form-format>
<subject>Patron Loader</subject>
<section-01>
<form-date>08/06/2009</form-date>
</section-01>
<section-02>
<line-number>000001</line-number>
<table-name>z303</table-name>
<action>reject</action>
<match-id>02564608398</match-id>
<patron-id></patron-id>
<msg-code>5024</msg-code>
<msg-desc>Error: System could not generate "dummy" barcode. Check tab10 or z52.last-bor-id-1.</msg-desc>
</section-02>
</printout>
-------------------------------------
MY QUESTION: What is the minimal amount of info I have to put on a PLIF line to have it do a patron delete?
Resolution:
I think the best thing would be to update the z305_expiry_date of these patrons (via SQL) to a date in the past, so that the p_cir_23 patron delete job *can* be used to delete them.
The following SQL could be used for that:
SQL-TTU50> update z305 set z305_expiry_date = 'yyyymmdd' where substr(z305_rec_key,1,12) in (select z308_id from z308 where z308_rec_key like '02%' and z308_rec_key not like '02R%');
- Article last edited: 10/8/2013