Shared Collections Facility (SCF) Institution Zone

Information on how the Shared Collections Facility Institution Zone (a.k.a. the SCF IZ) is configured, how to accession items to the SCF in Alma, and how SCF items in an owning Institution Zone (IZ) are copied to, requested from, etc. the SCF IZ.

Workflows for items at the SCF

Workflows on accessioning new items to the SCF, requesting SCF items, returning SCF items, etc.

Workflows for items at the SCF

Accessioning new items to SCF

Now that we have new architecture in which the owning IZ’s item record is used for fulfillment, there are new procedures for preparing items to be sent to the SCF for accessions. Prior to taking any of the steps below, please contact the SCF Supervisor to arrange transport and ensure there is space in the processing areas. Creation of the SCF version of the record will be done automatically by a special script created by Ex Libris.  To trigger the script, you will need to do the following:

  1. Identify item(s) in the owning IZ that you would like to send to the SCF via weeding or other selection process.

 

  1. Edit the items and give them a temporary location with the type “Remote Storage”.  You should be familiar with this list and it includes location codes like “wrlc stor” and “wrlc stnc”.  For the full list or if you aren’t certain, you can check the physical locations list as shown below.

 

  1. Editing the locations can be done to individual records during the weeding/selection process as shown below or as part of a batch change physical items job on a list of barcodes.
     

 

 

  1. Scan in the item(s) barcode – this causes the item to be put in transit or in process so that the item does not appear as available while in transit to SCF and being processed by SCF staff.
     

 

  1. Notify the Director of Library and User Services at WRLC and we will run the “SCF publishing profile“ publishing profile job for your owning IZ.  Note:  do not edit the publishing profile in any way.  This publishing profile uses a logical set of all items with a remote storage location.  By running this job we will publish any new additions to this set and your items will automatically have an identical item record created in the SCF IZ.

Workflows for items at the SCF

Requesting SCF Items

Below are resources for different requesting workflows:

Workflows for items at the SCF

Updating SCF items (barcodes, bibliographic records, etc.)

As detailed in the Metadata Infrastructure in the SCF IZ page, every item that resides in the WRLC's Shared Collections Facility (SCF) has two records in our Network Zone; one copy that resides in the owning Institution's IZ, and a second copy that resides in the SCF IZ.

Because of this, certain updates made to an SCF item in the owning Institution Zone are NOT automatically pushed out to the SCF catalog. Because of this discrepancy, the WRLC needs to be notified if certain changes are made to an SCF item.

 

Barcode

If the barcode of an SCF item is changed, please open a WRLC Service Desk ticket (servicedesk@wrlc.org) so that the SCF copy can be updated.

Without this necessary step, the SCF publishing app will create a separate item record in the SCF IZ containing the new barcode. This will result in two item records in the SCF IZ for the same item ; one with the old barcode, and one with the new barcode. WRLC must be notified of a barcode change in order to prevent this.

 

Bibliographic Record

If an SCF item is moved to a different bibliographic record, please open a WRLC Service Desk ticket (servicedesk@wrlc.org) so that the SCF copy can be updated.

Without this necessary step, requests for this item may fail. WRLC must be notified of a bib record change in order to prevent this. Please keep in mind, this policy applies to both items attached to an NZ record AND items attached to an IZ-only record. 

Remote Storage App

How the SCF remote storage app works for accessions, requests, loans, etc.

Remote Storage App

Accessions in the Remote Storage App

Accessions Workflow

The following accessions workflow is configured for all WRLC Institution Zones except UDC Law and CU Law.

scf-app-accession-workflow.PNG

  1. Update item in owning IZ (location is changed from a regular location to an SCF location)
  2. Publishing job runs in owning IZ (once a day, usually around midnight); the job sends a file of item information from an Alma set to a specific SFTP folder
  3. The Job Finish Webhook Integration Profile in the owning IZ sends out a webhook when the publishing job finishes.
  4. The Remote Storage app recognizes the webhook from the list of approved job webhooks in the configuration file. The app then opens and processes the file from the SFTP folder.
  5. The app first checks if the barcode exists in the SCF IZ. If it doesn’t, it looks for a matching bibliographic record, then a holdings record (in that order). If found, those records are used; if not, they are created in the same order. Details on the metadata added to the bibliographic and holdings records are provided in the Metadata changes in the SCF IZ section below 
  6. Item is created. Details on the metadata added to the item records are provided in the Metadata changes in the SCF IZ section below 
