ILLiad Exclusive: Adding a List of Users to the UserValidation table

Print Friendly and PDF Follow

You will first need to upload the text file to your ILLiad SQL Server for importing. If your server is hosted, contact your hosted server provider (OCLC or Atlas) regarding sending the file for import. The rest of these instructions pertain to only self-hosted servers with access to their own SQL Server.

Once the file is in place, you would then browse the SQL Server Management Studio under Databases | ILLData and right click on the database to choose Tasks .. Import Data.
Then, follow these instructions:

  1. A Data Transformation Wizard will open.
  2. Choose your Flat File Source as the source. Make sure that the file is delimited (separated by a character, usually a comma).
  3. Verify the file format and column delimiters. There should be a preview pane below.
  4. Set your source to your local SQL Server by filling out the Server name, authentication, and database.
  5. The next screen should show your source as the text file and the destination. You will need to change the Destination from the default table name to UserValidation by clicking in that field and choosing it from the drop-down.
  6. Click Next. You will want to run this immediately, but will also want to check the box to Save an SSIS package for later execution. It defaults to saving the package to the SQL Server. The schedule should be changed, or else it will run every day at midnight. It assumes that the text file will be in that same location each time, so be sure that you put the text file in a location where you'll be able to FTP it in the future.
  7. Click Next. Give the package a name if you chose to create one (i.e. UserValidation import for ILLiad).
  8. Click Next. Review the import in the final form. It should be going from a flat file to a SQL Server table. Click Finish to import the file and schedule the job.

For example, if you wish to limit access to ILLiad to only those users who have a library card, you can import a list of those library cards into the UserValidation table where the library card is the username. If you would like to import other information about those users (name, address, contact information, etc.) you can do that as well.

Usernames and Passwords for UserValidation

If your patrons are going to authenticate through the use of the UserValidation table, you will need to configure the username requirements and temporary initial password for your patrons. It is technically possible to not use the password field and leave that blank but is not recommended for security and privacy issues.

Usernames- The username patrons would enter when logging into the patron web pages would go in the Username field of the UserValidation table. This field must be unique across the entire database. If your list of users to import has duplicate entries, you will get errors trying to import those users into the UserValidation table.

Passwords- The password value can be implemented by entering the password for all users into the PlainTextPassword field of the UserValidation table. This field is used only for the initial registration of new users to compare to the value the new customer types in and is no longer used for future logins. 


For example, if you would like all ILLiad customers to use their library card as their username and their last name in all lowercase as their password, you can enter those values into the UserValidation table. The Username field would be 123456789 if that is the customer's library card number and the PlainTextPassword field would be "smith". Note that while you are using the customers' last name as his password, you would want to enter that value into the PlainTextPassword field and not the LastName field. Any other information you wish to pre-populate can be entered in UserValidation as well (FirstName, LastName, Phone, EMailAddress). Because you are using the PlainTextPassword field, the Password field in UserValidation would be blank.


If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation: