This section describes implementation of ITWeb for multiple locations under a single Library record. Examples of this are school districts, branch library systems and consortia. The district, library system, or consortia is represented by the library record; the location record then represents each school, branch or member library.
For SearchBank or LifeCenter services, these implementations require only the addition of unique location records linked to the same library record. For ITWeb services, the config application must be used to create profiles and user accounts for each location, if needed. This work can be performed by IAC staff or by one or more site administrators. To create a site administrator login, follow the procedures found on the Enabling ITWeb page. Brief instructions for creating multiple preferences and administrator logins are provided here and assumes all location records have been created in RLIS.
Log in to the library's config UI as iac_support/my_antonia.
1. Create a new preference, as required, for each location
2. Modify each Location profile; assign the appropriate interface profile (preference) for each location
3. If needed, create new user accounts and assign access to the appropriate location(s) and preference(s); do not assign these users access to Privileges for All Databases, All Locations or All Preferences, or to any User Administration Privileges
It may only be necessary to create one preference for multiple locations, assuming all locations choose to implement the same interface options. If, during the setup of the preference, the "Use as Default Setting" option is checked, these preferences will be applied to any location's interface unless a separate preference has been explicitly assigned to that location.
It is useful to create a "master" user account, even if no one at the site has been identified for this level of access or control. This account must have access to all privileges, for all locations and especially for User Administration. In this way, a local site administrator has the ability to create new users and preferences, creating access points for other site administrators. This has the potential to remove IAC staff from the role of creating and maintaining multiple preference profiles and user accounts, and shifts the control loci to the district, library or consortia staff.
It is strongly recommended that, during initial setup of large consortial config UIs, that TGG staff create an additional user account "template". This account is configured with no privileges; this makes it easier for the site administrator to create new account by allowing them to start with a "blank" form.
An example of this type of setup is at .../itconfig/oetca.
Here are the details:
1. Create a new preference, as required, for the location
2. Modify the Location profile; assign the new preference to that location
3. If needed, create a new user account and assign access to the appropriate location(s) and preference(s); do not assign these users access to Privileges for All Databases, All Locations or All Preferences, or to any User Administration Privileges
If you've followed steps 1 and 2 above, choose "Summary" on the left navigation bar to return to the main nav bar.
In the new user form
* Record the User Name and Password; you'll need to send this information along to the site administrators, and the password is not recoverable in the config UI if forgotten.
At this point, you've completed the necessary and sufficient steps to allow individual site administrators access to the configuration UI. In NYSL's case, you probably don't want to assign Report privileges, and almost certainly don't want to assign User Administration privs.
All that's left to do at this point is communicate the the config UI's URL, and username and password to the site. I don't have a good piece of boiler plate for such a memo, but the basics might include:
/* Begin *
Greetings,
Blah blah blah...
URL: infotrac.galegroup.com/itconfig/nysl_xx
username: someuser
password: somepassword
<Some basic instructions for using the config UI, or how to find the access screens, or
who to call for help, inserted here>
* end */
Other scenarios
Ongoing additions of location records to a single library group.
Many statewide and large consortia contracts are implemented over a period of time (sometimes in perpetuity), where individual libraries submit technical/authorization forms. These forms will flow into the installation group over a period often exceeding a year. As these forms arrive, new location records will be created corresponding to the individual library. In addition, IP addresses may need to be added to the Library record IP registry, dialup, RPA and usage report profiles may also be required (as outlined in Enabling ITWeb).
In these situations, special attention needs to be paid to the implementation plan, if one exists. These plans will often dictate the format to be used for creation of location codes, mandate banner content and backlink URLs, as well as content and delivery of customer notification (examples of these are being posted at Active Implementation Plans)