Assumptions made in the Accessions Workflow

Set for SCF Data Prep in Alma

Every participating WRLC Institution Zone has a Physical Items set that searches for all item records with either a temporary or permanent location at the Shared Collections Facility. Each set has an Internal Note stating DO NOT DELETE.

This set is used for the SCF Data Preparation Profile. 

SCF Data Preparation Publishing Profile in Alma

A publishing profile (called the "SCF Data Preparation Profile") in the owning IZ exports a MARC XML file containing new, deleted, and updated items found in a specific Alma set ("Set for SCF Data Prep"). 

The XML file names are :

Institution abbreviation + iz2scf + yyyymmdd + two-digit number + Alma Process ID + new or delete 

ex. au_iz2scf_2025060308_18906688690004102_new

The job is run daily, usually at night or early in the morning

A webhook is sent by the SCF Job Finish Webhook Integration Profile when the publishing job finishes. The job ID is listed in the config file for the app, letting the app know that this is a job that it should look out for. When the app recognizes the job id for the publishing profile, the app examines the file of items published and goes to work creating or updating the items in the SCF IZ.

Do not edit this profile without communicating with WRLC Central staff. If you save edits, it will change the Job ID, which is what the Remote Storage App looks for in the Job Finish Webhook. Editing this profile requires finding the new Job ID, and then updating the configuration JSON file with the new information.


SFTP for SCF App 

The S/FTP Definition configured in Alma is named "SFTP for SCF App". This is the destination where the publishing profile exports the daily item information file and where the Requests file is also sent.

In this Integration Profile, the specified subdirectory is "Alma" (or "AlmaRSA-PSB" for sandbox environments).

Each Publishing Profile for accessions uses a subdirectory in the format:
[Institution Code]/items

ex.01WRLC_AMU/items

After each sandbox refresh, the sandbox environment must be updated with the correct subdirectory.

Additionally, the SFTP server information in the app configuration file must exactly match the details specified in the S/FTP Definition.

Webhook Integration Profiles

There are two Webhook integration profiles important to the SCF accessions workflow. 

  1. SCF Job Finish Webhook Integration Profile in the owning Institution Zone

    1. Sends out a webhook for every job that finishes running in the Institution Zone. The SCF app searches for the job id (publishing_job_id) in the conf.json file and the institution is selected according to it.

  2. SCF Loans Webhooks Integration Profile in the SCF IZ

    1. Sends out a webhook for requests and loans in the SCF IZ. The SCFapp changes the status of the owning institution’s item record based on the changes made in the SCF IZ. For more information, see the Loans page and the Requests page.

You can see a list of Webhook logs in Alma (Ellipsis button, View Log), and can also see the publishing job id in the Webhooks log for the publishing profile. Webhook secret in integration profile should be the same as that listed in the config file. 

Loans for published items

When an item is published to the SCF IZ, a loan is automatically created for the item. It is loaned to a dummy patron account with a patron type of Library pickup locations.

The name of the account will often be Deliver to : [IZ abbreviation], for example Deliver to: CU.

The Primary ID of these user profiles is the IZ code, followed by a dash (no spaces), and then the code for the library, for example 01WRLC_GWA-SCRC.

The Primary ID for the dummy accounts cannot be edited, they are integral to the remote storage app code.

When an item is scanned in at the SCF IZ for initial processing, the remote storage app sees the Remove Loan webhook sent from the SCF IZ by the SCF Loans Webhooks Integration Profile, and the app removes any in transit status’s on the item in the owning IZ. 

Metadata changes in the SCF IZ

Bib records

The bibliographic records not linked to the NZ will be given an 035 field with the prefix of the IZ code (ex. 01WRLC_AMU) followed by the owning IZ’s MMS ID

