Functions for Converting PeopleSoft Patron Data into a PLIF File for Aleph
Tags:
PLIF, Patron Load Interface flat File, TCU, PeopleSoft, Aleph, Intermediate
Last Updated:
8/5/2010Aug 06, 2010 18:23
- Description
This is a set of VBscript functions and a subroutine we use for converting patron data from the university's PeopleSoft information system to a patron file in PLIF format that can be loaded into Aleph using the Circulation p_file_20 service. It is one component in an overall procedure that consists of:
- Two view tables in PeopleSoft, one containing student data and one for faculty/staff data.
- Another view table made available by the university IS department that maps university ID numbers to network usernames. This is so that one of the ID records placed in the PLIF file can include the network username in the Key Data field, to enable LDAP authentication when logging on to the My Account functions in the online catalog.
- Additional tables in Access that map codes used in PeopleSoft student and staff records to codes we use in our Aleph patron records. (The attached queries show how these tables are used, but since the codes are institution-specific, I have not attached the table data.)
- Simple VBscripts that are invoked by a Windows shortcut to start MS Access and run the macro to build either a student or faculty/staff PLIF file, then copy the output file to a file share on a network server.
- A Microsoft Access database that links to the three tables above using and ODBC connection, and includes a macro, several queries, temp tables populated by the queries, and the VBscript functions and subroutine included here. Most of the functions are invoked by the Make Table query that is used to populate the a temp table that becomes input for the Aleph_Create_PLIF subroutine. The output of that subroutine is a PLIF file saved on the user's hard drive (the script used to invoke MS Access copies this file to a file share when the user exits Access). I've included the Make Table query along with a file of containing the functions, but the query itself is hightly institution-specific, since it maps various status codes used in PeopleSoft to codes we use in our Aleph patron records.
- A custom service on the Aleph server that transfers the PLIF file from the file share (which is also accessible by a web server) to Aleph, and then invokes p_file_20 to load the PLIF file into Aleph.
- Author: Kerry Bouchard
- Additional author(s):
- Institution: Texas Christian University
- Year: 2010
2005
- License: BSD style
- Short description: Use, modification and distribution of the code are permitted provided the copyright notice, list of conditions and disclaimer appear in all related material.
- Link to terms: [Detailed license terms]
- Skill required for using this code:
Choose one of the following: basic, intermediate, advanced, expert. Please also add your choice as a tag at the bottom of the page.
State
'Stable'
Programming language
VBscript (Application Basic in Microsoft Access, which is just VBscript with some Access-specific objects)
Software requirements
To use as is, requires Microsoft Access. Functions could be adapted to other platforms.
Screen captures
Place your screen shot here...
Author(s) homepage
http://
Download
Attach the code file(s) to this page and link to them here.
Page attachments management can be reached from the top-right menu - 'attachments' after page save.
Working example
not applicable
Using the following Ex Libris open interfaces
None. Supplies data for p_file_20 patron file loader service in Circulation.
Changes
Version 1.2 ....
Text...
Version 1.1 ....
Text...
...
Text...
Release notes
Text...
Installation instructions
Many of the codes used for patron records in both PeopleSoft and Aleph are institution-specific, so this is not
"turnkey" software but just provided as an example for getting started for anyone who is interested.
 | Tip sample |
 | Info sample |
TO DO list
Text...
Known issues
Text...
Comments
Text...