system administrator notes - utm library portalportal.psz.utm.my/div/bpa_eng/images/training/... ·...

SirsiDynix Symphony 3.3.1

System Administrator Notes

December 2009

© 2009 SirsiDynix. All rights reserved.

The processes and all the routines contained herein are the proprietary properties and trade secrets of SirsiDynix. Except as provided by license agreement, this manual shall not be duplicated, used or disclosed for any purpose or reason, in whole or in part, without the express written consent of SirsiDynix. The information in this document is subject to change without notice and should not be construed as a commitment by SirsiDynix.

SirsiDynix grants the right of copying the enclosed material solely for the internal business use of the end user if (1) this document has been obtained by purchase or by license agreement in conjunction with SirsiDynix products, and (2) this copyright statement is included with each copy. All other copying or distribution is strictly prohibited.

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in sub-paragraph (b)(3) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013.

Rights for non-DOD U.S. Government departments and Agencies are as set forth in FAR 52.227-19(c)(1,2).

Sirsi®, WebCat®, Vizion®, WorkFlows®, Unicorn®, UnicornECOLE®, UnicornOASIS®, UnicornSTILAS®, Site Source®, DRA®, DRA Net®, Inlex®, MultiLIS®, Taos®, JurisLink™, Corinthian®, Dynix®, URSA®, Horizon™, Remote Patron Authentication™, TeleCirc™, and SirsiDynix Symphony™ are trademarks of SirsiDynix.

Other product and company names herein may be the trademarks of their respective owners. All titles, versions, trademarks, claims of compatibility, etc., of hardware and software products mentioned herein are the sole property and responsibility of the respective vendors. SirsiDynix makes no endorsement of any particular product for any purpose, nor claims responsibility for its operation and accuracy.

This document is compatible with SirsiDynix Symphony 3.3.1 Information in this document may also be compatible with later versions.

December 2009

D R A F T - - I N P R O G R E S S

Table of ContentsWorkFlows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

WorkFlows C Client Deprecated for Version 3.3.1 . . . . . . . . . . . . . . . . . . . . . . 5

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Unable to Search Korean Hangul Records — Unicode Oracle Sites Only . . . . . 7

Cataloging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

UNIMARC and SUNIMARC Formats Updated . . . . . . . . . . . . . . . . . . . . . . . . . . 9

e-Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Recommendations for Libraries Using Custom Elib_revD Pages . . . . . . . . . . . . . 13

Copy Admin File from Main Server to Remote e-Library Server . . . . . . . . . . . . 14

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

RevC Theme Created for Elib_revD Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

e-Library Variables May Now Be Modified in the Browser . . . . . . . . . . . . . . . 15

RTL Arabic Interface Now Supported in the Elib_revD Page Set . . . . . . . . . . . 17

Patron Authentication Using LDAP Now Available in e-Library . . . . . . . . . . . . 18

Variables Added to e-Library to Allow for Enterprise Integration . . . . . . . . . . . 19

Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

PayPal PayFlow Pro Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

81.pg Contained a Class Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Recreadlist2.cmd Contained an Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

User Record Load Format Updated with New Language Field . . . . . . . . . . . . . 23

WorkFlows Client 5

WorkFlows Client

General

WorkFlows C Client Deprecated for Version 3.3.1

With the release of SirsiDynix Symphony Version 3.3.1, the WorkFlows C client will no longer be supported. Sites using the C client will need to upgrade to the WorkFlows Java client. Steps to upgrade to the WorkFlows Java client are included in the Software Delivery Service upgrade information on the SirsiDynix Client Care web page.

6 Release Notes

General 7

General

Corrections

Unable to Search Korean Hangul Records — Unicode Oracle Sites Only

Previously, there were problems with keyword searching Korean Hangul records. This only occurred on SirsiDynix Symphony Unicode Oracle systems using BRS searching of Korean Hangul. To remedy this issue, a new Korean lexeme dictionary is delivered with the Version 3.3.1 upgrade. This dictionary will produce better and more consistent segmentation of Korean Hangul records. Users who want to index and search Korean Hangul should run the Rebuild Text Dictionary (Rebuildtext) report after this new lexeme dictionary is delivered.

SirsiDynix Symphony System Administrator Notes

SirsiDynix Symphony administrators who want to index and search Korean Hangul should run the Rebuild Text Dictionary (Rebuildtext) report after the new Korean Hangul lexeme dictionary is delivered with the Version 3.3.1 upgrade.

(UNI-24573)

8 Release Notes

Cataloging 9

Cataloging

Enhancements

UNIMARC and SUNIMARC Formats Updated