Holdings records

A new holdings record will be created for the item in the SCF IZ if there isn't a pre existing holdings record attached to the bib with the same location code.

Item records

Remote Storage App

Requests in the Remote Storage App

Requests Workflow

scf-app-request-workflow.PNG

  1. Shared Collections Facility Integration Profile runs and places file of requests in the SCF SFTP folder.
  2. Remote Storage app searches for the item in the SCF IZ using the barcode; if found, an item-level request is created
  3. If a barcode is not a part of the request metadata (because the request is for an article), then the app searches for the title using the NZ MMS Id; if found, a title-level request is created

Assumptions made in the Requests Workflow
  1. XML associates all requests to a specific item
  2. Requests webhook does not send webhook for every change
  3. XML file filters out all requests not related to remote storage locations
  4. Requests once communicated to the SCF IZ cannot be changed
  5.  No tracking is needed of the remote storgae items
  6. The request type is a Hold
  7. The pickup locaiton type is a personal delivery
  8. All other fields can be copied from the original request
  9. The patron/user for the hold request needs to be taken from the config file where each institution/library has a Patron ID
  10. Item n the SCF IZ must have provenance of the calling institution

Integration Profile

The Integration Profile used for Requests is configured in every participating Institution Zone in the WRLC Network

  1. Shared Collections Facility Integration Profile :

    1. This is a Remote Storage type integration profile. It runs twice daily (at noon and at midnight) and sends a file of all requests made to items with a Remote Storage location to an SFTP server for the remote storage app to process. The app searches for the job id (publishing_job_id) in the conf.json file.

Do not edit this profile without communicating with WRLC Central staff. If you save edits, it will change the Job ID, which is what the Remote Storage App looks for in the Job Finish Webhook. Editing this profile requires finding the new Job ID, and then updating the configuration JSON file with the new information.

SFTP for SCF App

The S/FTP Definition configured in Alma is named "SFTP for SCF App". This is the destination where the publishing profile exports the daily item information file and where the Requests file is also sent.

In this Integration Profile, the specified subdirectory is "Alma" (or "AlmaRSA-PSB" for sandbox environments).

Each Integration Profile for requests uses a subdirectory in the format:
[Institution Code]/requests

ex.01WRLC_AMU/requests

After each sandbox refresh, the sandbox environment must be updated with the correct subdirectory.

Additionally, the SFTP server information in the app configuration file must exactly match the details specified in the S/FTP Definition.

Requests Process

When a patron makes a request for an item at the SCF, the item is given a status of Waiting for Remote Storage in the owning Institution’s IZ. The item in the owning IZ also has a process type of Requested. 

If the requester is from a different Institution than the Institution that owns the item, the request will appear under both the Monitor Requests & Item Processes page (without a workflow assigned) and the Borrowing Requests page in the IZ of the requester, with a status of Request sent to Partner; the partner that is listed is the owning IZ, not the SCF IZ. 

The Shared Collections Facility Integration Profile in each owning Institution Zone runs twice daily (once at noon, and again at midnight), and transfers requests to the SCF IZ. In the SCF IZ, the item is given a status of Pick from shelf; it is “requested” by the patron account associated with the pickup location.

Once the request has successfully transferred to the SCF IZ, the status of the item in the owning IZ is changed to Request Communicated to Storage, until the item is scanned at the requester’s IZ; then the item is placed on their Hold Shelf. The item record will have a process type of Hold Shelf, even if the Hold Shelf is at another Institution other than the owning Institution.

When the item is scanned in the SCF IZ (after being picked up from the shelf by the SCF specialists), it is automatically loaned to the patron account associated with the requesting library (Deliver To : [Pickup IZ]). This is because all of the Library pickup patron accounts in the SCF IZ are governed by the Library Delivery fulfillment rule that is configured under the Limited Request fulfillment unit for Library pickup patron accounts. The SCF copy of the item remains on loan until the item is returned to the SCF.

When item is scanned in at the non-SCF Institution Zone, the item is given a status of Transit for Reshelving.

