User File Selection Tab
The User File Selection tab contains fields that are used when a report loads user records into the database. This tab may contain any of the following fields.
| • | Default Library |
| • | Dynamic Indexing |
| • | File to Load |
| • | File Type |
| • | Load by Alternate ID |
| • | Load by Web Auth ID |
| • | Mode |
| • | Move Previous User ID to Inactive IDs |
| • | Test Only |
| • | Update User ID and/or Alt ID |
| • | XML Stylesheet Filename |
Users in incoming records can be created or updated to any library defined in the appropriate field of the incoming user record. If new users are being loaded without a defined library, the library specified in this field will be the default library assigned to the user. Existing users are not updated to the Default Library; the existing user library is retained. The default value that displays is the Library associated with the User Access of the user who schedules the report. If the text in the Library field of the incoming record is not a valid Library policy name, the record will be loaded in error.
If this check box is selected, the loaded user records are automatically indexed immediately so they can be searched and browsed in the user searches. If this check box is cleared, the user records are not indexed until they are indexed by the next run of the Add, Delete, Update User (Aduusertext) report. By default, this check box is selected.
Note: It is recommended that you clear the Dynamic Indexing check box when loading more than 2,000 user records at one time so the SirsiDynix Symphony system performance is not adversely affected.
This field is required. Files of user records that have already been placed on the server in the Unicorn/Xfer directory display for selection. Select a file of user records from the list.
Note: You can use an ftp application to transfer the user record data on your workstation to the Xfer directory.
The File Type specifies the type of the file that contains user data to be loaded into the SirsiDynix Symphony database. Choose one of the following options:
| • | Choose Flat to load a file that is in the SirsiDynix flat format. |
| • | Choose XML to load a file that is formatted using XML and has a .xml file extension. |
This option is available for loading XML files that have been uploaded directly to the Unicorn/Xfer directory on the SirsiDynix Symphony via an FTP client. This feature may be useful to sites that want to automate the process of importing user data without the need for a file type conversion. For example, sites may choose this option for loading user data exported from its Microsoft® Active Directory® server directly to the SirsiDynix Symphony server.
If you choose the XML option, the XML stylesheet filename drop-down menu becomes available; you are required to choose an XML stylesheet if you choose the XML option.
Note: XML user data files are converted into SirsiDynix flat files when uploaded via the User Data Upload Wizard; if you want to load a user data file you uploaded using the User Data Upload wizard, choose the Flat option while specifying the appropriate File to Load.
If this check box is selected, the alternate ID will be used to match against existing user records. By default, users are matched by user ID, so this check box is cleared. If user ID or alternate ID fields are automatically converted to uppercase when they are entered at the workstation, the users that are loaded will also be uppercased. Otherwise, the case of the user ID and alternate ID fields in incoming records will be retained in new and matched user records.
If this check box is selected, the Web Auth ID will be used to match against existing user records. By default, users are matched by user ID, so this check box is cleared.
Selecting this check box disables the Load by Alternate ID check box, as only one ID can be used for matching records.
Note: The Web Auth ID is a case-sensitive field; if the case of the Web Auth ID of the incoming record is different from that of the Web Auth ID of the existing record, SirsiDynix Symphony will create a new user record. For example, if the incoming Web Auth ID value is TESTVALUE and the existing Web Auth ID is testvalue, SirsiDynix Symphony will create a new user record for TESTVALUE.
When user records are matched against existing users and a match is found, the mode determines how the records being loaded will relate to existing records.
| • | Create loads only new records. Incoming records will not load if they match existing User or Alternate IDs (depending on which is used for loading). Error records will be printed in the report log indicating that the user already exists. |
| • | Update loads only records that are matched against existing records. Incoming records will not load unless they match existing User or Alternate IDs (depending on which is used for loading). Error records will be printed in the report log indicating that the ID could not be found. |
| • | Create and Update creates new users for records that do not match an existing user, and user records that do match an existing user are updated. Create and Update is selected by default. |
Move Previous User ID to Inactive IDs
If this check box is selected and you have configured the report to update user IDs using the Update Other ID option, the report moves the previous user ID to the Inactive ID list when it updates a user ID.
Note: This check box can only be selected if the Load by Alternate ID and Update Other ID check boxes are selected.
The Test Only option allows you to run the report without making any modifications to the database. When this check box is selected, if any problems exist with the formatting of the file that would prevent the load or problems with an individual record, these may be corrected before the report is run to update the database. This check box is cleared by default.
When user records are matched against existing users and a match is found, you may select this check box to update any ID that was not matched. If you enable both this option and the Load by Web Auth ID option, both the user ID and the alternate ID are updated if their values have been updated in the incoming record.
For example, if you are loading by user ID, the alternate ID will be modified to the value supplied in the incoming record. Additionally, if you are loading by Web Auth ID, the user ID and alternate ID will be updated if there are updated values in the incoming record; otherwise, they will not be updated.
Clear the check box to leave both the matched ID and the other IDs unmodified.
Note: Unless the Web Auth ID is being used for matching user records, Web Auth IDs are always updated if SirsiDynix Symphony detects an update in the Web Auth ID field, regardless of this setting.
If you chose the XML File Type option, you will be required to make a selection from the XML Stylesheet Filename drop-down menu. SirsiDynix Symphony uses the stylesheet to format user record data to fields in the SirsiDynix Symphony user record. WorkFlows checks the Unicorn/Rptscript/XSL/importuser directory for available stylesheet files.
Note: SirsiDynix Symphony does not come delivered with any XML stylesheet files by default, so you will have to load your own to the SirsiDynix Symphony server. For an example of an XML stylesheet your library can use, visit the SirsiDynix Customer Support website at https://support.sirsidynix.com.
Related topics