The SirsiDynix Symphony UNIMARC and SUNIMARC formats have been updated.

• In the U122 field (Time Period of Item Content) , subfield a (Time Period) has been made repeatable.

• In the U125 field (Sound Recordings and Printed Music) subfield c (Vocal Score, Accompaniment Reduced for Keyboard) has been added.

• In the U128 field (Music Performances and Scores) subfield d (Key or Mode of Musical Work) has been added.

• In the U130 field (Microforms - Physical Attributes) subfield a the following changes have been made

Character position 7 (Colour) code z (other) has been added.

Character Position 10 (Base of Film) codes c (safety base, acetate undetermined), d (safety base, diacetate) , e (safety base, polyester) ,f (safety base, mixed, mixed safety base films spliced) and g (safety base, triacetate) have been added.

• In the U140 field (Antiquarian - General) subfield a (Antiquarian Coded Data - General) character positions 0-3 (Illustration Codes - Book) and 4-7 (Illustration Codes - Full Page Plates) code z (other) has been added.

Only new installations will receive the entire set of format changes in the SirsiDynix Symphony installation.

For existing sites, the SirsiDynix Symphony administrator will need to make the appropriate format policy changes, as needed.

10 Release Notes

• In the U141 field (Copy Specific Attributes) subfield b (leather) has been added.

• The U145 field (Medium of Performance) has been added with the following valid Indicators and Subfields:

– Indicator 1 (Arrangement indicator) .

– Indicator 2 (Alternative medium indicator)

– Subfield codes

Valid values for Subfield a (Type of Performance Medium)

Code UNIMARC Description

0 original composition

1 arranged composition


# not applicable

1 alternative medium of performance


a Type of Performance Medium (not repeatable)

b Instrument/voice, conductor, other performer or device ( 8 characters) Use the abbreviations listed in Code list A/1-9, A/12-13. For suffixes use codes reported in Code list B-C.

c Type of ensemble (8 characters) Use the abbreviations listed in Code list A/10-11. For suffixes use codes reported in Code list B-C.

d Group within larger ensemble (8 characters) Use the abbreviations listed in Code list A/10-11. For suffixes use codes reported in Code list B-C.

e Number of parts (4 characters) Each repeated e subfield contains a four-character code indicating the total number of real parts indicated in the suffix. For suffixes use codes reported in Code list D.

f Number of players (4 characters) For suffixes use codes reported in Code list D.


a vocal a capella music

b instrumental music

c vocal-instrumental music

Cataloging 11

• The U425 field (Updates) has been added with the following valid Indicators and Subfields:

– Indicator 2 (Note indicator)

– Subfield codes

Subfield 1 (Linking data) - For Embedded Fields

OR for Standard Subfields

d electroacoustic music

e elecroacoustic-mixed music

u undefined,variable

Valid Entry UNIMARC Description

0 Do not make a note

1 Make a note


a Author (not repeatable)

b General Material Designation (not repeatable)

c Place of Publication (not repeatable)

d Date of Publication (not repeatable)

e Edition Statement (not repeatable)

f First Statement of Responsibility (repeatable)

g Subsequent Statement of Responsibility (repeatable)

h Number of Section or Part (not repeatable)

i Name of Section or Part (not repeatable)

l Parallel Title (repeatable)

n Name of Publisher, Distributor, etc. (repeatable)

o Other Title Information (repeatable)

p Physical Description (repeatable)

s Series Statement (repeatable)

t Title (mandatory, repeatable)

u Uniform Resource Locator (not repeatable)

v Volume Number (not repeatable)

x International Standard Serial Number (not repeatable)


12 Release Notes

• In addition, the ZUNIMARC Full Entry ID Synonym List has been modified to include the 145 and 425 fields.


The SirsiDynix Symphony UNIMARC and SUNIMARC formats have been updated.

To add new entries to a format policy, the administrator must first check the EntryID policy list within a format to see if the entry is available. If not, the administrator will need to create a new Entry ID policy. This new entry ID should now be added to the format. To create an Entry ID Policy, use the Entry ID policy helper. See the Entry ID policy helper topic in the WorkFlows Java client online Help.

To add an entry ID to a format, see the “Entries Tab for the Format Policy” topic in the WorkFlows Java client online Help. This topic describes the fields required when adding an entry to a format policy. For each entry ID, sub-tabs such as Basic,Display, and Punctuation display fields to be completed based on the purpose of the format. After adding an entry to a format, the administrator must halt and run the workstation server for format changes to appear.

(UNI-25698)