When the returned item is scanned in at the SCF, not only is the Loan in the SCF IZ removed, but the In Transit status in the owning IZ is also removed due to the webhook sent via the SCF Loans Webhooks Profile Integration Profile, and processing done by the SCF app. For more information on Loans and the remote storage app, see the Loans page.

Remote Storage App

Remote Storage App Configuration

Configuration Files

There are two configuration files, one for the live production environment (opt/tomcat/webapps/AlmaRemoteStorageApp/WEB-INF/classes/conf.json), and one for the sandbox (opt/tomcat/webapps/AlmaRSA-PSB/WEB-INF/classes/conf.json).

This JSON file gives the remote storage app important information regarding institution, library, and location codes, as well as API keys, publishing profile IDs, etc.

What exactly is found in the configuration file?

If any changes are made to anything listed above, the configuration file must be updated. Changes made to this file requires a reloading of the Remote Storage App

Logs

Logs for both the production and sandbox environment are in opt/tomcat/logs

The file name denotes the type of log file; logs with a file name beginning with PSB-application are for the sandbox, and logs with a file name beginning with application are for the production environment. 

Log files starts at 6:30 am of the day listed in the name of the log, and ends at 6:30 am of the next day

The log will have thread numbers - each request/action is given a specific thread number. if there are many requests at once, the thread numbers are an easy way to keep track of one request

SCFTP for SCF App S/FTP Definition

The S/FTP Definition configured in Alma is named "SFTP for SCF App". This is the destination where the publishing profile exports the daily item information file and where the Requests file is also sent.

The specified subdirectory is "Alma" (or "AlmaRSA-PSB" for sandbox environments).

The SCF Data Preparation Publishing Profile for accessions uses a subdirectory in the format:
[Institution Code]/items

ex.01WRLC_AMU/items

The Shared Collections Facility Integration Profile for requests uses a subdirectory in the format:
[Institution Code]/requests

ex.01WRLC_AMU/requests

After each sandbox refresh, the sandbox environment must be updated with the correct subdirectory.

Integration Profiles

There are three Integration Profiles used for the Remote Storage App.

The two listed below are in each participating Institution's IZ

Do not edit this profile without communicating with WRLC Central staff. If you save edits, it will change the Job ID, which is what the Remote Storage App looks for in the Job Finish Webhook. Editing this profile requires finding the new Job ID, and then updating the configuration JSON file with the new information.

The profile listed below is in the SCF IZ

Set for SCF Item records

Every participating WRLC Institution Zone has a Physical Items set that searches for all item records with either a temporary or permanent location at the Shared Collections Facility. Each set has an Internal Note stating DO NOT DELETE.

This set is used for the SCF Data Preparation Profile. 

Publishing Profile

A publishing profile (called the "SCF Data Preparation Profile") in the owning IZ exports a MARC XML file containing new, deleted, and updated items found in a specific Alma set ("Set for SCF Data Prep"). 

The XML file names are :

Institution abbreviation + iz2scf + yyyymmdd + two-digit number + Alma Process ID + new or delete 

ex. au_iz2scf_2025060308_18906688690004102_new

The job is run daily, usually at night or early in the morning

A webhook is sent by the SCF Job Finish Webhook Integration Profile when the publishing job finishes. The job ID is listed in the config file for the app, letting the app know that this is a job that it should look out for. When the app recognizes the job id for the publishing profile, the app examines the file of items published and goes to work creating or updating the items in the SCF IZ.

Do not edit this profile without communicating with WRLC Central staff. If you save edits, it will change the Job ID, which is what the Remote Storage App looks for in the Job Finish Webhook. Editing this profile requires finding the new Job ID, and then updating the configuration JSON file with the new information.

Remote Storage App

Loans in the Remote Storage App

Loans Workflow

Changes in Loan status made in the SCF IZ are directly communicated to the owning IZ through a Webhook Integration Profile configured in the SCF IZ.

Changes in Loan status made in the owning IZ are NOT communicated to the SCF IZ. The process only runs one way : from SCF IZ to owning IZ.

scf-app-loan-workflow.PNG

  1. Item scanned in SCF IZ, loan is closed
  2. Webhook for the Loan Returned action is sent out
  3. If the user_id value in the webhook equals the Primary ID of the dummy library account in the SCF IZ. If the institution code and library code in the Primary ID exist in the configuration file, the remote storage app will process the return
  4. The remote storage app finds the item in the owning IZ (based on the information in the Primary ID of the patron account, the app knows which institution needs to be called), and returns the item

Webhook Integration Profile

The webhook profile used for Loans is configured in the SCF IZ. 

  1. SCF Loans Webhooks Integration Profile in the SCF IZ 

    1. Sends out a webhook for requests and loans originating in the SCF IZ. The remote storage app changes the status of the owning institution’s item record based on the changes made in the SCF IZ. 

For the Webhook profiles, you can see list of Webhook logs in Alma (Ellipsis, View Log), and can also see the publishing job id in the Webhooks log for the publishing profile. Webhook secret in integration profile the same as that listed in the config file. 

Loans for recently accessioned items

When an item is published to the SCF IZ, a loan is automatically created for the item. It is loaned to a dummy patron account with a patron type of Library pickup locations.

The name of the account will often be Deliver to : [IZ abbreviation], for example Deliver to: CU.

The Primary ID of these user profiles is the IZ code, followed by a dash (no spaces), and then the code for the library, for example 01WRLC_GWA-SCRC.

The Primary ID for the dummy accounts cannot be edited, they are integral to the remote storage app code.

When an item is scanned in at the SCF IZ for initial processing, the remote storage app sees the Remove Loan webhook sent from the SCF IZ by the SCF Loans Webhooks Integration Profile, and the app removes any in transit status’s on the item in the owning IZ. 

Loans for requested SCF items

Requests made for SCF items are transferred to the SCF IZ by the remote storage app (for a full description of this workflow, please see the Requests page). 

In the transfer process, the SCF copy of the item is requested in the SCF IZ by the dummy patron account associated with each library in the WRLC. The account used takes into consideration both the Primo/ Alma instance where the request originated, and the pickup location of the requested item.

For example, if an item was requested from GW's IZ for pickup at Gelman, the item in the SCF IZ would be requested by the dummy library account with the code 01WRLC_GWA-gelman

When the requested item is scanned at the SCF IZ, the item is automatically loaned to the dummy library account, and the loan webhooks are sent to the remote storage app via the SCF Loans Webhooks Profile in the SCF IZ.

Remote Storage App

How to find Job IDs for the Remote Storage App

The SCF Job Finish Webhook Integration Profile sends out a webhook every time a job finishes running in the Institution Zone. The Remote Storage App receives all of the webhooks and specifically looks for the webhooks with a Job ID that is listed in the configuration JSON file. 

The specific Job IDs the app is looking for are for the Shared Collections Facility Integration Profile (exports a file of requests to an SCF SFTP folder) and for the SCF Data Preparation Publishing Profile (exports a file of new SCF items).

It is important to keep these Job IDs accurate and up-to-date; Request and Accession workflows are reliant on them. 

If either the Integration Profile or the Publishing Profile are edited in Alma, the Job ID changes. It is essential to communicate with WRLC Staff before editing any of these two profiles.

Follow the workflows detailed below to find the correct Job ID used in the Remote Storage App's configuration file.

Publishing Profile Job ID

https://api-na.hosted.exlibrisgroup.com/almaws/v1/conf/jobs?
+ apikey=[insert API key here] 
+ &profile_id=[insert Profile ID here]

EXAMPLE:

https://api-na.hosted.exlibrisgroup.com/almaws/v1/conf/jobs?apikey=l8xx3ddc6c7128a144e8aa27a8faf383d199&profile_id=7750084200004102

For more information, see the Google spreadsheet Publishing Profile info

Request Integration Profile Job ID

https://api-na.hosted.exlibrisgroup.com/almaws/v1/conf/integration-profiles?
+ apikey=[insert API key here] 
+ &type=REMOTE_STORAGE

