Configuration and Policies > FAQs for System Configuration > FAQs: Downloading Patron Photos

FAQs: Downloading Patron Photos

What requirements must be met for patron photos to display?

Various Circulation wizards will display a photo with the user information if the photo image is available, and WorkFlows is configured to display patron photos. The following requirements must be met for the photos to display in the circulation wizard windows.

The Configure Display of User Photographs global policy must be set to Display User Photograph. This policy can be accessed from the Global Configuration wizard on the Configuration toolbar.
The Display Of User Photograph policy for your library must be set to Display User Photograph. This policy can be accessed from the Library Wizard on the Configuration toolbar.
Patron photo images must be uploaded to the library server via the Update User Photo Helper or the Batch Photo Import Utility.

How are the patron photos downloaded from the library server to my workstation?

Patron photos are downloaded to the workstation on demand. As wizards access patron photos, the photo for each user is downloaded to the workstation to the \Workflows\tmp directory as each user record is accessed.

Which wizards display patron photos?

If configured to appear, patron photos display in all wizards that display the user information header.

Why are the patron photos not displaying when I use wizards that can display them?

The following conditions will prevent patron photos from displaying.

The Configure Display of User Photographs global policy is set to Do Not Display User Photograph. This policy must be set to Display User Photograph. The Configure Display of User Photographs policy can be accessed from the Global Configuration wizard on the Configuration toolbar.
The Display Of User Photograph policy for your library is set to Do Not Display User Photograph. This policy must be set to Display User Photograph. This policy can be accessed from the Library wizard on the Configuration toolbar.
There was a problem during the photo importing process. Try importing the photos again using the Batch Photo Import Utility.

Why am I seeing an error image in the place of a patron's photo?

If an image fails to load and displays an error image in its place, WorkFlows provides a short message noting the reason.

Bad image – The image file size is greater than 8 KB or the image file has been corrupted. Import your image files again using the Batch Photo Import Utility.
Image locked – There is a problem displaying the image. Try closing the wizard and opening it again.

What is the mechanism for updating patron photos?

You can update individual patron photos from the Modify User Wizard. To update photos in batch, you can use the Batch Photo Import Utility.

What happens to patron photos if I have to remove and reinstall WorkFlows?

Since the patron image files are stored on the server and only downloaded to the WorkFlows client on demand, removing and reinstalling WorkFlows will not affect your ability to view patron photos. However, it is recommended that you remove the \Workflows folder from your home directory when completely reinstalling a new client. This will force new and updated toolbars and wizards to be downloaded to your workstation. On Windows systems, you can find \Workflows in the \Sirsi folder in your home directory. On Mac systems, you can find /Workflows in the /Preferences folder. For more information, see FAQs: WorkFlows Files Saved to the Workstation Home Directory .

Why can’t I view patron photos when I run WorkFlows from a shared network directory?

It is possible you are running WorkFlows from a shared network directory using the –w pathname command line option. The patron image files are stored in a subdirectory of the shared network directory, and you may not have write permissions for that directory. If this is true, the wizard process will stop and not update the image files. To update patron image files, only a user who has write permission for the shared network directory (such as the System Administrator) must run WorkFlows without the –w command line option.

 


© 2006, 2014 SirsiDynix