y International Standard Book Number/International Standard Music Number (not repeatable)

z CODEN (not repeatable)

0 Bibliographic Record Identifier (not repeatable)

3 Authority Record Number (not repeatable)

5 Institute to Which Field Applies (not repeatable)

Only new installations will receive the entire set of format changes in the SirsiDynix Symphony installation.

For existing sites, the SirsiDynix Symphony System Administrator will need to make the appropriate format policy changes, as needed.


e-Library 13

e-Library

General

Recommendations for Libraries Using Custom Elib_revD Pages

There are significant changes to the e-Library Elib_revD page set in SirsiDynix Symphony 3.3.1. This may cause previously created customizations not to work after the Symphony 3.3.1 upgrade. If you have already been using the Elib_revD page set in e-Library, and you have been making customizations, you can choose to preserve your customized Elib_revD page set. To do this:

Before the upgrade

1 Create the new directory Unicorn/Webcatcommon/Pages_deliv/Elib_revD_old. Copy the files in the Unicorn/Webcatcommon/Pages_deliv/Elib_revD directory to the newly created Elib_revD_old directory.

2 Create the new directory Unicorn/Webcat/Pages_custom/Elib_revD_old. Copy the files in the Unicorn/Webcat/Pages_custom/Elib_revD directory to the newly created Elib_revD_old directory.

3 Edit the Unicorn/Webcat/Config/system.env file so the PAGES_SET variable is defined as follows:

PAGES_SET|Elib_revD_old|