EXAMPLE:

https://api-na.hosted.exlibrisgroup.com/almaws/v1/conf/integration-profiles?apikey=l8xxdd61599bea484b8d8b7d84a722da788e&type=REMOTE_STORAGE

https://api-na.hosted.exlibrisgroup.com/almaws/v1/conf/jobs?
+ apikey=[insert API key here] 
+ &profile_id=[insert Profile ID here]

EXAMPLE:

https://api-na.hosted.exlibrisgroup.com/almaws/v1/conf/jobs?apikey=l8xxdd61599bea484b8d8b7d84a722da788e&profile_id=10385500680004107

Metadata Infrastructure in the SCF IZ

Every item that resides in the WRLC's Shared Collections Facility (SCF) has two records in our Network Zone; a copy that resides in the owning Institution's IZ, and a second copy that resides in the SCF IZ. The second SCF copy is primarily used for shelf and workflow control at the SCF. Because of this, the SCF copy is suppressed from discovery in the patron-facing catalog (Primo). The record that patrons view in Primo is the record in the owning Institution's IZ.

When a patron requests an item located at the SCF, the request is attached to the owning institution's copy of the item record (the unsuppressed record). Then the SCF publishing app automatically transfers that request to the SCF copy of the item record (the suppressed record).  

Bibliographic Records

If the owning Institution's item record is attached to a Network Zone bibliographic record, the SCF copy of the item record will also be attached to the same NZ bib record. The SCF holding and item records are suppressed from discovery in Primo.

infra-1.PNG

If the owning Institution's item record is NOT attached to a Network Zone bibliographic record (if it is attached to an IZ-only record), then the SCF copy of the item record will be attached to a suppressed copy of the IZ-only bibliographic record. 

infra-3.PNG

The SCF copy of the bib record will have the MMS Id of the owning Institution's record in the 035 field; the inclusion of the MMS Id allows for requests of non-NZ linked items to occur.

infra-2.PNG

Any updates made to the owning Institution's bib record will NOT be transferred to the SCF copy of the bib record.

If an SCF item is moved to a different bib record, please open a WRLC Service Desk ticket (servicedesk@wrlc.org) so that the SCF copy can be updated. Without this necessary step, requests for this item may fail. For more policies like this, see the Updating SCF items (barcodes, bibliographic records, etc.) page.

Holding Records

All SCF holding record copies are suppressed from Discovery.

Any updates made to the owning Institution's holding record will NOT be transferred to the SCF copy of the holding record.

Item Records

The SCF copy of the item record has a few key differences from the original owning Institution item record.

The barcode will have an 'X' appended to the end. In addition, a provenance code is added to keep track of which Institution owns the item.

infra-4.PNG

Unlike the bib and holding records, updates made in the following fields to the owning Institution's copy of the item record will be transferred to the SCF copy:

If the barcode of an SCF item is changed, please open a WRLC Service Desk ticket (servicedesk@wrlc.org) so that the SCF copy can be updated. For more policies like this, see the Updating SCF items (barcodes, bibliographic records, etc.) page.

Item Locations

The permanent or temporary WRLC location in the owning Institution IZ is transferred to the SCF IZ as a permanent location.

If the item location in the owning IZ has one of the following location codes, the item in the SCF IZ will have the exact same location.

auba
brl box
da per
da pernc
dcpl box
gal arch
gtda
gtlaw
gtmed
gtwn
gtwn box
gw cq
gw nea
gw nsas
mu arch
mu av
udc jazz
wral
wr aumc
wr aumr
wrlc
wrlc almon
wrlc alper
wrlc cgrc
wrlc cunc
wrlccunc
wrlc danc
wrlc dism
wrlc disp
wrlc gtdp
wrlc gtkib
wrlc gtkip
wrlc gtmo
wrlc gtnc
wrlc gtsp
wrlc gtspe
wrlc gtthe
wrlc gtv
wrlc gtvc
wrlc hida
wrlc himm
wrlc micro
wrlcscfrs
wrlc sgrc
wrlc_shrd
wrlc shrm
wrlc shrp
wrlc snsa
wrlc stnc
wrlcstndup
wrlcstnret
wrlcstodup
wrlc stor
wrlcstoret
wrlcstrret
wrlc stru
wrlc_stru
wrlc wood
wrlc woodc

