The Balboa University Library website is a showcase for the APIs avaialble with the Sierra Library System Platform. When you visit our pages you see a variety of ways in which you can create web content and "plug it in" to your Sierra system.
Below is a list of the specific Sierra APIs that we've employed and exactly how we've implemented them on this site.
Note! This is NOT a complete list of available APIs. It's only those we've actually employed on this site. You can also review our complete documentation discussing the entire Sierra API suite.
The Patron API |
||
| Method | Read/Write? | How Implemented on This Site |
|---|---|---|
| register | write | Patrons can perform online registration and the Sierra API adds the record to the database. The system will create a temporary barcode and automatically assigns them the patron type of 15 (self-registered). |
| validate | read | When the patron logs in as a patron, the API validates that the user credentials are valid in the Sierra database. |
| find | read | Once a patron logs in, the API looks up their patron record and provides the ability to display the patron name and other information on pages throughout the site ("My Account" pages, for example). |
| update | write | A logged in patron can change their PIN from the "My Account" page. The Sierra API validates the format of the new PIN and (if in proper format) updates the patron record in the Sierra database with the new PIN number. Patrons can also update or delete data on their own patron record: addresses, phone numbers, emails, etc. |
| checkouts | read | Patrons can access their "My Account" page and get a list of what they have checked out. The checkouts API call retrieves all the items checked out to the logged-in patron and provides a link to the associated item record. |
| checkouts renewal | write | Patrons can renew any item or set of items from their list of checkouts. The Sierra API makes the renewal request against the Sierra database and the user is informed whether or not the renewal was successful. |
| checkouts history | read | Patrons can get a current list of titles they've checked out in the past. The Sierra API provides the checkout history information which allows us to link to and display the bibliographic information. We have also implemented an API method that allows users to remove selected items from their checkout history. |
| hold requests | write | Patrons (once logged in) can see a title in the carousel and place a hold request on it. The Polaris API places the hold request in the Sierra database and provides information about whether or not the hold was placed successfully. |
| holds | read | Patrons can get a current list of titles they have on hold. The API provides a list of all the holds related to the specific patron. |
| holds modify - cancel | write | From the list of their holds a patron can choose to cancel one or more holds. The Sierra API makes the cancellation request and provides information about whether or not the hold was canceled in the Sierra database. |
| holds modify - freeze/unfreeze | write | From the list of their holds a patron can choose to freeze an active hold (or UNfreeze an already frozen hold). The Sierra API makes the request and provides information about whether or not the hold was frozen/unfrozen in the Sierra database. |
| holds modify - change pickup location | write | A patron can change the pickup location of one or more holds in their list. The Sierra API makes the location change request and provides information about whether or not the pickup location was changed in the Sierra database. |
| fines | read | From their "My Account" page a patron can get a list of all the current fines and fees on their account including: descriptin, charges, partial payments, etc. |
The Bib API |
||
| Method | Read/Write? | How Implemented on This Site |
| bib query | read | The bibs query API call is used to generate the titles in the carousel. A Sierra staff user creates a review file and then generates the accompanying JSON. We give the JSON string to the query API which gives our app a list of bib ids and we build the carousel from there. |
| bib id | read | This is the fundamental API call used throughout our integration. Any time we present bibiiographic information about a specific title (title, author, format, cover art, etc.) we used this API to extract the information from Sierra. ANY MARC data is retrievable with the bib id API method. |
| bib MARC | read | Yes, the bib id API returns selective MARC data; but the bib MARC API returns the entire MARC record data. Useful particularly on the full bib detail display where we offer the ability to view the full MARC record. |
The Item API |
||
| Method | Read/Write? | How Implemented on This Site |
| items | read | The items API goes hand-in-hand with the bibs API. As you'd expect, when we look at the bibliographic detail of a record, we also use the items api to list all the linked item records. The items API is also used extensively throught the "My Account" pages in our implementation. In the case of checkouts or reading history the basic information we have about each entry is it's item ID. So when we get a list of items (patron checkouts for example) we then call the bib API to supplement the item information with bib data such as the item's title, author, etc. |
The Internal - Metadata API |
||
| Method | Read/Write? | How Implemented on This Site |
| user | read | The user API authenticates a Sierra staff user login. There is a website configuration page that is only accessible by authorized library staff members. |
| pickup locations | read | The pickup locations API provides a list of the library locations which have been identified in Sierra as holds pickup locations. The list comes into play whenever a patrons choose to place a hold or change hold pickup locations. |