WRLC HQ

Documents and Information for staff at WRLC Headquarters

Handle Server

The WRLC handle server prefix is 1961. 

The prefix is renewed each year in January.  

The contact for renewal is hdladmin@cnri.reston.va.us.  (Most recently this was Christy Short.)

The last renewal in January 2024 was $50.00.

TESTING:

Test URLs
https://hdl.handle.net (enter handle like 1961/muislandora:871 )
https://hdl.wrlc.org/1961/14672
https://hdl.handle.net/1961/muislandora:876

Test command
$ mysql -u root -p -e "show databases;"

Trouble shooting:

If the handle server doesn't restart on reboot, check the lock file. 

If lock file was not removed on shutdown/crash, it will need to be removed before the handle server can restart.

Location:  /opt/handle/svr1/txns/lock

-rw-r--r-- 1 root     www-data       4 Mar 25 09:50 lock
kilduff@crhandle:/opt/handle/svr1/txns$

Remove lock file.

 

 

Note - migrated to cloud 4/8/2024

Letters managed in the NZ for Physical Item Requests

There are two letters managed in the network zone for our partners.

Letters managed in the NZ for Physical Item Requests

Pull Slip (Ful Resource Request Slip Letter)

The Pull Slip is managed for our partners to provide consistency for the displayed location codes.  These codes are use to direct the physical items to the patron's selected pickup location.

Notes: 

Letters managed in the NZ for Physical Item Requests

On Hold Shelf Letter

The On Hold Shelf Letter is managed in the Network Zone so that specific library instructions can be provided to the patron on when and how material can be picked up.  The original format of the letter only provided instructions from the owning library.  These instruction were not specific to the pickup location that the patron selected.

Local Authority Headings Workflows

The following are the workflows used by the WRLC Consortial Network Zone Manager to oversee, edit, and update the local authority records in the WRLC Network Zone environment.

Replacement Headings

  1. Create local authority record. Save as a Local LCSH authority record in the NZ (do not import records, the headings will not link to an imported authority record unless that authority record is opened and saved in the Metadata Editor).

  2. Create set of NZ records containing original LCSH

  3. Run the “Unlink Bib Records from Authority Records” job on the set. This is done so that the headings will be unlinked from the LCSH authority record.

  4. After 24 hours, check the results of the Preferred Term Correction job via the Authority Control Task List. All headings should have been linked to the local authority record and flipped.

  5. Follow instructions for CZ records (see appropriate section below)

  6. Follow instructions for changing incorrect URIs for local flipped headings (see appropriate section below).

Supplemental Headings

  1. Create local authority record. Save as a Local WRLC authority record in the NZ

  2. Add normalization rules to the WRLC transform 650 to 650 subf 2 local subf 5 CAO normalization rule

  3. Create set of NZ records containing original LCSH

  4. Run normalization rule on the set

  5. After 24 hours, check the results of the set to make sure the local headings are linked to their local authority records.

  6. Follow instructions for CZ records (see appropriate section below).

Community Zone Local Headings

  1. Write normalization rule with title “WRLC CZ [New Heading] Local LCSH”

  2. Create a logical set of all CZ records with the original LCSH

  3. Run the normalization rule on the set. Save this as a recurring job (to run every 2 months on the 15th)

  4. Consortial NZ Manager will review results of scheduled jobs every 2 months 

Change URIs for Replacement Headings

  1. Add new replacement headings to the normalization rule "WRLC Delete incorrect URIs for flipped Local Headings“
  2. Edit the logical query for the "WRLC Local Replacement Subject Headings" set and save

  3. Delete any previously configured recurring jobs that removed URIs for replacement headings
  4. Run the normalization rule “WRLC Delete incorrect URIs for flipped Local Headings“ on filtered set to delete incorrect URIs. Save this as a recurring job (to run every 2 months on the 16th). 

  5. Consortial NZ Manager will review results of scheduled job every 2 months

Documentation

WRLC Local Subject Headings tracking spreadsheet : Replacement and Supplemental Heading Tracking

Testing document : Local Authority Records

Sandbox Configuration after refresh

The Premium Sandboxes are refreshed twice a year.  This copies the latest configurations from production Alma into the PSB Network Zone and the 3 PSB IZs.  Several configuration changes need to be made so that the AFN will work correctly.

Sandbox Configuration after refresh

Update Rota Template Members

After the refresh, the Rota Template has the full compliment of partners for Consortium Book Borrowing (CLS-Physical) template.  Members that do not have an IZ Sandbox need to be removed for the Rota to work properly.  Currently, the members should be AU, DC, and GW.  Remove the others that do not have a PSB.

In the PSB Network Zone:

Fulfillment  -->  Resource Sharing  -->  Rota Templates  -->  Edit Consortium Book Borrowing (CLS-Physical)

Screen Shot 2024-02-13 at 4.32.26 PM.png

Sandbox Configuration after refresh

Update the Resource Sharing Partners for the PSB

The Resource Sharing partners that are template members will need to have their URL parameter updated.

Fulfillment  -->  Resource Sharing  -->  Partners  

Screen Shot 2024-02-13 at 4.42.52 PM.png

Screen Shot 2024-02-13 at 4.45.38 PM.png

 Currently, the URLs are:

