External users are stored and managed outside the library’s scope, usually in another system maintained by the institution (for example, in a Student Information System). These users' information is loaded into Alma and is synchronized on a regular
We use a PERL script (can be found on github) in order to read current patron information from ODS and build XML file to send to Alma. Note that all new patrons get the Patron role automatically assigned by Alma, using the Role Assignment Rules.
This is a manual "step-by-step" procedure that you can simplify or automate (i.e. with cron scripts) at various stages. We receive the patron data from a system called S3 (or ESSE3) in excel file: but you can use any equivalent SIS that permits to
So, you've moved to Alma, but your patron records are still in Aleph PLIF format. In this article we will describe a xsl file that can be used in order to convert Aleph patron PLIF records into Alma's SIS format. The XSLT file is a template that handles
So, you've moved to Alma, but your patron records are still in Voyager SIF format. You have read an even implemented the code in the blog post Using Voyager SIF records to create Alma XML patron load data only to discover you need the output in Alma SIS
Introduction to Creating and testing an API application. download. Creating and testing an API application to retrieve and update bibliographic records. download. Creating and testing an API application to retrieve data via Alma analytics. download.
So, you've moved to Alma, but your Student or HR system is still providing patron records in Voyager SIF format. We've been using the Voyage SIF format for patron records since implementing Voyager, and so over time developed a PHP include file to allow
When a file is uploaded with special characters in XML, the special characters should be escaped. This should be done when uploading a patron file in SIS load, or a bibliographic file via an import profile. In the following example, a patron file with