NVTGC -- Affiliation v. Delivery Location

The NVTGC field is unique in that it can designate 2 types of functionality: Site/Affiliation (NVTGC) v. Delivery Location.

• Site/Affiliation: A location which will be a fully operational ILL unit, processing borrowing & doc del for its users and lending request from its collection.
• One ILLiad instance can have multiple Sites. 
• Each Site will have all ILLiad functionality. 
• A Site can have multiple Delivery Locations.
• This type of NVTGC will display as a list of processing centers options when you log-into the Client. 
• Delivery Location: A location designated strictly for patron pick-up and return of print materials.
• Email notifications can be customized to reflect information unique to each Delivery Locations such as hours and phone number. 
• Once you have logged into the client, the system will limit you to viewing only those requests and users Delivery Locations configured for that Site.  In most cases, the Site/Affiliation NVTGC code will be replicated here.
• There is not a direct way to view which NVTGC codes are configured only as Delivery Locations in the Client or the Customization Manager. Support can provide a list for you.

 This design was built under the assumption that each Site on ILLiad instance would have disparate Delivery Locations because they are serving disparate user groups. For example

• Upland University has 3 Sites on its ILLiad instance: Main, Medical, and Law. 
• Main library has Delivery Locations Engineering, Music and Architecture.
• Medical has Delivery Locations Med Library and Research Annex.
• Law has one Delivery Location at the Law Library.

If you have Delivery Locations that are shared across the Site/Affiliation location, you will need to add new Delivery Location configurations FOR each Site WITHIN each Site. Here's an example of what I mean by that:

• Upland University ILLiad has 5 Sites which are all also potential Delivery Locations: Main Library (MAIN), Medical Library (MED), East Campus (EAST), Downtown Campus (DTWN), Alpine Research Center (MTN). The Medical Library also has an additional Delivery Location (Research Annex-ANNX) that is only accessible to Medical Library patrons. The following Delivery Locations would need to be created.
  • NVTGC: MAIN
    • Delivery Locations
      • MAIN-MAIN
      • MAIN-MED
      • MAIN-EAST
      • MAIN-DTWN
      • MAIN-MTN
    • NVTGC: MED
      • Delivery Locations
        • MED-MAIN
        • MED-MED
        • MED-EAST
        • MED-DTWN
        • MED-MTN
        • MED-ANNX
      • NVTGC: EAST
        • Delivery Locations
          • EAST-MAIN
          • EAST-MED
          • EAST-EAST
          • EAST-DTWN
          • EAST-MTN
        • NVTGC: DTWN
          • Delivery Locations
            • DTWN-MAIN
            • DTWN-MED
            • DTWN-EAST
            • DTWN-DTWN
            • DTWN-MTN
          • NVTGC: MTN
            • Delivery Locations
              • MTN-MAIN
              • MTN-MED
              • MTN-EAST
              • MTN-DTWN
              • MTN-MTN

NOTE:  In order to add delivery locations to the ILLiad system, a script will need to be run. This script will create the necessary database entries for any new delivery locations. Information about that process can be found here: https://support.atlas-sys.com/hc/en-us/articles/360011910473-Adding-Delivery-Locations

Implications for User Records
The user record will always have an NVTGC value which assigns the user to a Site/Affiliation and all the subsequent requests would only be view-able when logging in the Client with that symbol. If the Site has just one Delivery Location, the user record will have an NVTGC value, serving both purposes of Site/Affiliation & Delivery Location. When a site has multiple Delivery Locations, the user is restricted to the Delivery Location options that are configured for his/her NVTGC. However, in the Client User Record ALL DELIVERY LOCATIONS will display in the Location field regardless of the Site/Affiliation under which the Client is viewing. 

The configuration of your web pages determines how the NVTGC value is assigned to user records. See our documentation or contact your support representative for more information on this configuration.