SCF Requests

All things related to SCF processing of physical item request from the SCFapp.

Delivery locations with Codes

Partners with Library Names, Pull Slip Codes and Courier Slip Code

Institution Name (IZ) Library name Location Code (Pull Slip) Courier Slip Code
American University American University Library AU AU
AU, Washington College of Law Library Pence Law Library AULAW AU-WCL
Catholic University of America Mullen Library CU CU
CUA, Columbus School of Law * Law Library (CU LAW) * CU LAW
University of the District of Columbia Main Library DC DC/UDC
UDC, Law School UDC Law Library DCL ?
Gallaudet University Gallaudet University Library GA GA
George Mason University Libraries Fenwick Library GM GM
  Mason Square Library GMA GM-A
  Mercer Library GMP  
  Law Library GMA GML
Georgetown University Lauinger Library GT, GT-OD GT
  Bioethics Research Library GT-Bioethics (GT)
  Blommer Science Library GTB (GT)
  School of Continuing Studies Library GT-SCS (GT)
  Woodstock Theological Library GT-WTL (GT)
GU, Law Library Georgetown Law Library GTL GTL
George Washington University Gelman Library GW GW
  Eckles Library GWE MTV
  Virginia Science & Technology Campus GWN GW-NVCL
  GW Online-Only Community GWOC (GW)
GWU, Himmelfarb Health Sciences Library Himmelfarb Health Science Library HI HI
GWU, Jacob Burns Law Library Jacob Burns Law Library JB GW-JB
Howard University Founders Library HU HU
  Louis Stokes Health Sciences Library HU-HS HU-HS
  Law Library HUWC HU LAW
Marymount University Reinsch Library MU MU
  Ballston Coakley Library Extension MUB MU-B
Shared storage institution WRLC - Shared Collections Facility WR  
  Trinity Library (for Trinity Patrons) TR TR
Trinity University Washington * Trinity Main (TR) * TR

* Not configured as part of the CLS/AFN Fulfillment Network

Physical item request that originated as an ILLiad physical item request

ILLIad Physical Item Requests through Alma

 

The SCF will start to transition to filling ILLiad physical item requests through Alma.  Currently these requests are made via email.  These new requests can be identified as ILLiad requests using the pull slip.  The pull slip for these requests will have an ILL number, return address, and delivery information where you would expect the Hold line, the patron’s name, and The Due Date line.  See example below:

These requests would be pulled as any normal physical item request coming into the SCF IZ via Alma.  Use the information on the “Mailing:” line to determine if an item should be mailed or sent to the owning library (some form of Yes for mailing, some form of No to send the item to the owning IZ.)  If you are not certain, contact the owning library’s staff for clarification.  For the most part, we would expect that not mailing the item would be the exception.  In either case, you will scan the item in the SCF IZ to put it “In Transit”.

 

Mailing: Yes

If the item is to be sent to the requesting institution, use the “Please deliver to:” address for mailing.  Be sure to include the pull slip with the item.  You will also need to logon to the owning IZ with the SCFStaff account.  You will need to scan the barcode (without the X)  using the Default_Circ_Desk.  This will place the item on the owning library’s “On Hold” shelf and notify the ILL Staff patron that the item is being sent.

 

Mailing: No

If the item is not to be mailed to the ILL borrower, then follow standard procedure.  Send to the owning library via the courier.

 

These loaned items will be returned to the owning libraries and come back to the SCF via the courier.

 

Remote Storage Location Configuration

Configuring a Physical Location as a Remote Storage Location

This configuration enables requests for items in the location to be exported to the Remote Storage Application. These instructions assume you are creating a new location, but they can be used to configure an existing location as well.

Prerequisites 

Prerequisites should already be configured in your IZ.

Creating/Editing the Location

At the Library level, go to Alma Configuration > Fulfillment > Locations > Physical Locations and “+ Add Location”. Type should be “Remote Storage” and Remote Storage is “Shared Collections Facility”. Next, edit the location to add circulations desks using the “Attach Existing Circulation Desk” menu. Attach two desks: One is the circ desk that your operators who process items at this location are assigned to; it should not have the option to reshelve items in the remote storage locations. The other is the “WRLC SCF Storage” desk; it does have “Reshelve” checked.

Integration with the SCF Remote Storage App

In order for the Remote Storage App to recognize this location, it must be added to the app’s configuration file, so let WRLC know what the location’s code is.


If you want to publish new items added to this new location to accession them into the SCF, the location must be added to the logical set that is used by the Publishing Profile we set up for accessioning. Please coordinate this also with WRLC so we can be sure that it is done without causing the publishing job ID to change or to have existing items in the SCF re-published.

Updating the Remote Storage Application configuration

In the updated Azure web app version of the Remote Storage Application (currently used for PSBs; will deploy to production IZs soon), configurations (including storage locations for all IZs) are stored on the sftp server at sftp.wrlc2k.wrlc.org in a file named conf.json. 

The PSB config.json is found at:

PSB: /home/scfapp/AlmaRSA-PSB/conf.json

You'll need to be at WRLC HQ or on the WRLC VPN to update conf.json.

To make updates to the PSB config file, use an FTP client such as FileZilla to download conf.json to your local computer. Then make your desired changes and re-upload it to the same location via FTP.

Once the PSB config file is updated on the server, it must be loaded into the Remote Storage Application by visiting the following the URL:

PSB: https://wrlc-alma-remote-storage.azurewebsites.net/configuration

You can then check the Remote Storage Application's log files to verify that the conf file loaded successfully.

This page will be updated with additional file information once the web app is deployed to production IZs.