[Workflowtoolkit-l] Share your NVTGC wisdom

Tue Sep 7 09:16:05 EDT 2010

Princeton shares this model as well, although we don't have as many sites as
Yale.

Jennifer Block

_________________________________________

Jennifer Block

Interlibrary Services/Document Delivery Librarian

Princeton University

One Washington Road

Princeton, New Jersey  08544-2098

Phone:  609-258-5704

FAX:     609-258-0441

Ariel IP: 128.112.205.74

Email:   <mailto:jblock at princeton.edu> jblock at princeton.edu

_________________________________________

From: workflowtoolkit-l-bounces at geneseo.edu
[mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Jones, Carol
Sent: Tuesday, September 07, 2010 9:08 AM
To: ILLiad Best Practices Workflow Toolkit
Subject: Re: [Workflowtoolkit-l] Share your NVTGC wisdom

Tim,

We have a shared server for our ILLiad setup that may differ a bit from many
others.  We have seven "sites" on our server; five of them operate under
OCLC symbol YUS (Sterling Memorial is the primary site, plus Divinity, Kline
Science, Social Science, and Mudd libraries).  All incoming lending requests
are downloaded to Sterling and then routed to the other sites as needed,
based on which one "owns" the requested item.

 The other two sites have their own OCLC symbols; the Medical Library is YUM
and the Law Library is GXR.  Their incoming requests go directly to them,
based on the OCLC symbol in lender string.  

I'm not sure how much "wisdom" this provides, but it is another model of
shared server.

Carol Jones

Carol L. Jones

Head of Document Delivery

Sterling Memorial Library

Yale University

New Haven, CT 06511

Email:     carol.jones at yale.edu

Phone:  203-432-2080

FAX:        203-432-2257

From: workflowtoolkit-l-bounces at geneseo.edu
[mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Tim Bowersox
Sent: Tuesday, September 07, 2010 8:39 AM
To: ILLiad Best Practices Workflow Toolkit
Subject: Re: [Workflowtoolkit-l] Share your NVTGC wisdom

Dave, thanks so much for sharing this info! This will go a long way in
demystifying setting up NVTGCs on a shared server environment. Once I get
some spare time, I'll use this as the backbone for a Workflow Toolkit page
on the subject (with your name in lights, of course).  :)

Keep the contributions coming, folks!

-Tim

Tim Bowersox

Information Delivery Services Librarian

Milne Library, SUNY Geneseo

1 College Circle

Geneseo, NY 14454

(585) 245-5589

On Sep 2, 2010, at 12:29 PM, Dave Williams wrote:

Great idea, Tim! This is a useful topic and I can try help to document this.
And hopefully we others including the experts at Atlas Systems can fill in
the gaps, add to, and, where appropriate, correct me. And please let me know
if you want me to add this to the wiki and have people make edits there.

Anyway, to get the balling rolling:

== NVTGC Codes ==

This email will address who they are handled in two environments: non-shared
server AND in a shared server environment. (We can speak of this, because a
little over a year ago, Notre Dame went from a non-shared server environment
to a shared server environment and we got to learn the difference in how
they work in these two different invironments.)

I.                    NON-SHARED SERVER (Notre Dame Main Library + their
Delivery Locations)

HOW IT GENERALLY WORKS

There seems to be two types of NVTCG codes: (1) Main Institutional and (2)
Delivery Locations.

(1)    Our NVTGC code is our institutional code, IND.

(2)    When signing up for an ILL account via the ILL online registration
page, user can select a delivery location (for us, tends to be a branch):

o   ILL = ILL Office (synonymous with Main Library);

o   ARCH = Architecture Branch;

o   MATH = Math Branch;

o   Etc.

SERVER PROCESSING

BORROWING requests from our users come get processed and are based on their
Delivery Location NVTGC value. For example, we have routing rules that place
ARCH requests into a special Architecture Branch Queue.

** If user didn't select a Delivery Location NVTGC value, by default user is
assigned the ILL value. (For some reason, there was an issue of making it a
required field, which I don't recall now.)  This becomes important when we
switched to a shared server environment**

ILLIAD USER FORMS

On the "NewUserRegistration.html" form (online registration for new users),
these DELIVERY LOCATIONs options are coded under <#PARAM name="NVTGC" and
selecting a delivery location somehow links user to IND. Using the form,
users who don't select a delivery location (and therefore, an NVGTC value)
by default will be assigned the NVTGC value of ILL (main ILL office), not
IND (the institutional code). These sub-library delivery locations are all
within the institutional umbrella of the NVTGC code of IND (Notre Dame).

II.                  SHARED SERVER (Two Institutions)

HOW IT GENERALLY WORKS

Each institution has their own unique institutional code: IND (Main Library
+ Branches) and XND (Law Library)

WHY SWITCH TO SHARED SERVER?

Though they are under another administrative entity, the Notre Dame Law
Library wanted to use the ILLiad system to manage ILL requests. Given our
association and relationship with the Law Library, it made sense for us to
SHARE resources and costs, rather than have the Law Library purchase a
separate license and contract.

SERVER PROCESSING

With the two types of users sharing the same server - (1) Notre Dame "Main
Library + Branches" and (2) Notre Dame Library Users - borrowing request are
kept separate. Staffs from the two institutions do not see each others'
requests, because they are filtered based on the institutional NVTGC Value
(IND or XND)

** EXCEPT that the NVTGC code "ILL" (in a shared server environment) became
a DEFUNCT, Non Usable NVTGC value. When we switched to a shared server,
requests from users with NVGTC value of "ILL" were no longer being filtering
into the Notre Dame Main Library, but were "lost"; we had to contact Atlas
Systems (we are hosted) who changed any user with the NVGTC value of ILL to
IND. The NVGTC code then became a dual purpose: institutional and delivery
location for the ILL main office. **

ILLIAD USER FORMS

Therefore you will need to edit the User Registration forms and update the
default delivery location. The "NewUserRegistration.html" form ( <#PARAM
name="NVTGC" of ILL (main ILL office)) needs to be changed from "ILL" to
"IND." This ensures that patron who didn't select a delivery location during
registration have their request filtered to the changed NVGTC code (in our
case, IND) rather than filtered to the now defunct ILL code.

** This is important, if you don't want your users to have their request get
lost in the system. Since we are hosted, OCLC Support handles most of this
sort of configuration via scripts, but sometimes, things can fall through
the cracks. It did for us. ** Here is what the code was updated to:

<label for="NVTGC">

<span class="field">

<span class="req">*</span>

<span class="<#ERROR name="ERRORNVTGC">">

<b>Delivery Location</b></span>

<br />

<span class="note">When you choose Hesburgh Library IND will display</span>

</span>

<select id="NVTGC" name="NVTGC" size="1" class="f-name" tabindex="4">

<option value="<#PARAM name="NVTGC">" selected>

<#PARAM name="NVTGC"></option> </option> <option value="IND">IND/Hesburgh
Library</option>

<option value="ARCH">Architecture Library</option>

<option value="BIC">Business Information Center</option>

<option value="CPL">Chem/Physics Library</option>

<option value="ENG">Engineering Library</option>

<option value="KKIC">Kellog/Kroc Information Center</option>

<option value="MATH">Mathematics Library</option>

</select><br />

</label>

STAFF MANAGER (8)

In the shared server configuration, each ILLiad user account must be
assigned an Institutional NVGTC code (Called "Site") when their user account
is created. By doing this, when the user logs onto the ILLiad client, user
only sees the requests that pertain to their institution.

You can assign a user with an "Site" of "ALL", but this means that.

(This is a non issue in a non-shared environment)

CUSTOMIZATION MANAGER

When you log into the customization manager, you have to select the SITE
where you are working (see attached image.) Since I make changes or create
routing rules in the IND site, I select the IND code.

(This is a non issue prior in a non-shared environment)

If I can think of anything more, I will. And please, don't be shy about
corrections. That's the only way we'll get this thing figured out!

Best regards,

Dave Williams, Tech Support Dude, Resource Delivery

University of Notre Dame

williams.210 at nd.edu

574-631-8291

From: workflowtoolkit-l-bounces at geneseo.edu
[mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Tim Bowersox
Sent: Tuesday, August 24, 2010 8:58 AM
To: workflowtoolkit-l at geneseo.edu
Subject: [Workflowtoolkit-l] Share your NVTGC wisdom

One thing that is sorely lacking from the Workflow Toolkit are best
practices concerning multiple sites and those historic NVTGC codes in
ILLiad. For many of us in ILLiad-land, NVTGC is nothing more than a mythical
topic and doesn't actually impact our daily workflows. But for everyone else
who is using ILLiad in a shared-server or multisite environment, you've
undoubtedly developed unique workflows that take advantage of NVTGC codes.

It would be great if you could impart your NVTGC wisdom upon us
single-siters. Specifically, how have you implemented NVTGC codes at your
site? Are you a shared server or single server environment? What advice do
you have for folks exploring NVTGC codes?

I hope to compile your responses into a new topic in the Workflow Toolkit,
so please don't be shy! Feel free to share any documentation or flowcharts
you may have developed.

Share your wisdom on our blog at http://wp.me/pG0qX-bI

Tim Bowersox

Information Delivery Services Librarian

Milne Library, SUNY Geneseo

1 College Circle

Geneseo, NY 14454

(585) 245-5589

<cust_mgr_shared.jpg>_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.geneseo.edu/pipermail/workflowtoolkit-l/attachments/20100907/01de6f16/attachment-0001.html>