Once both the Rota Template members and the Resource Sharing Partner URL are updated you need to run the "Distribute Resource Sharing Network Configuration" job from the PSB Network Zone.  This job distributes the changes that you just made to the template partner IZs

Fulfillment  -->  Advanced Tools - General  -->  Distribute Resource Sharing Network Configuration

Screen Shot 2024-02-13 at 4.56.16 PM.png


Sandbox Configuration after refresh

Update sftp server directory for PSB use

The Premium Sandbox uses the sftp.wrlc.org server to post files from the running of the "Send Request to Remote Storage" jobs.  It is also used for posting files from the running of the publishing jobs.  

Follow the instructions below for all of the Institution Zones in the sandbox:

Configuration --> General --> External Systems --> Allowed S/FTP connections 

Add the IP sftp.wrlc.org to the list of allowed connections in the sandbox

Capture.PNG

Configuration --> General --> External Systems --> S/FTP definitions 

Screen Shot 2024-09-03 at 10.06.57 AM.png

Find the "SFTP for SCF App" connection.

Screen Shot 2024-09-03 at 10.08.07 AM.png

Select edit.

Screen Shot 2024-09-03 at 9.55.52 AM.png

Locate the Sub-directrory used on the sftp.wrlc.org server.

Screen Shot 2024-09-03 at 9.56.33 AM.png

Change the Sub-directory to "AlmaRSA-PSB".  Save. 

This is the directory the Sandbox should be using.   You can test if the PSB can connect using the TestFTP button on the upper right of the screen.

For more info on these configurations, see Salesforce case #07222190

Sandbox Configuration after refresh

Update Webhook profiles

In the non-SCF Institution Zones, the SCF Job Finish Webhook profile needs to be update with the Webhook listener URL and activated so that both publishing and requesting functions of the SCFapp work in the PSB.

In the SCF sandbox, the SCF Loans Webhooks profile needs to be updated and activated with the same URL.

Configuration --> General --> External Systems --> Integration Profiles --> Webhook profile

Screen Shot 2024-09-10 at 9.07.20 AM.png

Select Edit.

Screen Shot 2024-09-10 at 8.50.16 AM.png

Add the Webhook listener URL :

https://wrlc-alma-remote-storage.azurewebsites.net/webhook

Activate and Save.

You will see confirmation of activation if the URL is correct an the server responds.

For more info on these configurations, see Salesforce case #07222190

Due Dates

Due Dates

Update the Faculty Due Date

As with each IZ that participates in consortial lending needs to maintain the fixed due date on their calendars for patrons in "wrlc user" user group with the "WRLC Faculty" job category, so does the SCF IZ.  This is done 3 time a year so that Faculty can have loans that last the semester.  The dates are changed about 6 weeks prior to the expiration of the current due date.

The designated due dates are January 31st for the Fall semester, May 31st for the Spring semester, and September 30th for the Summer sessions.

The dates are changed on the following schedule:



Due Dates

Bulk Due Date change for pseudo-patrons

Since there is no method to automatically renew items loaned to the scfapp pseudo-patrons, this must be done manually.

This should be done once the "Faculty due date" has been updated in the SCF.  (This is done 3 times in a year.)

Procedure to Update the item due dates:

SCF Requests

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

SCF Requests

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

SCF Requests

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.

 

SCF Requests

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.

Troubleshooting Alma/Primo Service Desk tickets

Helpful information on how to troubleshoot various types of Alma/Primo related WRLC Service Desk tickets

Troubleshooting Alma/Primo Service Desk tickets

Troubleshooting Proxy Issues

Now that WRLC no longer oversees proxy servers for our institutions, the main goal in answering any proxy related Service Desk tickets is to see where the real issue lies. IF the problem is with Alma configuration, we can edit their Alma configs for them. IF the problem isn't with Alma, the institution will have to contact either their proxy service or the vendor for a resolution.

In order to see where the problem resides, it is helpful to get a sense of the scope of the issue.

Is it an issue with access to all e-resources in their catalog for all of their patrons?

If so, the issue most likely resides with their proxy provider and the institution will need to contact them for assistance.

Is the issue limited to a specific electronic collection or vendor?

Is the issue only with a specific ebook or ejournal?

Affiliate Library Configuration

1. Create user group

aff_lib_config1.PNG

 

2. Apply user record group to a specific type

aff_lib_config2.PNG

 

3. Associate library location with Fulfillment Unit

 

4. Associate user group with Fulfillment Unit

aff_lib_config3.PNG

aff_lib_config4.PNG

aff_lib_config5.PNG

5. Create a restricted search group for Primo VE

aff_lib_config6.PNG

aff_lib_config7.PNG

aff_lib_config8.PNG

aff_lib_config9.PNG

 
6. Create a custom local data search scope

aff_lib_config10.PNG

 

7. Create a search profile
 
8. Create a Primo VE view for affiliate library users

aff_lib_config11.PNG

 

9. Create user profile(s)

aff_lib_config12.PNG

 

10. Update letter configuration for pull slip
<!--   Internal Alma request from affiliate institution [Insert affiliate library here}   -->
<xsl:when test="(notification_data/user_for_printing/user_group='[User Group Code]')">
<font size ="40px;">[Affiliate Library Name]</font>
</xsl:when>