4 Edit the Unicorn/Webcat/Config/*.env file that is associated with a test login as follows.

PAGES_SET|Elib_revD|

After the upgrade

After the Symphony 3.3.1 upgrade, you will still have the Elib_revD page set that you had before the upgrade, including the customizations. You can see the new Elib_revD page set, minus your customizations, by logging in with a test login. This will allow you to test changes with the new page set.

In e-Library 3.3.1, the CSS structure has been changed to incorporate the use of themes. A default theme, along with themes for elementary, middle school and high school users, are delivered. The new structure does change the location of the custom.css file that should be used to create custom styles; you will need to edit the custom.css within the theme you are using. All sites will be delivered using the default theme. The CSS for this theme is located in Unicorn/Webcat/Config/Css/default/css . To change the theme in use, you can edit the THEME environment variable with the path to the new theme you wish to use.

14 Release Notes

Copy Admin File from Main Server to Remote e-Library Server

When any changes are made to the User Access or Environment policies in the WorkFlows Java client, it is required that the ...Unicorn/Config/admin file on the main SirsiDynix Symphony server be copied over to the remote e-Library server. This is necessary in order to keep the admin files in sync so that, when using Configuration Admin in e-Library, the correct environment file will be modified.

This only applies to SirsiDynix Symphony systems that use a remote e-Library server.

(UNI-25947)

Enhancements

RevC Theme Created for Elib_revD Pages

In e-Library 3.3.1, an eLib_revC theme has been created for use in the eLib_revD set of pages. This allows libraries that like the revC look to keep using it, while taking advantage of functionality that has been introduced with the Elib_revD set of pages.

Use of the revC theme may be configured by your SirsiDynix Symphony Administrator.

SirsiDynix Symphony System Administrator Note

The e-Library environment variables to allow the use of the revC theme in the Elib_revD page set are as follows:

• The PAGES_SET variable needs to be set to Elib_revD in /Unicorn/Webcat/Config/system.env

PAGES_SET|Elib_revD|

• The new THEME variable needs to point to the revC theme, by placing the following value in /Unicorn/Webcat/Config/system.env

THEME|/Css/revC/revC.css|

(UNI-22987, UNI-24216)

e-Library 15

e-Library Variables May Now Be Modified in the Browser

In e-Library, there is now the option for a System Administrator to modify certain environment variables through the browser. The System Administrator has the option to change individual environment files as he/she sees fit.

You must use a System Administrator login in order to have the ability to make changes to the environment files using the graphical interface. Once logged in as System Administrator, a Configuration Admin option will display in the rootbar, where these changes can be made.


The following is a list of the variables from ibistro.env that may now be modified in the e-Library graphical browser interface.

ALLOW_HOLD_OPEN_ORDER

ALTID_ACCESS

ALTIDLABELPUBLIC

BASE_DN

BESTSELL_CONFIG_LIST

BIND

BIND_DN

BIND_PASSWORD

CAT_ICON_BROWSE

CAT_ICON_EXACT_SEARCH

CAT_ICON_SEARCH

CAT_ICON_TERM_SEARCH

CERT_FILE_LOCN

CUSTOMCSS

DISP_ITYPICON

DISPCLASSONLY

DISPFULLCALL

DISPONORDER

HIDE_EST_WAIT

HOLD_ITEMS_ON_SHELF

IBISTRO_BESTSELL_CONFIG

IBISTRO_HOTSITES_CONFIG

16 Release Notes

IBISTRO_LIBINFO_CONFIG

IBISTRO_MOSTPOP_CONFIG

IBISTRO_MYFAVS_CONFIG

IBISTRO_RECREAD_CONFIG

LDAP_ADDR

LDAP_LIBR

LDAP_PORT

LDAP_UACS

LIBINFO_LISTLEN

LIBLOGO

LIBRARY_SLOGAN

LOGIN_FORM_TITLE

NUM_SEARCH_HITS

PIN_ACCESS

PINPROMPT

POWERSEARCH_LIBR_OPTIONS

QUICKSEARCH_LIBR_OPTIONS

RECREAD_CONFIG_LIST

SESSION_TIMEOUT

SSL_AUTHENTICATION

SUMMARY_HOLDINGS

TAGLINE

TITLE

UPPERCASE_USERID

USE_COPY_SUMMARY_HOLDINGS

USE_EDIT_HOLD

USE_HOLD_EXPIRATION_DATE

USE_HOLD_ICON

USE_HOLD_ICON_HITLIST

USE_ITEM_LIBRARY_DESC

USE_ITEM_LOCATION_DESC

e-Library 17

USE_KEEP_ALL_BUTTON

USE_LIBRARY_ALL

USE_LIBRARY_HERE

USE_LIMIT_BUTTON

USE_MAIL_SERVICE

USE_OUR

USE_OUR_APARTMENT

USE_OUR_DOB

USE_OUR_MIDDLE_NAME

USE_OUR_NAME_SUFFIX

USE_OUR_SSN

USE_RENEW_REVIEW

USE_RENEWED

USE_SUSPEND_HOLD

USEHOLDQUEUEPOS

USER_ID_TAG

USERID_ACCESS

USERIDLABELPUBLIC

WEBCAT_NAME

(UNI-23006)

RTL Arabic Interface Now Supported in the Elib_revD Page Set

In e-Library, the Right-to-Left Arabic interface is now supported in the Elib_revD set of pages.

(UNI-24105)

18 Release Notes

Patron Authentication Using LDAP Now Available in e-Library

Patron authentication using LDAP can now be done in e-Library. LDAP stands for Lightweight Directory Access Protocol, and allows a library to authenticate against a user database other than the ILS.


Once an LDAP server has been set up for use, SirsiDynix Symphony System Administrators should use the following steps in order to ensure that LDAP is configured on their SirsiDynix Symphony system

1 Log into e-Library as the System Administrator, and select Configuration Admin.

2 In the Environment pulldown, select System File.

3 Under the menu, select the LDAP Configuration option

4 Place the appropriate values in the listed variables:

• Address of the LDAP server - IP or DNS of the LDAP server.

• The Port on the LDAP server - Port number of LDAP server.

• LDAP Field for Lookup - Which LDAP field should be used for lookup.

• The Base Distinguished Name - The name of the entry. For example: DC=sirsi, DC=com is the Distinguished Name of the parent entry, where DC stands for Domain Component.

• The Library Policy for LDAP - Valid library policy name; it should be entered in all capital letters and should match a library policy in the SirsiDynix Symphony system.

• The User Access Policy for LDAP - Valid user access policy name; it should be entered in all capital letters, and should match a user access policy in the SirsiDynix Symphony system.

• Use BIND for LDAP - Should BIND be used for LDAP.

• The Distinguished Name for BIND - BIND distinguished name.

• The BIND Password - BIND password

• SSL Authentication for LDAP - Indicates SSL or simple.

• Certificate File Location - The path to a copy of the certificate of the LDAP server.

Note: The Distinguished Name for BIND and The BIND Password are only meaningful if Use BIND for LDAP is set to YES.

Note: Certificate File Location is only meaningful if SSL Authentication for LDAP is set to Yes.

Note: If you have more than one LDAP server you wish to use, than these values should be placed in the appropriate Environment files listed in the pulldown.

e-Library 19

5 While still logged into e-Library as System Administrator, change to the General Access section, and ensure that the following variable is set to No:

• Make User ID Uppercase

Note: Setting this variable to No means that all user id’s in e-Library will be case-sensitive.

6 Click Save before exiting out of e-Library.

7 On the main SirsiDynix Symphony server, in the ...Unicorn/Config/netports file, there should be an ldapserver line that specifies the LDAP port and IP address

ldapserver|LDAP server port|LDAP server IP address|

For example:

ldapserver|389|frodo.library.edu|

8 Halt and restart the SirsiDynix Symphony server to make the file changes take effect.

9 There needs to be a valid value in the webauth_ID field in the user records in SirsiDynix Symphony. User records may be manually edited in the WorkFlows Java client, or a batch load of the value into existing user records may be done.

(UNI-22548)

Variables Added to e-Library to Allow for Enterprise Integration

To allow better integration with Enterprise, variables have been added to e-Library. These variables only apply to customers who have both e-Library and Enterprise.


To enable better integration with Enterprise, set the following variables in the ../Unicorn/Webcat/Config/system.env or envn#.env files.

1 For iFrames for the header and navigation areas

• HEADER_IFRAME||

Defines the iframe to place in the header. This can be used to share headers between Enterprise and e-Library (RevD only).

• HEADER_IFRAME_HEIGHT||

Defines the height of the iframe in the header.

• NAVIGATION_IFRAME||

Defines an extra navigation bar. This can be used to share navigation between Enterprise and e-Library (RevD only).

• NAVIGATION_IFRAME_HEIGHT||

Defines the height of the iframe navigation bar

20 Release Notes

2 For a Go back to Enterprise button

• ENTERPRISE_GO_BACK_BUTTON_URL||

Defines the url for the enterprise profile to go to

• ENTERPRISE_GO_BACK||

Defines the label to use for the enterprise go back button

3 For an Enterprise Search Box

• ENTERPRISE_SEARCH_URL||

Defines the search url for the Enterprise Search Box to use.

• ENTERPRISE_SEARCH_HEADING||

Defines the heading to use on the Enterprise Search Box.

(UNI-25478)

Corrections

PayPal PayFlow Pro Changes

As of September 1, 2009, customers using PayPal’s PayFlow Pro with their OPACs were told they would need to upgrade to the next version of PayFlow Pro. In order to accommodate the changes made to the PayFlow Pro interface, variables will need to be set by your SirsiDynix Symphony Administrator.


If using PayPal’s PayFlow Pro as an option for bill paying in e-Library changes made in PayFlow’s interface necessitate that the following variables be set in your local .env files for e-Library.

VERISIGN_HOST|payflowpro.paypal.com|

VERISIGN_PAYMENT|1|

VERISIGN_USERID|sirsidynix|

VERISIGN_VENDOR|sirsidynix|

VERISIGN_PARTNER|PayPal|

VERISIGN_PASSWORD|s1rs1c0rp|

VERISIGN_HOST|pilot-payflowpro.paypal.com|

(UNI-23328)(08/04/09)

(UNI-24960)(10/06/09)

e-Library 21

81.pg Contained a Class Error

In previous versions of e-Library, the delivered 81.pg contained an error, which indicated the incorrect class was being applied.

This has been corrected.

(UNI-24106)

Recreadlist2.cmd Contained an Error

In previous versions of e-Library, the delivered recreadlist2.cmd in the Elib_revD page set contained an error that indicated the incorrect class was being used.

This has been corrected.

(UNI-24101)

22 Release Notes

System Administration 23

System Administration

General

Enhancements

User Record Load Format Updated with New Language Field

The user record load format has been updated with a new field, User Preferred Language. In the ASCII-text format, this field is labeled .USER_PREF_LANG. and can be populated with valid Language policy values. For the pipe-delimited user record format, this field was added as the last field of the user record, field position 53. When a user record is created in the WorkFlows Java client, this Language field defaults to English. Library staff can change the user’s preferred language to any Language policy name defined for the system. The Load Users report can be used to update the Language field value in a user’s record as long as the .USER_PREF_LANG. field (in ASCII-text format) is included in the user record and it contains a valid Language policy value. (UNI-20838)


The user record load format has been updated with a new field, User Preferred Language. In the ASCII-text format, this field is labeled .USER_PREF_LANG. and can be populated with valid Language policy values. For the pipe-delimited user record format, this field was added as the last field of the user record, field position 53. When a user record is created in the WorkFlows Java client, this Language field defaults to English. Library staff can change the user’s preferred language to any Language policy name defined for the system. The Load Users report can be used to update the Language field value in a user’s record as long as the .USER_PREF_LANG. field (in ASCII-text format) is included in the user record and it contains a valid Language policy value. (UNI-20838)

system administrator notes - utm library portalportal.psz.utm.my/div/bpa_eng/images/training/... ·...

Documents