Any SCF location in the owning IZ that is NOT listed above will be given the default location of wrlc stor in the SCF IZ.

Primo VE

Although there are two record copies for each item, the patron only sees one item in Primo because all SCF records are suppressed. 

For example, this bib record has both American University and SCF holdings attached.

infra-1.PNG

In Primo, only the American University holdings are visible to the patron.

infra-5.PNG

Patron Accounts for Libraries

When SCF items are requested and sent to neighboring libraries, they are checked out to patron accounts in the SCF IZ that represent each library pickup location.  

These user accounts have the following characteristics

scf-app-user-profiles.PNG

SCF Physical Locations

UNDER CONSTRUCTION

American University

Location Code in AU Institution Zone Location Description in AU Institution Zone Temporary or Permanent Location in AU Institution Zone Library Name in AU Institution Zone Equivalent Location in SCF IZ*
auscfgen Shared Collections Facility - General Most are Permanent (a handful are Temporary) American University Library wrlc stor
auscfmus Shared Collections Facility - Music Permanent Music Library (American University) wrlc stor
auscfspec Shared Collections Facility - Special Permanent University Archives and Special Collections (American University) wrlc stor
wrlc stnc WRLC Storage Non-Circulating Temporary American University Library wrlc stnc
wrlc stor WRLC Storage Circulating Temporary American University Library wrlc stor
wrlc stru WRLC Storage Restricted Temporary American University Library wrlc stru
wrlcscfrs WRLC SCF Remote Storage Temporary American University Library wrlc stor

American University College of Law

Location Code in AU Law Institution Zone Location Description in AU Law Institution Zone Temporary or Permanent Location in AU Law Institution Zone Equivalent Location in SCF IZ*
WRLC WRLC Offsite Storage Permanent wrlc stor

Catholic University of America

Location Code in CU Institution Zone Location Description in CU Institution Zone Temporary or Permanent Location in CU Institution Zone Library Name in CU Institution Zone Equivalent Location in SCF IZ*
wrlc stor WRLC Shared Collections Facility (wrlc stor) Temporary AND Permanent Mullen Library wrlc stor
wrlc stnc WRLC Shared Collections Facility (wrlc stnc) Temporary Mullen Library wrlc stnc
wrlc shrp WRLC Shared Collections Facility (wrlc shrp) Temporary Mullen Library wrlc shrp
wrlc stru WRLC Shared Collections Facility (wrlc stru) Most are Temporary, a handful are Permanent Mullen Library wrlc stru
wrlc disp WRLC Shared Collections Facility (wrlc disp) Temporary Mullen Library wrlc disp
wrlc shrm WRLC Shared Collections Facility (wrlc shrm) Temporary Mullen Library wrlc shrm
wrlc dism WRLC Shared Collections Facility (wrlc dism) Temporary Mullen Library wrlc dism
wr aumc WRLC Shared Collections Facility Temporary Mullen Library wr aumc

Gallaudet University

