Director s Station Administration Training Guide (Version 4.8.1)

Transcription

1 Director s Station Administration Training Guide (Version 4.8.1) DOC-DRSTGEN-ALL

2 Publication Name: Director s Station Administration Training Guide Publication Number: DOC-DRSTGEN-ALL Version Number: First Printing: April 2005 Updated: June 2007 Last Updated: August 2008 Additional copies of this document can be downloaded from the Client Care section of the Sirsi web site, 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. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in Technical Data and Computer Software clause in DFARS Rights for non-dod U.S. Government departments and Agencies are as set forth in FAR (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, and TeleCirc 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.

3 Table of Contents Introduction... 3 Training Overview... 3 Who Should Attend?... 3 Prerequisite... 3 Course Goals... 3 Director s Station Overview... 5 Managing User Access... 5 Director s Station Address... 5 Default Users and Passwords... 5 Dashboard and Popout Menu... 6 Popout Menu Bar... 7 Site Management... 9 Managing Groups... 9 Adding a New Group Assigning Cube Access to a Group Assigning Database Access to a Group Editing a Group Assigning Group Members Deleting a Group Managing Roles Managing Users Adding a User Editing an Existing User Deleting a User SwiftViews Managing SwiftViews Cubes About Cubes Manage Cube Security Editing Cube Security Assigning Cube Access to Groups Using Browse to Design Reports Using the Designer to create a new report Managing Categories, Menus, and My Folder Managing Categories System Categories Changing Order of Categories Category Members Managing Menus Adding Items Sorting menu items August 2008 i

4 Director s Station Administration Training Guide Managing My Folder Adding Items Editing Items Storing Items Deleting Items Sorting menu items My Profile Managing Reports Manage Reports Changing the Display Using the Reports Menu Additional Tools on the Reports Toolbar Systems Administration Managing Application Settings General Tab Reports Tab Tab Advanced Tab Managing User Sessions Managing Log Files Understanding the Structure of Director s Station Keeping Director s Station Running Smoothly Part 1 Confirm that the Data is Current and Correct Part 2 Extract Director s Station Data (datainterchng) Report Part 3 Checking the ETL (Extract Transform Load) Part 4 Contact Client Care Backing Up the Director s Station Scenario 1: Full System Backup Scenario 2: Automated Backup Scripts Scenario 3: Backup Directory Index ii

5 Introduction Training Overview Who Should Attend? Prerequisite Course Goals This course is intended for the Director s Station administrator who will be responsible for maintaining the application and training the end user. No previous classes are required. However, it is recommended that participants attend the Director s Station End User Training before attending this class. After completing this course, participants will be able to: Create new groups, roles, and users Create a SwiftView for new groups Manage security in Director s Station Maintain the function and look of Director s Station through the Popout Menu or the Dashboard Understand how information is brought over and processed in the Director s Station server Understand how to keep Director s Station running smoothly August

6 Director s Station Administration Training Guide 4

7 Director s Station Overview Managing User Access Director s Station administration can be divided into two broad categories: administration within the user interface of Director s Station, and systems-level administration that encompasses data transfer and other maintenance processes. Director s Station Address You can access Director s Station using a URL with the following pattern: If your network uses internal IPs, use the internal IP address to access Director s Station. Default Users and Passwords A valid user account is necessary to access Director s Station. Director s Station: administrator director sirsidynix The administrator and director user logins represent the primary user groups expected to access Director s Station. The delivered password for each of these logins is the user name repeated: The administrator user name has the password administrator. The director user name has the password director. It is recommended that you change the passwords for these users. User names are not case sensitive, but passwords are. How to change user names and passwords is explained on pages of this training guide. Note Please notify SirsiDynix Client Care of any changes to the sirsidynix login or password. Groups can be used to limit a user s access. A user has access rights to all of the data to which his assigned group has access. August

8 Director s Station Administration Training Guide Dashboard and Popout Menu For example, if you want to limit a user to the MainLibrary group, which has access only to the MAIN library s collection data, do not assign that same user to the delivered Directors group. The Directors group has unlimited access to all of the library s data, and the all access of the Directors group will override the main access of the MainLibrary group. Popout Menu Bar The Dashboard is the starting point for collection analysis. The Dashboard can be divided into the following sections: SwiftLinks Tabbed lists of delivered and customized reports, meters, and charts in SwiftReports, SwiftMeters, and SwiftCharts tabs, as well as a General tab with functions that are used by administrators SwiftReports Delivered and customized reports SwiftCharts Graphs created from reports SwiftMeters Notifications for data that has crossed a set threshold or thresholds SwiftHelp A list of help topics delivered to assist in working with Director s Station. Note The more panels you have on your dashboard, the longer it will take to load each time you refresh your dashboard. 6

9 Popout Menu Bar Icon Description Home Click this icon at any time to return to your Dashboard. Manage Menu Click this icon to upload, organize, and manage documents, reports, charts, and meters in the Popout Menu (for all users). Manage My Folder Click this icon to upload, organize, and manage your documents, reports, charts, and meters in your personal My Folder. Log Off Click this icon to exit Director s Station. If you use the on your browser to close the window, you will not immediately clear the session. The session will remain active until it expires. This can create problems if you have a limited number of licenses, or if you restrict logins to only allow one concurrent login per user. Users will have to wait for sessions left by closing the browser window to time out before they can log in. August

10 Director s Station Administration Training Guide Popout Menu The Popout Menu includes the following folders, also known as categories: About SirsiDynix Contains a link to the SirsiDynix home page. Documentation Contains access points to the on-line SwiftKnowledge documentation. Collection Analysis Contains reports designed to access your SirsiDynix Symphony or Unicorn data. It is divided into functional areas in the library such as Administration, Technical Services, and Public Services. There is also a folder for All Measures All Modules. These are all of the delivered reports in Director s Station. Each of these reports has links to the appropriate detailed lists and contains all of the available dimensions and measures. Public Access Analysis Contains reports designed to access your OPAC data. Site Management Used by administrators to administer Director s Station users, groups and access. This training guide focuses almost entirely on the contents of this category. My Folder Used to organize customized reports, charts, s, meters, links, and documents. 8

11 Managing Groups Site Management Users are the individual logins used by your staff to access Director s Station. Director s Station security is managed through these users. Administrators can create individual users for everyone who will be accessing Director s Station, or they can create users that are shared by several staff members who all do the same thing. Because each user has their own dashboard and My Folder, it is usually best to have a separate user created for each staff member who will be using Director s Station. Because many users are likely to have similar access and security rights needs, groups and roles are used to set up the rules for what different types of users can and can t do. When users are created, they are assigned to the groups and/or roles needed to give them the access they should have. Every user must belong to at least one group, but roles are optional. Manage users, roles, and groups in Director s Station, as follows: 1. Click the Popout Menu Bar. 2. Click the Site Management folder to access Manage Users, Manage Roles, and Manage Groups. Another way to get to this is through the General tab of the SwiftLinks panel on My DirectorsStation Dashboard. 3. After selecting the desired management option, you can create, edit, or delete users, roles, or groups for the continued management of your Director s Station site. Many sites do not need additional groups, but if you add new groups, it is recommended that the groups (and roles, if used) be created before the users are created. To access Manage Groups 1. Click the Popout Menu Bar to view folders. You can also access this by going to the General tab in the SwiftLinks panel of My DirectorsStation Dashboard. 2. Click the Site Management folder. 3. Click Manage Groups. When you access Manage Groups, a list of the available groups to which you have access appears: August

12 Director s Station Administration Training Guide From Manage Groups you can perform the following functions: Assign group members Manage group cube access Add a new group Edit an existing group Delete a group Adding a New Group To add a new group 1. In Site Management / Manage Groups, click New Group. The New Group dialog box appears: 10

13 2. Enter the required Name and Description fields. 3. Check the System Group checkbox if you want the group to be a system group. System groups cannot be deleted without un-checking the system group checkbox first. System groups are displayed in blue in the group list. 4. Use the arrow buttons to add or remove Rights for the new group. You can also move a group from column to column by double-clicking on it. To move several at once, hold down the CTRL key to select multiple rights, then click the arrow to move all selected rights. Only rights assigned to your user access by the administrator will display. These rights may be assigned when managing groups or users: August

14 Director s Station Administration Training Guide Rights Global: Help Edit Global: Group Administration Global: Role Administration Global: Site Administration Global: Upload Documents Global: User Administration Reports: Alerts Reports: Calculator Reports: Create Charts Reports: Design Reports: Download Description This right is obsolete with the new Help implementation. It is only displayed when managing users. Sets a user as a Group Administrator. This right cannot be assigned to a role or group. It is only displayed when managing users. Sets a user as a Role Administrator. This right cannot be assigned to a role or group. It is only displayed when managing users. Sets a user as a Site Administrator. Site Administrators automatically have access to all other rights. It is only displayed when managing users. The user has the ability to upload documents to the user's "My Folder". When this right is coupled with the "Group Administrator" right a user can upload documents to the Popout Menu. Sets a user as a User Administrator. This only allows editing of users. It is only displayed when managing users. The user has the ability to create a meter. Users can still see and interact with meters that have been created by others even when this right has been removed. The user has the ability to create custom calculation within reports. The user can view and use the selection menu that will appear when highlighting a group of cells. The design icon will be visible for users with this right. If this right is not given the design icon will not be on the toolbar. The user has the ability to download the report. Removing this right will remove the export icon from all reports for a given user. 12

15 Reports: Drill Reports: Reports: Include Empty Rows Reports: Move Filters Reports: Order Columns Reports: Overwrite Protect Reports: Print Reports: Save Reports: Sort Reports: Use Filters Reports: Value Filter Reports: Change Variables Reports: XML Writer This right gives access to the detailed list report links on the select menu that are created by SirsiDynix (i.e. title lists). The user has the ability to reports. Removing this right will remove the icon from all reports for a given user. This gives the user the ability to change the suppression of empty rows. If the user is not given this right, the default setting is to suppress empty rows. If this right is not given the choice will not be seen in the Report Settings. This gives the user the ability to move filters (aka dimensions). This gives the user the ability to move columns. This gives the user the ability to overwrite protect a report that is saved to the Popout Menu. This locks a report so no user can overwrite it. This right requires the Reports: Save right. The user has the ability to print a report. Removing this right will remove the print icon from all reports for a given user. The user has the ability to Save the report to the Popout Menu. All users have the ability to save reports to My Folder regardless of this setting. The sort option will not appear on the column menu if this is right is not given. If this right is not given the user will not have access to filter boxes. The Value Filter option will not be available on the column menu if this right is not given. This right allows a user to create and change custom report variables. This allows access to the Edit Report window which shows the reports XML and the View Query window. This right is recommended for advanced users. August

16 Director s Station Administration Training Guide Note To restrict users from saving items to categories other than My Folder in the Popout Menu, do not include the Reports: Save and Reports: Overwrite Protect rights. Users without these rights are able to save items to their own My Folder only. 5. Click Save to add the new group, or click Cancel to return to Manage Groups without saving your changes. Assigning Cube Access to a Group To grant a group access to specific cubes 1. In Site Management / Manage Groups, select a group from the list. 2. Click Group Cube Access. The Group Cube Access dialog box appears: 3. Do one of the following: To give full access to a cube, mouse-over the cube name and click anywhere in the yellow area outside of the Partial button. A check appears in the box indicating that this group has full access to this cube. With full access, members of this group are able to use all dimensions in this cube. To give partial access to a cube: a. Mouse-over the cube name and click in the Partial button on the right. 14

17 The Group Cube Access dialog box appears: b. Open the Measures folder if you want to restrict members of this group from using any measures. c. Uncheck any measures or dimensions that you don t want members of this group to be able to use. d. When finished, to return to the Group Cube Access dialog box, click OK to save your changes, or Cancel to not save your changes. 4. Click Save to save your changes or click Cancel to return to Manage Groups without saving your changes. Assigning Database Access to a Group In order for users of Director s Station to have access to detailed drill-down lists, they must have access to the SQL databases (SirsiDW and SirsiLogs) that contain the data for the detailed drill-down lists. To grant a group access to databases 1. In Site Management / Advanced / Manage Database Registration and Security, select SirsiDW from the list. 2. Click Database Groups. August

18 Director s Station Administration Training Guide The Database Groups dialog box appears: 3. Move all of the newly created groups from the No Access side to the Access side. You can highlight multiple entries, and use the move multiple selected groups. 4. Click Save to save your changes or click Cancel to return to Manage Database Registration and Security without saving your changes. 5. Repeat the process for the SirsiLogs database. to Editing a Group To edit an existing group 1. In Site Management / Manage Groups, select a group from the list. 2. Click Edit to open the Edit Group dialog box. 3. Edit the group s Name, Description, or Rights. 4. Click Save, or click Cancel to return to Manage Groups without saving your changes. 16

19 Assigning Group Members To add and remove members from a group 1. In Site Management / Manage Groups, select a group from the list. 2. Click Group Members. The Group Members dialog box appears listing the users who are members of the group: Note All security in Director s Station is controlled at the group level and is used to determine menu and data access. You must be an Administrator to access the Manage Groups function. An administrator can only see and edit a group in which he is a member. Administrator users should be members of all groups. 3. Select the users you want to make Members or Non- Members, and click the appropriate arrow button. You can also double-click the user to move the user from one list to another. You can select multiple users by pressing the CTRL button. August

20 Director s Station Administration Training Guide Deleting a Group To delete an existing group 1. In Site Management / Manage Groups, select the group you want to delete from the list. 2. Click Delete. 3. Click OK to confirm. Note Deleting a group does not affect user accounts. However, deleting a group may affect user access to components if that user belongs to multiple groups. You cannot delete System Groups, which are displayed in blue in the list, without first changing them to nonsystem groups. Managing Roles Managing Users Roles are much like groups, except that they do not control menu or cube security. Anything you can accomplish with a role, may also be done with a group. Groups tend to follow your organization chart vertically, while roles cut through your organization horizontally. In some cases it is easier to keep roles and groups separate than it is to create more groups to accomplish role differentiations. You must be an Administrator to access the Manage Roles page. The primary use of roles is to allow the opportunity for an individual SwiftView that is different from the group SwiftView. However, because security is not controlled through roles, a user will continue to be able to access only those reports in the SwiftView that are accessible to his group level. To access Manage Users 1. Click the Popout Menu Bar to view folders. You can also access this by going to the General tab in the SwiftLinks panel of My DirectorsStation Dashboard. 2. Click the Site Management folder. 3. Click Manage Users. Manage Users provides a list of all users that exist within the system. If there are many users, you can use the box at the top to search for a user s name: 18

21 Adding a User From Manage Users, you can do the following: Add a new user Edit an existing user Delete a user To add a new user 1. From Site Management / Manage Users, click New User. The New User dialog box appears: August

22 Director s Station Administration Training Guide 2. Required Enter the new user s First Name and Last Name fields. 3. Optional If you want, you can enter the new user s Address. If a user has an address entered her, and has any active meters, the user can be notified that the meter has reached its thresholds. 4. Required Enter the new user s Username for logging into Director s Station. 5. Optional If you want, you can enter a Reference Number for the new user. This field has no function and is for reference only. 6. Optional Clear the Account Enabled checkbox if you want to disable the account. 7. Required Enter a Password, and re-type it in Affirm Password. A message displays if both values are not identical. 8. Optional You can set the password to expire automatically by selecting Password Expires and entering the date of expiration. 20

23 After the password expiration date passes, the user is prompted to change the password upon the next login. The expiration date is automatically updated to expire a given number of days in the future. If you prefer that the password not expire, clear the check box, and the user may go to My Profile to change his password. See page 44 of this training guide for more information on My Profile. 9. Recommended To make the user a member of a group, move the selected group or groups from the Non-Member list to the Group Member list. Use the arrow buttons to move users from one box to another. Members of the Administrators group have access to Site Management and can save reports to the Popout Menu, as delivered. Other groups can be set to save to the menu if the site desires. Group membership can also be managed from Manage Groups. 10. Optional Move roles from the Roles Not Held list to the Roles Held list to assign roles to the user as needed. Roles are typically used to manage multiple SwiftViews. Use the arrow buttons to move users from one box to another. The user will be granted all access rights assigned to this role. No roles are delivered by SirsiDynix. Roles are explained further on page 17 of this training guide. 11. Optional Assign additional rights to this user if needed. As you move groups and roles over for user memberships, you see the corresponding Rights move with them.. If no rights move over then no rights are assigned to the groups or roles you assigned to the user. In addition to the group and role rights, you can also assign a user one or more individual rights. If a user is moved out of a group or role, they will still maintain the individually assigned rights. Note For information about the each of the rights available, see the chart that begins on page 11 of this guide. 12. Click Save to add the new group, or click Cancel to return to Manage Users without saving your changes. Note When creating a new user in a new group, the administrator is already automatically a member of the new group. Do not remove the administrator from the group. If the administrator is not included in a group, the administrator does not have the right to manage the group and does not see the user in the list. August

24 Director s Station Administration Training Guide Editing an Existing User Deleting a User To edit an existing user 1. In Site Management / Manage Users, select the user you want to edit from the list. 2. Click Edit to open the Edit User dialog box. 3. Make desired changes, as explained on pages of this training guide. 4. Click Save to save your changes, or click Cancel to return to Manage Users without saving your changes. To delete a user 1. In Site Management / Manage Users, select the user you want to delete from the list. 2. Click Delete. 3. Click OK to confirm. 22

25 Managing SwiftViews SwiftViews Whenever a user is logged in to Director s Station, he is associated with a personal dashboard that is called a SwiftView. When a user is first created on your site, he will have a blank template SwiftView. Each user should select a SwiftView from one of the delivered SwiftViews. SwiftViews for administrators and directors are delivered with Director s Station. When a user belongs to either of these groups (Administrators or Directors), Select SwiftView can be used to select a populated SwiftView. To assign a SwiftView to a User 1. Make sure the user is assigned to at least one group with an existing SwiftView (e.g. Administrators or Directors), even if it is only long enough to assign a SwiftView. 2. Mouse-over Menu: 3. Mouse-over Select SwiftView 4. Click the name of a group with a pre-defined SwiftView (e.g. Administrators or Directors) that you want to copy (Do NOT select My SwiftView). 5. After page refreshes, again mouse-over Menu. August

26 Director s Station Administration Training Guide 6. Mouse-over Copy SwiftView to 7. Click on My SwiftView. 8. Click OK in the confirmation window. 9. Log off of Director s Station. 10. Log back in as the new user. 11. Make desired changes to the SwiftView Dashboard. Note If the user was temporarily added to a group just so that group s SwiftView could be copied (ex. Administrators or Directors), delete the user from that group now that the SwiftView has been copied. Every time you log in after My SwiftView is saved, the saved information appears as My SwiftView. 24

27 Cubes About Cubes In Director s Station, a cube is loosely related to a module. Cubes allow administrators to define which measures and dimensions users can access in the reports. SirsiDynix delivers all of the cubes designed to be used with Director s Station. All of the information in these cubes is current database information with the exception of the circulation information related and OPAC cubes. There are two types of data in Director s Station cubes. Database cubes are taken directly from the tables in a Symphony/Unicorn ILS. Transactional cubes are created from logs of activity, such as circulation transactions, or OPAC searches. Each cube below is identified as either database, or transactional: Acquisitions Fund, vendor, order, and distribution database information Activity Item use, hold item, and other staff activity transactional information Authority Authority database information Bill Bill creation and payment database information Booking Booking database information Catalog Catalog, call number, and item database information Charge Charge records as well as other state of the collection database information. This corresponds with the All Checkout Measures (Current) reports. Checkins Discharge item transactional information only Checkouts Only transactional information associated with circulation, including item and reserves checkouts and renewals. This corresponds with the All Checkout Measures (Historical) reports Hold Hold database information OPAC Search history or transactional information (if you are collecting weblogs from ibistro/ilink, Web2, or EPS) Request Request database information Reserve Reserves database information August

28 Director s Station Administration Training Guide Manage Cube Security Serials Serials database information Users User database information You should not register any new cubes. However, you can manage access to cubes as well as individual measures and dimensions within a cube. CAUTION Never create a new cube or deactivate an existing cube. To access Manage Cube Security 1. Click the Popout Menu Bar to view folders. You can also access this by going to the General tab in the SwiftLinks panel of My DirectorsStation Dashboard. 2. Click the Site Management folder. 3. Click the Advanced folder. 4. Click Manage Cube Registrations and Security. The Manage Cube Security dialog box appears: 26

29 You can do the following from Manage Cube Security: Edit the registration or security of existing cubes Manage which groups have access to specific cubes Browse the hierarchies and measures of selected cubes 5. If you can t see any cubes that should be in the list, check the Show Inactive Cubes box to display all cubes, even those that have been deactivated. 6. If you are having trouble accessing a cube, such as A problem has occurred messages, the first thing to try is Clear All Connections. CAUTION Never use the New Cube, or Deactivate options. Any cube you create is not supported by SirsiDynix. If you deactivate a cube (such as the Booking cube, because you do not have the Materials Booking module) it cannot be restored if you were to purchase the Materials Booking module at a later date. Editing Cube Security To edit cube security 1. From Site Management / Advanced / Manage Cube Registrations and Security, select the cube you want to edit. 2. Click Edit. The Edit Cube Security dialog box appears: August

30 Director s Station Administration Training Guide 3. Do not edit the Cube Label. The cube label displays as the start of the title on all reports created from the cube and is displayed in the Add Cube section. 4. Do not change the values in Connection String. If you change any of these values, the cube will no longer be accessible in Director s Station. Below is a description of the fields in this section: Cube Name This field contains the actual cube name created in Analysis Services. Server Name This field contains the Analysis Services server name. This will always be the same as the computer name that Analysis Services resides on. If the Web server and Analysis Services exist on the same machine then you may see the keyword localhost. Server Type This will always be Analysis Services Database Name This field contains the Analysis Services database that contains the cube. This should be DirectorStation for the cubes that are created from the Symphony databases. The database name for cubes created from the history, statistics, and web logs are the same as the cube name (Activity, Checkouts, Checkins, OPAC). 5. Edit the Description. 28

31 A description is not required. The description can only be seen by Administrators who have the right to edit cube registration. 6. You can uncheck Cube Enabled to disable cubes for which you don not have corresponding Unicorn or Symphony modules. Director s Station is delivered with this selected. If a cube is enabled, it means that people have the ability to access the cube and access all reports created against the cube. A disabled cube and its associated reports cannot be accessed by users. Any attempt to access a cube that has been disabled will result in the following error message: This cube has been disabled. Assigning Cube Access to Groups To grant a group access to specific cubes 1. In Site Management / Manage Cube Registration and Security, select a cube from the list. 2. Click Cube Group Access. The Cube Group Access dialog box for the selected cube appears: August

32 Director s Station Administration Training Guide 3. Do one of the following: To give full access to a cube mouse-over the group name and click anywhere in the yellow area outside of the Partial button. A check appears in the box indicating that this group has full access to this cube. With full access, members of this group are able to use all dimensions in this cube. To give partial access to a cube a. Mouse-over the group name and click in the Partial button on the right. The Cube Group Access dialog box appears: b. Open the Measures folder if you want to restrict members of this group from using any measures. c. Uncheck any measures or dimensions that you don t want members of this group to be able to use. d. When finished, to return to the Cube Group Access dialog box, click OK to save your changes, or Cancel to not save your changes. 4. Click Save to save your changes or click Cancel to return to Manage Groups without saving your changes. 30

33 Using Browse to Design Reports It is faster to use the Design option when creating complicated reports because the query is not sent to the server until you have completed your selections and the server only returns the information required for the report, not for all of the possible measures and dimensions. CAUTION Detail drill-down lists are report specific. If you create a report using the Browse option, there will be no detail drill-down lists associated with it. You can copy the XML for the list reports from the All Measures All Modules reports. They are in the <drillthrough> tag between </output> and </cubereportbuilder> To access design mode using Browse 1. In Site Management / Manage Cube Registration and Security, select a cube from the list. 2. Click Browse. The design dialog box for the selected cube appears: August

34 Director s Station Administration Training Guide Notice that this is similar to the design view explained in the End User training guide (accessed via the Design button in the toolbar), except that here you start by selecting a cube and creating a report from scratch. When you click the Design button in an existing report, you have a report already defined and use the Design mode to modify it. In any of the delivered All Measures reports, all of the Available Hierarchies are displayed in the Drop Filter Fields Here box, because all of the available filters are displayed in the default reports. Since you are starting from scratch here, you need to drag and drop any and all rows, columns, and filter dimensions to areas in the report where you will use them. Using the Designer to create a new report To create a new report using the designer 1. Drag any of the Available Hierarchies that you want to use as filter dimension to the Drop Filter Fields Here box: 32

35 2. Drag any of the Available Hierarchies that you want to use as columns to the Drop Column Fields Here box. The most common dimension to place here is Measures. 3. Drag any of the Available Hierarchies that you want to use as rows to the Drop Row Fields Here box. 4. Click on any row or column dimension to limit the members you want to have available in the report. Any Dimension or Measure that is on the Drop Row Fields Here or Drop Column Fields Here can be limited to display only the members you are interested in by clicking on the desired dimension, causing the Filter box to appear: August

36 Director s Station Administration Training Guide 5. Use the check boxes to select desired fields than click OK to save and close. 6. Click OK at the bottom of the Available Hierarchies when you are finished. 34

37 Managing Categories, Menus, and My Folder Managing Categories Categories are the top-level listings seen in the Popout Menu. Administrators can create and edit custom categories, but it is strongly recommended that you not change or delete the delivered Categories. CAUTION Do not delete delivered categories. If you do, you cannot replace them. The Manage Categories window can only be accessed from the Popout Menu under Site Management / Manage Categories: System Categories All categories displayed in blue are System Categories which can not be deleted without editing the category and removing the "System Category" attribute. August

38 Director s Station Administration Training Guide Changing Order of Categories Category Members To change the order of the categories in the Popout Menu, select a category from the list and use the up or down arrows to move the selected category. By setting access you are dictating which groups will see each category on the menu. To manage category members 1. In the Manage Categories window, select the category you want to control access to. 2. Click the Category Members button to display the Category Members window: 3. Select any groups in the Non-Members column that should have access to this category and use the leftarrow to move them to the Members column on the left. 4. Select any groups in the Members column that should NOT have access to this category and use the rightarrow to move them to the Non-Members column on the right. 5. Click Save when complete to save your changes and be returned to the main Manage Categories window. 36

39 Note If you have made changes and would like to restore the values back to the default of All Groups, you must move all specific groups to the Non-Members column. Click Save and the category can then be viewed by all members of all groups. Managing Menus Adding Items Menus are the folders and subfolders that appear under the categories in the navigation Popout Menu. Administrators can add, edit, and delete folders, links, and documents to any category or existing folder. It is strongly recommend that you NOT delete any delivered menu items. Administrator(s)s can use the Manage Menu icon in the Popout Menu Bar to add items for any and all users. Any links, folders, or documents created here will be available to any user who accesses Director s Station. Links, folders and documents are saved to the menu in the same way that they are saved to My Folder, with one exception. The Manage Menu includes an Allow Anonymous option. When this option is selected, the item being registered is saved to the Popout Menu that displays on the login page, without requiring a login to access. The category and any sub-folders must also be anonymous for the link to be displayed without logging in. Any Director s Station report requires a user to login to access it, regardless of the anonymous setting. To add a new item to the menu 1. Click the Manage Menu icon in the Popout Menu Bar. The Manage Menu dialog box appears: August

40 Director s Station Administration Training Guide 2. Click Add Item: 3. Choose a appropriate tab to begin adding items: Links Add internal and external hypertext links Folders Add subfolders for organizing reports Documents Add any type of document CAUTION Never create a new cube. 38

41 To add a new folder to the menu 1. From Add Item, click the Folders tab: 2. Enter a Name for the folder. 3. For In Folder, select the folder or subfolder where the folder to reside. 4. Click Save. Note Top level category folders are managed in Manage Categories, which allows the management of a subfolder in a category. There is no limit to the number or depth of subfolders that can be added within a category. To add a new link to the menu 1. From Add Item, click the Links tab: August

42 Director s Station Administration Training Guide 2. Enter a Name for the link. 3. For In Folder, select the folder or subfolder where the link will reside. 4. Indicate whether the item will Allow Anonymous access. 5. Check whether the link is a Local Link or a Web link. 6. Enter the URL for the link. A local link includes the drive letter and path to an individual file on the Director s Station server. A Web link requires an prefix. 7. Add a Description if desired. 8. Click Save. 40

43 To add a new document to the menu 1. From Add Item, click the Documents tab. 2. Enter a Title for the document. 3. For In Folder, select the folder or subfolder where the document will reside. 4. Check whether the item will Allow Anonymous access or not. 5. Select the document Type, such as Excel, Word, PowerPoint, or Other. Any type of file can be selected. The type indicates what icon will be used on the menu. The icon is displayed is shown next to the type when a type is selected. If you set the type for Word document as Excel, Director s Station will notice and use the correct icon. The only time this is really important is when the document is a type that Director s Station doesn t recognize and you want to select an appropriate icon for display. 6. Locate the File. Use the Browse button to select a file on your local machine. Note When uploading documents it is easiest to start by selecting the file since some other fields will autopopulate based on the file information. To fill this field, type the path and file name or browse to the file you wish to upload. The Title and Type will then autopopulate. August

44 Director s Station Administration Training Guide 7. Add a Description, if desired. 8. Click Save. Note Administrator(s)s may want to limit the users who can upload documents since it may have an effect on bandwidth use and disk space. A loading box will appear while the document is being loaded. The time to load documents is directly related to the size of the file and the speed at which the data is transferred. If you are uploading a large file during a high traffic time, it may take a significant time to load. Sorting menu items By default all links on the menu are displayed in the order that they are created, placing the most recent at the bottom. However, administrators may change the organization of the menu: 1. Click the Manage Menu icon in the Popout Menu Bar. 2. Click on the link or sub-folder that you want to move. 3. Drag the item to another location. A black line displays to show where the item will be placed when the mouse button is released. 4. Drop the item when it is in the correct location. Rearrangement Rules: Managing My Folder You can move links from one folder to another. You can move links to other categories. You can move your subfolders. You can move subfolders into other subfolders. You CANNOT move categories from this menu. You CANNOT copy and paste links or subfolders. All users are able to upload, organize, and manage documents and reports for their personal My Folder category using Manage My Folder in Director s Station. Each sser has their own My Folder that no other user can access without that user s username and password. All of the user s information regarding reports and meters are saved here, as well as other possible links. By default Manage My Folder contains a My Folder folder and an subfolder. 42

45 To access Manage My Folder 1. Click the Manage My Folder icon in the Popout Menu Bar to open Manage My Folder: Adding Items 2. Click My Folder. To add a new item to My Folder 1. Click the Manage My Folder icon in the Popout Menu Bar. The Manage My Folder dialog box appears. 2. Click Add Item: August

46 Director s Station Administration Training Guide 3. Choose one of these tabs to begin adding items: Links Add internal and external hypertext links Folders Add subfolders for organizing reports Documents Add any type of document Note In addition the items listed here, you can also add reports, charts, and meters to your My Folder. To add a new folder to My Folder 1. From Add Item, click the Folders tab. 2. Enter a Name for the folder. 3. For In Folder, select the folder or subfolder where the folder will reside. (This should generally be My Folder.) 4. Indicate whether the item will Allow Anonymous access. 5. Click Save. To add a new link to My Folder 1. From Add Item, click the Links tab. 2. Enter a Name for the link. 3. For In Folder, select the folder or subfolder where the link will be stored. 4. Indicate whether the link is a Local Link or a web link. 5. Enter the URL for the link. A local link includes the drive letter and path to an individual file on the Director s Station server. A Web link requires an prefix. 6. Add a Description if desired. 7. Click Save. To add a new document to My Folder 1. From Add Item, click the Documents tab. 2. Enter a Title for the Document. 3. For In Folder, select the folder or subfolder where the document will be stored. 4. Select the document Type, such as Excel, Word, PowerPoint, or Other. Any type of file can be selected. The type indicates what icon will be used on the menu. The icon is 44

47 displayed is shown next to the type when a type is selected. If you set the type for Word document as Excel, Director s Station will notice and use the correct icon. The only time this is really important is when the document is a type that Director s Station doesn t recognize and you want to select an appropriate icon for display. 5. Locate the File. Use the Browse button to select a file on your local machine. Note When uploading documents it is easiest to start by selecting the File since other fields will auto-populate based on the file information. To fill this field, type the path and file name or browse to the file you wish to upload. The Title and Type will then auto-populate. 6. Add a Description, if desired. 7. Click Save. Note All uploaded documents are transferred over the Internet and stored in the application database. Administrator(s)s may want to limit the users who can upload documents since it may have an effect on bandwidth use and disk space. A loading box will appear while the document is being loaded. The time to load documents is directly related to the size of the file and the speed at which the data is transferred. If you are uploading a large file during a high-traffic time, it may take a significant time to load. Editing Items When editing links it helps to remember that all of the menu items are considered to be "links" once created in the menu. Thus, they are all edited in the same way. The link information is displayed and can be changed: 1. Click the Manage My Folder icon. 2. Click My Folder to display the items that may be edited. 3. Select the item you wish to edit. The item properties display in the white space on the left. 4. Click Edit, and make the desired changes. 5. Click Save. August

48 Director s Station Administration Training Guide Storing Items Deleting Items My Folder data can grow quickly and become unmanageable. You should use the Add Item, Folders option to develop a plan for storing your links, reports, charts, meters and documents. 1. Click the Manage My Folder icon. 2. Click My Folder to display the items that may be deleted. 3. Select the item you wish to delete. 4. Click Delete 5. Click OK to confirm. Note Deleting a subfolder will automatically delete all the links within this folder. Sorting menu items My Profile By default, all links in My Folder are displayed in the order that they are created with the most recently added at the bottom of the list. However, you may change the organization of the menu. 1. Click the Manage My Folder icon. 2. Find the link or sub-folder that you want to move. 3. Click the item you want to move. 4. Drag the item to another location. A black line appears where the item will be placed when the mouse button is released. 5. Drop the item when it is in the correct location. All users, except administrators, can use My Profile to change their: To do this: name address password 1. Click the Manage My Folder icon in the Popout Menu Bar. 2. Click My Folder: 46

49 3. Select My Profile: 4. Make whatever changes are needed. 5. Click Save to save your changes. Note The My Profile option is not available for the sirsi or administrator login, or any user in the Admin group. August

50 Director s Station Administration Training Guide 48

51 Manage Reports Managing Reports Administrators have access to all of the reports in the Director s Station and can make changes to the reports or delete them. Only administrators have access to the Manage Reports page. Users with the Reports: XML Writer right can make modifications to the report XML as well, from the Edit Report option on each report menu. All reports can be edited via Site Management / Advanced / Manage Reports. By default, the reports are grouped by cube or database, referred to as the Source: Changing the Display You can easily change the display by selecting the menu available from the down-arrow associated with each column: 1. Click the down-arrow next to Report Name 2. Determine which columns to include in the display by pointing to the columns option and selecting the columns you want to display, as shown here: August

52 Director s Station Administration Training Guide Note Drag and drop the columns to change the order, and use the bars between the column headers to resize the columns. Each column allows you to sort in ascending or descending order. 3. Click the Report Name column header to sort the column in either ascending or descending order. Note As long as the Show in Groups is selected, the sort is at the group level. 4. Unselect Show in Groups to display and sort the entire column of Report Names: 50

53 5. Select the Visibility column down-arrow and select the Group By This Field option. The reports are displayed by whether they are Public (which means shared to a public folder), or whether they are Private (which means that they are saved to a user s My Folder): August

54 Director s Station Administration Training Guide Using the Reports Menu In the Reports Administration toolbar, in the Reports pull-down menu, you can edit, execute, and delete reports. Even more advanced options are also available: If you become familiar with the report XML, you can use the New Report option to create new reports. You can also use Report Dependencies to see relationships in custom reports that have been created that contain more than one report. To use any of these report options, except New Report, first select the report you want to work with, then select the menu option you desire to use. To edit a report When you edit a report you are accessing the report s XML and manually updating the XML code. Typically, only an administrator would do this for reasons such as unlocking a locked report. To edit a report: 1. Highlight the report that you want to edit. 2. Click the Reports button down-arrow. 3. Select Edit Report. 4. Make the desired changes and do one of the following: Click Save to make the changes and to return to Report Administration. Click Save and Execute to make the changes and show the report in the Director s Station user interface. Click Cancel to make no changes and to return to Report Administration. 52

55 To execute a report Executing a report displays it in the Director s Station user interface as if it had been selected from a menu or a SwiftView. 1. Highlight the report that you want to execute. 2. Click the down-arrow next to Reports. 3. Select Execute Report. Note You can also highlight the report and double-click it to execute it. To delete a report Deleting a report from My Folder or elsewhere in the Popout Menu, or from SwiftLinks, only removes the links to the report. The report is still available. For example, a user may a report to another user and then remove it from his My Folder and SwiftLinks, but the user who receives the will still be able to access the report until the report is removed here by the administrator. Outside of Report Administration, a report is never truly removed until it has been removed using this Report Administration window. When an administrator uses Delete Report in Report Administration, the report is completely removed and cannot be recovered. Just as deleting the links to reports does not actually remove the reports, deleting a report in Report Administration does not remove the links to the report from SwiftLinks or from the Popout Menus, such as My Folder. Users still need to remove the link in these locations themselves. If someone tries to use links to access a report that has been deleted, they see this message: To delete a report in Report Administration: 1. Highlight the report or reports that you want to edit using the shift-click method to highlight sequential reports and the control-click method to highlight out of sequence reports. August

56 Director s Station Administration Training Guide 2. Click the down-arrow next to Reports. 3. Select Delete Reports. 4. In the confirmation window, click Yes to complete the deletion or No to cancel the deletion. Additional Tools on the Reports Toolbar These additional Tools are available for you to use: Import/Export allows you to export a report from one Director s Station database into another. Templates allow you to create additional templates that will be available in the Layout Templates available on each report. You can also manage existing templates. Filter allows you to search the list of existing reports for a particular report name. The name has to match exactly, and for delivered reports, the translation key (such as _all_catalog_measures) needs to be searched. You can also select to exclude private reports and include variable reports which are not delivered or derived from delivered reports. 54

57 Systems Administration This section is specifically for the systems administrator who will be responsible for the day to day success of the Director s Station. Managing Application Settings Only administrators have access to the Manage Settings page. The Director s Station application settings govern the use of the application. All settings can be edited via the Site Management / Advanced / Manage Settings link or manually by accessing the settings file on the Director s Station server at this location: C:\Program Files\SwiftKnowledgeInc\SwiftKnowledgeV8\ SKSites\<VirtualDirectoryName>\SKsettings.xml CAUTION Do not edit these settings unless you fully understand the implications of your changes. Editing these settings can cause Director s Station to not function. General Tab Settings are divided into functional areas that are separated by tabs in the application: August

58 Director s Station Administration Training Guide The General tab contains the following settings: Organization Name The default is SirsiDynix. You should change this to your licensed organizational name. The name entered here will appear at the top of all reports: Login Text This field contains the text that is displayed on the top of the login page to the left of the SwiftKnowledge logo. By default this field is left blank. There is no limit to the length of text that can be placed here. Limited HTML tags can be used: Login Message This field contains the text that is displayed on the login page directly below the user name and password boxes. There is no limit to the length of text. The text will automatically wrap if needed. As is illustrated in the example above, limited HTML tags are supported. 56

59 Password Minimum Length This field contains the minimum length for user passwords. The number refers to the minimum number of characters required. The default is 5 characters. CAUTION NEVER set this number to 0. Setting this to 0 will allow users to register without a password. However, the login screen requires both a user name and a password to be typed in. Therefore, a user with no password can not log in. Password Expiration (Days) This field contains the Password Expiration Interval. The number represents the number of days that will pass before a user password that is set to expire will expire. CAUTION NEVER set this number to 0. When the password expiration date is set to 0, a user s password expires the instant they change it. This forces the user into a loop requesting that they change their password over and over and never allowing them to log in. Ajax Timeout (Seconds) This field determines how long Director s Station will try to access your server and get results before timing out. The default is 120 seconds. Allowed Languages This field provides the language behavior for the application. If the field is left blank, no languages will be available from the login page and the user s browser language will be used if that language exists. all Makes all languages in the Director s Station database available. August

60 Director s Station Administration Training Guide en, all All languages are available and a default language is set. The default language is represented by a two character language code. en, fr Makes available the languages that are listed (in this case English and French). The first language in the list is taken as the default. The languages are represented by their two character language code and separated by commas. For a language to be available it must also exist in the Director s Station database. Initial View This field determines which SwiftView the user will use upon log in. This only takes effect if Force Initial View (below) is checked. If a user belongs to more than one group, the first initial SwiftView listed will be the one that will open as default. Multiple dashboards can be entered separated by a comma or a semicolon. Force Initial View This field works in conjunction with the Initial View (above) setting. Check to enable. When this element is disabled, a user that is a member of a group that has an initial SwiftView will display the group level SwiftView unless they have created a My SwiftView at which time the My SwiftView will always be displayed at login. When this element is enabled, the group level SwiftView is forced to restore regardless of the existence of a My SwiftView. Hide Start Pages This field is used to control the display of the user defined pages that are available under each Category in the Popout Menu. Start Page Text may be defined when managing categories. 58

61 Reports Tab The Reports tab contains the following settings: Include Empty Default This field only affects the default settings of a report. Since all of the All Measures reports are already saved with Empty behavior defined, this setting is only evident when a new report is built directly from the cube Browse option. Checked suppresses empty rows. Unchecked shows empty rows. CSV Delimiter This field specifies the default value for comma separated files that are exported to Excel. The default for U.S. English Windows locale is a comma. In other Windows locales, such as Spain, the expected list separator is a semicolon. Use this setting to modify the data that is exported so that the list separator is the desired value. Default Page Size (Rows) This field determines the number of rows that will be returned in a report at a time. Hide Measure Groups In Analysis Services each Measure is a member of a Measure Group. This field determines whether each measure is found under its measure group or whether the Measure Group is hidden and each measure displays at the top level. You should keep this checked. Although it is safe to uncheck this if you want to see what effect it has, your reports will generally look better if you keep this checked. August

62 Director s Station Administration Training Guide Tab If you want to the ability to information from Director s Station your administrator needs to: Set up this screen with your SMTP server information. Setup a task scheduler to run the skmailer.exe. Setup Return Address and Application URL settings for this feature to work. The tab contains the following settings: Server Address This field is only used if you want the ability to meters. A valid mail server name must be used. ing meters also requires Return Address and Application URL settings. Port This field contains the port that is used for . It defaults to 25. Use SSL This field determines whether you want to use encrypted . It is disabled, by default. Username This field contains the address that may be required by your SMTP mail server. Password This field contains the password that may be required by your SMTP mail server. Return Address This field contains the address to be used for the "From" line when ing meters. E- mailing meters also requires Server Address and Application URL. This does not actually have to be a valid address. 60

63 Advanced Tab Application URL When ing reports or meters, a URL is created and passed as a link to your mail browser. By default, Director s Station will get the URL for this link from the user s browser. However, since different users will need to use different URLs depending on their location, the URL entered here will override the default. If used, the URL in this box should represent the URL that most users would use to access Director s Station. If this field is blank the default is used. Send Embedded Images This field determines whether embedded images may be sent. The Advanced tab contains the following settings: Session Keep-Alive The default setting for this field is false. When set to false, the user session terminates when the SessionTimeOut threshold has been reached. This is determined by the user not interacting with the server for the set amount of time. Setting this value to true, the user session will never be terminated automatically. Duplicate Users The default for this field is set to true. A setting of true allows a single user login to be used multiple times concurrently. A setting of false does not allow a user to login more than once at the same time.. OLAP Connection Pool This field manages connections to the cubes. The default for this field is set August

64 Director s Station Administration Training Guide Managing User Sessions to true. The default setting should not be changed unless you are instructed by SirsiDynix. Maximum Users This field limits the number of users that can be logged into Director s Station. If you have user license restrictions, this setting is ignored. Manage User Sessions allows administrators to see and interact with users that are currently logged in. To see who is online or send messages to online users: 1. In the Popout Menu, open Site Management / Advanced / Manage User Sessions. The Manage User Sessions window opens with a user list at the top showing information about each user currently logged in and their environment: Managing Log Files 2. Select a User or users to whom you wish to send a message. 3. Type a message into the text box. 4. Click Send Message. All users selected will be sent the typed message the next time they refresh their browser or navigate to another page. Director s Station generates log files for a number of reasons: All user logins are recorded as successful or unsuccessful. All internal components running are logged at runtime. 62

65 All memory management triggers are logged. All errors found in SQL, Analysis Services, or IIS are logged. All problems encountered are logged. Most often users are unaware that logging is taking place. When an issue is created that prevents a user request from completing, a generic error message appears, such as the following: The requested action is unable to complete at this time, please try again later. This error in itself gives little detail to the administrator; however, any time this error is displayed, a log is created. You can navigate to and view the actual log files where they are located on the web server at: C:\Program Files\SwiftKnowledgeInc\SwiftKnowledgeV8\ SKSites\DirectorsStation\SKLogs You can use Windows explorer and Notepad to view these logs on the web server. However, it is easier to view and manage these logs through the Manage Logs component of Director s Station. To view and manage these logs through the Manage Logs component of Director s Station, open Site Management / Advanced / Manage Logs: When managing logs through Director s Station, the log files are listed in order of the last modified date. Since the log files are often named for internal purposes, the modified date is the only real indicator an administrator has to determine what log file is August

66 Director s Station Administration Training Guide associated with a particular problem. Therefore, it is easiest to locate a log file when you can reproduce the problem you have encountered and then access the log files immediately. More information about each log can be seen by selecting the desired log and clicking the View button. Log entries can be deleted by selecting the entries you wish to delete and clicking the Delete button. Note It is recommended that administrators periodically (weekly to monthly) delete old log files to conserve space on the server. Understanding the Structure of Director s Station A snapshot of the Unicorn database is taken for use in Director s Station by running the Extract Director s Station Data 64

67 (datainterchng) report in WorkFlows. Files that contain data on acquisitions, authority, charges, bills, holds, reserves, requests, serials, and users are created. Also produced are files on bibliographic information, zip codes, history logs, web logs, and policies. These files are FTPed to the Director s Station server. If a remote OPAC server is used, there is another process on that server to send weblog files to the Director s Station server. Within the Director s Station server, this data is processed. OLAP or Online Analytical Processing cubes are created from the data. These cubes are managed by Analysis Services. Scripts run nightly to process the files brought over by the report and to process the OLAP cubes. The information processed within the Director s Station server allows you to run delivered or custom reports on your own data using your Director s Station, which is accessed by a Web browser. Keeping Director s Station Running Smoothly Part 1 Confirm that the Data is Current and Correct The first indicator that something is wrong is going to be the Refresh date on the Director s Station reports. 1. Open Director's Station and log in. 2. From the Popout Menu, select Collection Analysis / All Measures All Modules, or click on an existing report in the SwiftLinks panel of My DirectorsStation Dashboard. 3. Display the reports for each of the modules you currently use in Unicorn. There are two ways to see the last time the data has been processed. Click on the toolbar and the Refreshed Date displays on the upper-right corner: August

68 Director s Station Administration Training Guide Click on the toolbar and the Refreshed Date displays in the middle of other informative data: 4. On reports that show daily activity, like All Checkin Measures, use this method to check for currency of data: a. Click the drop-down arrow for the "FY Jan Dec" button. b. Select the current year and click it. c. Select the latest quarter and click it. d. Select the latest month and click it. e. Select the last date (which should be the same date as is on the current Histlogs file). This is typically one day prior to the refresh date: It is important to not let your system get out of date. If you do not use the Director s Station every day, it should be someone s responsibility to log on and check the Refresh Date and the latest Transaction Date. If the refresh date is not current, review the 66

69 following target areas to see where the process may have faltered. Part 2 Extract Director s Station Data (datainterchng) Report The Extract Director s Station Data (datainterchng) report needs to be run nightly on the Unicorn Server. When the report begins running, it sends the information shown below to the finished list with a status of OK. For example, the following message appears: Found finished.done file on Director's Station Server. Verify that DTS has finished and if necessary remove the finished.done file. This means that the ETL (Extract Transform Load) did not run on the Director s Station server. Any errors that occur in the report will appear at the beginning. Watch for failed FTP transactions. A failed FTP transaction is marked by the following message: ** FTP status=error. Contact Client Care if the Extract Director s Station Data (datainterchng) report shows any of these messages. Note This check can be done quickly and easily by doing a text scan for the words ERROR and ABNORMAL each day. Report Log for Director's Station Data Interchange Report datainterchng scheduled as $<datainterchng> Director's Station Data Interchange Starting Data Interchange as a batch process. Run ds_ved.pl - Ved extracts. Run export/ftp script for authority Run export/ftp script for bill Run export/ftp script for billpaymnt Run export/ftp script for booking Run export/ftp script for callnum Run export/ftp script for catalog Run export/ftp script for charge Run export/ftp script for course Run export/ftp script for dist Run export/ftp script for fund Run export/ftp script for fundcyc Run export/ftp script for funding Run export/ftp script for hold Run export/ftp script for holdblanket Run export/ftp script for invline Run export/ftp script for invoice Run export/ftp script for item Run export/ftp script for order Run export/ftp script for orderline Run export/ftp script for request Run export/ftp script for resctl August

70 Director s Station Administration Training Guide Run export/ftp script for reserve Run export/ftp script for serctl Run export/ftp script for user Run export/ftp script for userstatus Run export/ftp script for vendor Run export/ftp script for vendorcyc Additional logs will be added when the report has finished. UNICORN catalog selection started on Wednesday, July 9, 2008, 2:26 PM The catalog file will be read sequentially by primary key. The catalog key will be written to standard output. The display-formatted author will be written to standard output. The title key will be written to standard output. *** SQL *** SELECT catalog_key,marc,marc_file,format FROM catalog ORDER BY catalog_key *** SQL *** catalog record(s) considered catalog record(s) selected. UNICORN catalog selection finished on Wednesday, July 9, 2008, 2:46 PM UNICORN orderline selection started on Wednesday, July 9, 2008, 2:46 PM The orderline file will be read sequentially by primary key. The orderline key will be written to standard output. 1 orderline record(s) considered. 1 orderline record(s) selected. UNICORN orderline selection finished on Wednesday, July 9, 2008, 2:46 PM UNICORN user selection started on Wednesday, July 9, 2008, 2:46 PM The user file will be read sequentially by primary key. The user key will be written to standard output. SELECT user_key FROM users ORDER BY user_key *** SQL *** *** SQL *** user record(s) considered user record(s) selected. UNICORN user selection finished on Wednesday, July 9, 2008, 3:01 PM UNICORN Print User started on Wednesday, July 9, 2008, 2:46 PM The user key will be read from standard input. Flat user records will be written to standard output user record(s) printed. UNICORN Print User finished on Wednesday, July 9, 2008, 3:01 PM records printed. FTP files to DS server started on Wed Jul 9 15:02:25 PDT ** Sending policies in ascii mode. ** File successfully transfered : policies. ** Sending strings.pol in ascii mode. ** File successfully transfered : strings.pol. ** Sending catalog in ascii mode. ** File successfully transfered : catalog. ** Sending segment.txt in ascii mode. ** File successfully transfered : segment.txt. ** Sending useradd.txt in ascii mode. ** File successfully transfered : useradd.txt. ** Sending zipcode in ascii mode. ** File successfully transfered : zipcode. FTP files to DS server finished on Wed Jul 9 15:02:58 PDT Process HIST files started on Wed Jul 9 15:02:58 PDT Copy /s/sirsi/unicorn/logs/hist/ hist.z. Mode = binary Sending hist.Z. Status = DONE Squeeze /s/sirsi/unicorn/logs/hist/ hist to hist.Z. Mode = binary Sending hist.Z. Status = DONE Copy /s/sirsi/unicorn/logs/stat/ stat.z. Mode = binary 68

71 Sending stat.Z. Status = DONE Squeeze /s/sirsi/unicorn/logs/stat/ stat to stat.Z. Mode = binary Sending stat.Z. Status = DONE Process HIST files finished on Wed Jul 9 15:04:12 PDT Process WEBLOG files started on Wed Jul 9 15:04:12 PDT Create previous month from weblog.Z... cat: Cannot open /s/sirsi/unicorn/webcat/logs/200806*.weblog. Create current month from weblog.Z... cat: Cannot open /s/sirsi/unicorn/webcat/logs/200807*.weblog. Mode = binary Sending weblog.Z. Status = DONE Mode = binary Sending weblog.Z. Status = DONE Process WEBLOG files finished on Wed Jul 9 15:04:13 PDT Export authority started on Wed Jul 9 14:26:55 PDT UNICORN Export authority file started on Wednesday, July 9, 2008, 2:26 PM Authority records will be read from the authority.dat file. Authority records will be written to Data/authority.txt formatted for DS authority record(s) read authority record(s) written. UNICORN Export authority file finished on Wednesday, July 9, 2008, 2:27 PM FTP authority.txt started on Wed Jul 9 14:27:38 PDT ** SENDING: ascii file authority.txt. ** FTP status=done. FTP authority.txt finished on Wed Jul 9 14:27:42 PDT Export authority finished on Wed Jul 9 14:27:42 PDT 2008 Export bill started on Wed Jul 9 14:26:55 PDT UNICORN Directors station export bill file started on Wednesday, July 9, 2008, 2:26 PM Bill records will be read from the bill database. Bill records will be written to Data/bill.txt formatted for DS. ' ' will be the output delimiter bill record(s) read bill record(s) written. UNICORN Directors station export bill file finished on Wednesday, July 9, 2008, 2:30 PM FTP bill.txt started on Wed Jul 9 14:30:37 PDT ** SENDING: ascii file bill.txt. ** FTP status=done. FTP bill.txt finished on Wed Jul 9 14:31:03 PDT Export bill finished on Wed Jul 9 14:31:03 PDT 2008 Export billpaymnt started on Wed Jul 9 14:26:55 PDT UNICORN Directors station export billpaymnt file started on Wednesday, July 9, 2008, 2:26 PM Billpaymnt records will be read from the billpaymnt file. Billpaymnt records will be written to Data/billpaymnt.txt formatted for DS. ' ' will be the output delimiter billpaymnt record(s) read billpaymnt record(s) written. UNICORN Directors station export billpaymnt file finished on Wednesday, July 9, 2008, 2:27 PM FTP billpaymnt.txt started on Wed Jul 9 14:27:13 PDT ** SENDING: ascii file billpaymnt.txt. ** FTP status=done. FTP billpaymnt.txt finished on Wed Jul 9 14:27:14 PDT Export billpaymnt finished on Wed Jul 9 14:27:14 PDT 2008 Export booking started on Wed Jul 9 14:26:55 PDT UNICORN Export booking file started on Wednesday, July 9, 2008, 2:26 PM Booking records will be read from the CISAM booking.dat file. Booking records will be written to Data/booking.txt. Booking xinfo records will be written to bookingxinfo. ' ' will be the output delimiter 0 booking record(s) read. 0 booking record(s) written. August

72 Director s Station Administration Training Guide 0 bookingxinfo(s) read. 0 bookingxinfo(s) written. UNICORN Export booking file finished on Wednesday, July 9, 2008, 2:27 PM FTP booking.txt started on Wed Jul 9 14:27:07 PDT ** SENDING: ascii file booking.txt. ** FTP status=done. FTP booking.txt finished on Wed Jul 9 14:27:08 PDT Export booking finished on Wed Jul 9 14:27:08 PDT 2008 Export callnum started on Wed Jul 9 14:26:55 PDT UNICORN Export callnum file started on Wednesday, July 9, 2008, 2:26 PM Callnum records will be read from the CISAM callnums.dat file. Callnum records will be written to Data/callnum.txt formatted for DS. ' ' will be the output delimiter callnum record(s) read callnum record(s) written. UNICORN Export callnum file finished on Wednesday, July 9, 2008, 2:34 PM FTP callnum.txt started on Wed Jul 9 14:34:11 PDT ** SENDING: ascii file callnum.txt. ** FTP status=done. FTP callnum.txt finished on Wed Jul 9 14:35:05 PDT Export callnum finished on Wed Jul 9 14:35:06 PDT 2008 Export catalog started on Wed Jul 9 14:26:55 PDT UNICORN DS export catalog files started on Wednesday, July 9, 2008, 2:26 PM Catalog records will be read (Fixed for lang/cop). Catalog records will be written to Data/catalog.txt formatted for DS. ' ' will be the output delimiter catalog record(s) read catalog record(s) written. 0 headingved record(s) read. 0 headingved records(tags) written. 0 marclist record(s) read. 0 marclist records(tags) written marc record(s) read marc records(tags) written. UNICORN DS export catalog files finished on Wednesday, July 9, 2008, 2:43 PM FTP catalog.txt started on Wed Jul 9 14:43:27 PDT ** SENDING: ascii file catalog.txt. ** FTP status=done. FTP catalog.txt finished on Wed Jul 9 14:43:39 PDT Export catalog finished on Wed Jul 9 14:43:40 PDT 2008 Export charge started on Wed Jul 9 14:26:55 PDT UNICORN Export charge file started on Wednesday, July 9, 2008, 2:26 PM Charge records will be read from the CISAM charge.dat file. Charge records will be written to Data/charge.txt. ' ' will be the output delimiter charge record(s) read charge record(s) written. UNICORN Export charge file finished on Wednesday, July 9, 2008, 2:29 PM FTP charge.txt started on Wed Jul 9 14:29:58 PDT ** SENDING: ascii file charge.txt. ** FTP status=done. FTP charge.txt finished on Wed Jul 9 14:30:22 PDT Export charge finished on Wed Jul 9 14:30:22 PDT 2008 Export course started on Wed Jul 9 14:26:55 PDT UNICORN Export course file started on Wednesday, July 9, 2008, 2:26 PM Course records will be read from the CISAM course.dat file. Course records will be written to Data/course.txt. Course xinfo records will be written to coursexinfo. ' ' will be the output delimiter 0 course record(s) read. 0 course record(s) written. 0 coursexinfo(s) read. 0 coursexinfo(s) written. UNICORN Export course file finished on Wednesday, July 9, 2008, 2:27 PM FTP course.txt started on Wed Jul 9 14:27:07 PDT ** SENDING: ascii file course.txt. ** FTP status=done. FTP course.txt finished on Wed Jul 9 14:27:08 PDT

73 Export course finished on Wed Jul 9 14:27:08 PDT 2008 Export dist started on Wed Jul 9 14:26:55 PDT UNICORN Export dist file started on Wednesday, July 9, 2008, 2:26 PM Dist records will be read from the CISAM dist.dat file. Dist records will be written to Data/dist.txt. ' ' will be the output delimiter 2 dist record(s) read. 2 dist record(s) written. UNICORN Exportdist file finished on Wednesday, July 9, 2008, 2:27 PM FTP dist.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file dist.txt. ** FTP status=done. FTP dist.txt finished on Wed Jul 9 14:27:08 PDT Export dist finished on Wed Jul 9 14:27:08 PDT 2008 Export fund started on Wed Jul 9 14:26:55 PDT UNICORN Export fund file started on Wednesday, July 9, 2008, 2:26 PM Fund records will be read from the CISAM fund.dat file. Fund records will be written to Data/fund.txt. Fund xinfo records will be written to extendedinfo. ' ' will be the output delimiter 6069 fund record(s) read fund record(s) written. 0 fund xinfo(s) read. 0 fund xinfo(s) written. UNICORN Export fund file finished on Wednesday, July 9, 2008, 2:27 PM FTP fund.txt started on Wed Jul 9 14:27:07 PDT ** SENDING: ascii file fund.txt. ** FTP status=done. FTP fund.txt finished on Wed Jul 9 14:27:07 PDT Export fund finished on Wed Jul 9 14:27:07 PDT 2008 Export fundcyc started on Wed Jul 9 14:26:57 PDT UNICORN Export fundcyc file started on Wednesday, July 9, 2008, 2:26 PM Fundcyc records will be read from the CISAM fundcyc.dat file. Fundcyc records will be written to Data/fundcyc.txt. ' ' will be the output delimiter 6069 fundcyc record(s) read fundcyc record(s) written. UNICORN Export fundcyc file finished on Wednesday, July 9, 2008, 2:27 PM FTP fundcyc.txt started on Wed Jul 9 14:27:06 PDT ** SENDING: ascii file fundcyc.txt. ** FTP status=done. FTP fundcyc.txt finished on Wed Jul 9 14:27:07 PDT Export fundcyc finished on Wed Jul 9 14:27:07 PDT 2008 Export funding started on Wed Jul 9 14:26:57 PDT UNICORN Export funding file started on Wednesday, July 9, 2008, 2:26 PM Funding records will be read from the CISAM funding.dat file. Funding records will be written to Data/funding.txt. ' ' will be the output delimiter 2 funding record(s) read. 2 funding record(s) written. UNICORN Export funding file finished on Wednesday, July 9, 2008, 2:27 PM FTP funding.txt started on Wed Jul 9 14:27:07 PDT ** SENDING: ascii file funding.txt. ** FTP status=done. FTP funding.txt finished on Wed Jul 9 14:27:08 PDT Export funding finished on Wed Jul 9 14:27:08 PDT 2008 Export hold started on Wed Jul 9 14:26:57 PDT UNICORN Export hold file started on Wednesday, July 9, 2008, 2:26 PM Hold records will be read from the CISAM hold.dat file. Hold records will be written to Data/hold.txt. ' ' will be the output delimiter hold record(s) read hold record(s) written. UNICORN Export hold file finished on Wednesday, July 9, 2008, 2:27 PM FTP hold.txt started on Wed Jul 9 14:27:24 PDT ** SENDING: ascii file hold.txt. ** FTP status=done. FTP hold.txt finished on Wed Jul 9 14:27:26 PDT Export hold finished on Wed Jul 9 14:27:26 PDT 2008 August

74 Director s Station Administration Training Guide Export holdblanket started on Wed Jul 9 14:26:57 PDT UNICORN Export holdblanket file started on Wednesday, July 9, 2008, 2:26 PM Holdblanket records will be read from the CISAM holdblanket.dat file. Holdblanket records will be written to Data/holdblanket.txt. ' ' will be the output delimiter 0 holdblanket record(s) read. 0 holdblanket record(s) written. UNICORN Export holdblanket file finished on Wednesday, July 9, 2008, 2:27 PM FTP holdblanket.txt started on Wed Jul 9 14:27:07 PDT ** SENDING: ascii file holdblanket.txt. ** FTP status=done. FTP holdblanket.txt finished on Wed Jul 9 14:27:07 PDT Export holdblanket finished on Wed Jul 9 14:27:07 PDT 2008 Export invline started on Wed Jul 9 14:27:02 PDT UNICORN Export invline file started on Wednesday, July 9, 2008, 2:27 PM Invline records will be read from the CISAM invline.dat file. Invline records will be written to Data/invline.txt. Invline xinfo records will be written to extendedinfo. ' ' will be the output delimiter 0 invline record(s) read. 0 invline record(s) written. 0 invline xinfo(s) read. 0 invline xinfo(s) written. UNICORN Export invline file finished on Wednesday, July 9, 2008, 2:27 PM FTP invline.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file invline.txt. ** FTP status=done. FTP invline.txt finished on Wed Jul 9 14:27:08 PDT Export invline finished on Wed Jul 9 14:27:08 PDT 2008 Export invoice started on Wed Jul 9 14:27:05 PDT UNICORN Export invoice file started on Wednesday, July 9, 2008, 2:27 PM Invoice records will be read from the CISAM invoice.dat file. Invoice records will be written to Data/invoice.txt. Invoice xinfo records will be written to extendedinfo. ' ' will be the output delimiter 0 invoice record(s) read. 0 invoice record(s) written. 0 invoice xinfo(s) read. 0 invoice xinfo(s) written. UNICORN Export invoice file finished on Wednesday, July 9, 2008, 2:27 PM FTP invoice.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file invoice.txt. ** FTP status=done. FTP invoice.txt finished on Wed Jul 9 14:27:08 PDT Export invoice finished on Wed Jul 9 14:27:08 PDT 2008 Export item started on Wed Jul 9 14:27:03 PDT UNICORN Export item file started on Wednesday, July 9, 2008, 2:27 PM Item records will be read from the CISAM item.dat file. Item records will be written to Data/item.txt. Item xinfo records will be written to itemxinfo. ' ' will be the output delimiter item record(s) read item record(s) written. 0 item xinfo(s) read. 0 item xinfo(s) written. UNICORN Export item file finished on Wednesday, July 9, 2008, 2:40 PM FTP item.txt started on Wed Jul 9 14:40:12 PDT ** SENDING: ascii file item.txt. ** FTP status=done. FTP item.txt finished on Wed Jul 9 14:42:26 PDT Export item finished on Wed Jul 9 14:42:28 PDT 2008 Export order started on Wed Jul 9 14:27:05 PDT UNICORN Export order file started on Wednesday, July 9, 2008, 2:27 PM Order records will be read from the CISAM order.dat file. Order records will be written to Data/order.txt. Order xinfo records will be written to extendedinfo. ' ' will be the output delimiter 1 order record(s) read. 72

75 1 order record(s) written. 0 order xinfo(s) read. 0 order xinfo(s) written. UNICORN Export order file finished on Wednesday, July 9, 2008, 2:27 PM FTP order.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file order.txt. ** FTP status=done. FTP order.txt finished on Wed Jul 9 14:27:08 PDT Export order finished on Wed Jul 9 14:27:08 PDT 2008 Export orderline started on Wed Jul 9 14:27:03 PDT UNICORN Export orderline file started on Wednesday, July 9, 2008, 2:27 PM Orderline records will be read from the CISAM orderline.dat file. Orderline records will be written to Data/orderline.txt. Orderline xinfo records will be written to extendedinfo. Orderline segment records will be written to segments. ' ' will be the output delimiter 1 orderline record(s) read. 1 orderline record(s) written. 0 orderline xinfo(s) read. 0 orderline xinfo(s) written. 0 orderline segments(s) read. 0 orderline segments(s) written. UNICORN Export orderline file finished on Wednesday, July 9, 2008, 2:27 PM FTP orderline.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file orderline.txt. ** FTP status=done. FTP orderline.txt finished on Wed Jul 9 14:27:08 PDT Export orderline finished on Wed Jul 9 14:27:08 PDT 2008 Export request started on Wed Jul 9 14:27:04 PDT UNICORN Export request file started on Wednesday, July 9, 2008, 2:27 PM Request records will be read from the CISAM request.dat file. Request records will be written to Data/request.txt. Request xinfo records will be written to requestved. ' ' will be the output delimiter 1445 request record(s) read request record(s) written. 0 requestved(s) read. 0 requestved(s) written. UNICORN Export request file finished on Wednesday, July 9, 2008, 2:27 PM FTP request.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file request.txt. ** FTP status=done. FTP request.txt finished on Wed Jul 9 14:27:08 PDT Export request finished on Wed Jul 9 14:27:08 PDT 2008 Export resctl started on Wed Jul 9 14:27:06 PDT UNICORN Export resctl file started on Wednesday, July 9, 2008, 2:27 PM Resctl records will be read from the CISAM resctl.dat file. Resctl records will be written to Data/resctl.txt. Resctl xinfo records will be written to resctlxinfo. Resctl copy records will be written to resctlcopy. ' ' will be the output delimiter 0 resctl record(s) read. 0 resctl record(s) written. 0 resctl xinfo(s) read. 0 resctl xinfo(s) written. 0 resctl copy(s) read. 0 resctl copy(s) written. UNICORN Export resctl file finished on Wednesday, July 9, 2008, 2:27 PM FTP resctl.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file resctl.txt. ** FTP status=done. FTP resctl.txt finished on Wed Jul 9 14:27:08 PDT Export resctl finished on Wed Jul 9 14:27:08 PDT 2008 Export reserve started on Wed Jul 9 14:27:03 PDT UNICORN Export reserve file started on Wednesday, July 9, 2008, 2:27 PM Reserve records will be read from the CISAM reserve.dat file. Reserve records will be written to Data/reserve.txt. ' ' will be the output delimiter 0 reserve record(s) read. August

76 Director s Station Administration Training Guide 0 reserve record(s) written. UNICORN Export reserve file finished on Wednesday, July 9, 2008, 2:27 PM FTP reserve.txt started on Wed Jul 9 14:27:07 PDT ** SENDING: ascii file reserve.txt. ** FTP status=done. FTP reserve.txt finished on Wed Jul 9 14:27:08 PDT Export reserve finished on Wed Jul 9 14:27:08 PDT 2008 Export serctl started on Wed Jul 9 14:27:06 PDT UNICORN Export serctl file started on Wednesday, July 9, 2008, 2:27 PM Serctl records will be read from the CISAM serctl.dat file. Serctl records will be written to Data/serctl.txt. Serctl xinfo records will be written to serctlxinfo. ' ' will be the output delimiter 0 serctl record(s) read. 0 serctl record(s) written. 0 serctl xinfo(s) read. 0 serctl xinfo(s) written. UNICORN Export serctl file finished on Wednesday, July 9, 2008, 2:27 PM FTP serctl.txt started on Wed Jul 9 14:27:08 PDT ** SENDING: ascii file serctl.txt. ** FTP status=done. FTP serctl.txt finished on Wed Jul 9 14:27:08 PDT Export serctl finished on Wed Jul 9 14:27:08 PDT 2008 Export user started on Wed Jul 9 14:27:07 PDT UNICORN Export user file started on Wednesday, July 9, 2008, 2:27 PM User records will be read from the CISAM user.dat file. User records will be written to Data/user.txt formatted for DS. ' ' will be the output delimiter user record(s) read user record(s) written. UNICORN Export user file finished on Wednesday, July 9, 2008, 2:45 PM FTP user.txt started on Wed Jul 9 14:45:16 PDT ** SENDING: ascii file user.txt. ** FTP status=done. FTP user.txt finished on Wed Jul 9 14:46:04 PDT Export user finished on Wed Jul 9 14:46:05 PDT 2008 Export userstatus started on Wed Jul 9 14:27:07 PDT UNICORN Export userstatus file started on Wednesday, July 9, 2008, 2:27 PM Userstatus records will be read from the CISAM userstatus.dat file. Userstatus records will be written to Data/userstatus.txt. ' ' will be the output delimiter userstatus record(s) read userstatus record(s) written. UNICORN Export userstatus file finished on Wednesday, July 9, 2008, 2:28 PM FTP userstatus.txt started on Wed Jul 9 14:28:36 PDT ** SENDING: ascii file userstatus.txt. ** FTP status=done. FTP userstatus.txt finished on Wed Jul 9 14:28:52 PDT Export userstatus finished on Wed Jul 9 14:28:52 PDT 2008 Export vendor started on Wed Jul 9 14:27:07 PDT UNICORN Export vendor file started on Wednesday, July 9, 2008, 2:27 PM Vendor records will be read from the CISAM vendor.dat file. Vendor records will be written to Data/vendor.txt. Vendor xinfo records will be written to extendedinfo. Vendor address records will be written to address. ' ' will be the output delimiter 1287 vendor record(s) read vendor record(s) written. 0 vendor xinfo(s) read. 0 vendor xinfo(s) written. 0 vendor address(s) read. 0 vendor address(s) written. UNICORN Export vendor file finished on Wednesday, July 9, 2008, 2:27 PM FTP vendor.txt started on Wed Jul 9 14:27:09 PDT ** SENDING: ascii file vendor.txt. ** FTP status=done. FTP vendor.txt finished on Wed Jul 9 14:27:09 PDT Export vendor finished on Wed Jul 9 14:27:09 PDT 2008 Export vendorcyc started on Wed Jul 9 14:27:07 PDT

77 UNICORN Export vendorcyc file started on Wednesday, July 9, 2008, 2:27 PM Vendorcyc records will be read from the CISAM vendorcyc.dat file. Vendorcyc records will be written to Data/vendorcyc.txt. ' ' will be the output delimiter 2574 vendorcyc record(s) read vendorcyc record(s) written. UNICORN Export vendorcyc file finished on Wednesday, July 9, 2008, 2:27 PM FTP vendorcyc.txt started on Wed Jul 9 14:27:09 PDT ** SENDING: ascii file vendorcyc.txt. ** FTP status=done. FTP vendorcyc.txt finished on Wed Jul 9 14:27:09 PDT Export vendorcyc finished on Wed Jul 9 14:27:09 PDT 2008 Start Sending Finished File. ** Sending finished.done in ascii mode. ** File successfully transfered : finished.done. Done Sending Finished File. Part 3 Checking the ETL (Extract Transform Load) To confirm whether or not the data transformation was successful, perform the following steps, go to: Popout Menu Bar / Site Management / Director s Station Reports / Latest ETL Details: August

78 Director s Station Administration Training Guide The details of the latest ETL process should be void of error messages. An example of a good ETL process without errors is given below: Note The ETL will run regardless of any problems that it may encounter during the process. Administrators need to check on the ETL status frequently to ensure that the data is being processed correctly and in a timely manner. Part 4 Contact Client Care If the Refresh Dates and report data are not current, the datainterchng report contains errors or abnormal listings, or the ETL contains any errors, contact SirsiDynix Client Care for assistance. Backing Up the Director s Station There are several options for backing up the Director s Station data: Full System Backup Automated Backup Scripts Backup Directory Scenario 1: Full System Backup The easiest backup scenario is to back up the entire system to a removable storage device. In the event of a failure, the system can be restored to the latest saved backup. This option requires more expensive hardware and a standard system backup routine. 76