Berenson Export to Remote Storage

Exporting physical item requests to BER FTP location

Part I: Physical item request config:

1. Configure New Remote Storage:
   1. Alma >General > Locations > Remote Storage: Add new remote storage
      
2. Add new S/FTP connection type
   1. Put Public Key from Alma in the .ssh/authorized_keys file on the destination SFTP server
      1. NOTE: key is the same on both PSB and production environment
   2. Verify destination SFTP server accepts incoming traffic from ExLibris domains
   3. Alma > General> External systems > S/FTP definitions
      1. Can copy existing using duplicate option
         
      2. Use Edit option to Test FTP to make sure it's connecting
   4. NOTE: In Sandbox, you must also allow outgoing S/FTP connection for testing purposes
      1. Configure this at Alma > General > Allowed S/FTP connections
      2. This option doesn't exist in Production and isn't necessary as outgoing connections are not blocked
3. Add integration Profile for RS:
   1. 1. Alma >General>Integration Profiles
         
      2. In Actions tab: Integration type - xml/ncip
      3. Export file path = blank (could be set up to export to a specific directory if needed)
      4. Job runs nightly at 24:00 Eastern time to export waiting requests to BER server
4. Add new Berenson Remote Storage Circ desk
   1. Picks from shelf = yes
   2. Supports digitization = yes (not really necessary as BER decided not to implement digitization workflows in Alma)
   3. Add operators who need to use this desk
5. Add new Berenson locations/adjust existing locations to make them remote storage locations:
   1. Berenson decided to flip DEP, AUCT, STORE, and PER from regular locations to be remote storage locations
      
      1. 
      2. Need to adjust Type, Fulfillment unit, remote storage field, and External name for this change
   2. Make sure they are associated with remote storage circ desk for reshelve relationship
      1. Items returned to remote storage from BER will be manually "reshelved" (scanned in) by BER remote storage staff who will use a generic circ login to do this work
   3. Make sure type = Remote storage and remote storage = Berenson Storage for each new location
      
      
6. Adjust TOUs for BER:
   1. Go to Config > Fulfillment > Fulfillment units (Harvard University scope)
   2. In this case added new Fulfillment unit so that items in remote storage locations are requestable via HOLLIS (for physical requests); current Non Cambridge TOU does not allow for HOLLIS requesting. 
      1. Fulfillment unit is called NONCAMBREQ
      2. On shelf request policy = anywhere to allow HOLLIS requesting for these locations
      3. Make sure New BER remote storage locations are in Fulfillment Unit locations
      4. 
         
   3. Go to Rule type = request
      1. Add rule for BER requests remote storage for physical items such that they are requestable in HOLLIS:
         
         
         

Part II: Digitization Dept config: 

NOTE: BER decided not to implement this. See page history (pre-August 30 2019) for info on how it was configured for testing.