Location Code in GA Institution Zone Location Description in GA Institution Zone Temporary or Permanent Location in GA Institution Zone Library Name in GA Institution Zone Equivalent Location in SCF IZ*
wrlc stor WRLC Shared Collections Facility (wrlc stor) Permanent AND Temporary Gallaudet University Library wrlc stor
wrlc stru WRLC Shared Collections Facility (wrlc stru) Permanent AND Temporary Gallaudet University Library wrlc stru
wrlc dflm WRLC Shared Collections Facility (wrlc stor) Film Most are Temporary, some are Permanent Gallaudet University Library wrlc stor
wrlc dfbk WRLC Shared Collections Facility (wrlc stor) Deaf Books Most are Temporary, some are Permanent Gallaudet University Library wrlc stor
WRLCDIG WRLC Digital Collections Permanent Gallaudet University Library wrlc stor
wrlcstoret WRLC Shared Collections Facility (wrlcstoret) Temporary Gallaudet University Library wrlcstoret
wrlc stnc WRLC Shared Collections Facility (wrlc stnc) Temporary Gallaudet University Library wrlc stnc
wrlc shrp WRLC Shared Collections Facility (wrlc shrp) Temporary Gallaudet University Library wrlc shrp
wrlc shrm WRLC Shared Collections Facility (wrlc shrm) Temporary Gallaudet University Library wrlc shrm
wrlc resv WRLC Shared Collections Facility (wrlc stor) Reserves Temporary Gallaudet University Library wrlc stor
wrlc dism WRLC Shared Collections Facility (wrlc dism) Temporary Gallaudet University Library wrlc dism
wrlc dfmd WRLC Shared Collections Facility (wrlc stor) Deaf Media Temporary Gallaudet University Library wrlc stor
wrlc cstk WRLC Shared Collections Facility (wrlc stor) Closed Stacks Temporary Gallaudet University Library wrlc stor

George Mason University

Location Code in GM Institution Zone Location Description in GM Institution Zone Temporary or Permanent Location in GM Institution Zone Library Name in GM Institution Zone Equivalent Location in SCF IZ*
wrlc_shrd WRLC Shared Collections Facility Most are Permanent, some are Temporary Fenwick Library wrlc stor
wrlc_rstcd WRLC Center - Restricted Use Most are Permanent, some are Temporary Fenwick Library wrlc stor
wrlc_cntr WRLC Center Permanent Fenwick Library wrlc stor

 

George Washington University

Location Code in GW Institution Zone Location Description in GW Institution Zone Temporary or Permanent Location in GW Institution Zone Library Name in GW Institution Zone Equivalent Location in SCF IZ*
wrlc_stor WRLC Storage Circulating Most are Permanent, handful are Temporary Gelman Library wrlc stor
wrlc_stnc WRLC Storage Non-Circulating Permanent Gelman Library wrlc stnc
wrlc sgrc WRLC Storage Restricted - GRC Most are Permanent, handful are Temporary Gelman Library wrlc sgrc
wrlc cgrc WRLC Storage Circulating - GRC Permanent Gelman Library wrlc cgrc
wrlc stru WRLC Storage Restricted Permanent Gelman Library wrlc stru
wrlc shrp WRLC Shared periodical Permanent Gelman Library wrlc shrp
wrlc disp WRLC Shared Per. Discard Permanent Gelman Library wrlc disp
wrlc dism WRLC Shared Mono. Discard Permanent Gelman Library wrlc dism
wrlc snsa WRLC Restricted National Security Archive Permanent Gelman Library wrlc snsa
wrlc_stru WRLC Storage Restricted Permanent Special Collections Research Center wrlc_stru

Georgetown University

Location Code in GT Institution Zone Location Description in GT Institution Zone Temporary or Permanent Location in GT Institution Zone Library Name in GT Institution Zone Equivalent Location in SCF IZ*
wrlc_stor WRLC Storage Circulating Most are Permanent, handful are Temporary Gelman Library wrlc stor

Howard University

 

Marymount University

Location Code in MU Institution Zone Location Description in MU Institution Zone Temporary or Permanent Location in MU Institution Zone Equivalent Location in SCF IZ*
wrlc stor WRLC Storage Circulating Most are Temporary (a handful are Permanent) wrlc stor
wrlc stnc WRLC Storage Non-Circulating Temporary wrlc stnc
wrlc shrp WRLC Shared Periodical Temporary wrlc shrp
wrlc stru WRLC Storage Restricted Temporary wrlc stru

University of the District of Columbia

Location Code in DC Institution Zone Location Description in DC Institution Zone Temporary or Permanent Location in DC Institution Zone Equivalent Location in SCF IZ*
wrlc stor WRLC Shared Collections Facility Temporary wrlc stor
wrlc stnc WRLC Shared Collections Facility (non-circulating) Temporary wrlc stnc

* Items that do not have a matching location in the SCF Institution Zone are given the default location of wrlc stor