Web2

1. Web2 Review and Troubleshooting

2. Topics • Overview of main customizable files • Troubleshooting techniques • FAQs

3. Initial list of schools • ITC name comes from dasite parameter of dasite_env.pl • District name copied from “dist” line of schools.txt • A single apostrophe will cause problems with the welcome screen eg. St. Mary’s should be spelled as St. Marys. • Sirsi logo is controlled by “U” at the beginning of the “dist” line in schools.txt • Email address is from emailsupport parameter of dasite_env.pl • Javascript can sometimes be obstinate about refreshing. Note: Any changes to schools.txt or dasite_env.pl requires that you run infohio.pl and refresh the webpage.

5. Initial list of schools (opened) • Each building name is directly copied from schools.txt • Building URL is generated as Unicorn or MultiLIS as dictated by first character U/M of building line in schools.txt • Location of welcome page is generated from building code in schools.txt • The address portion of the URL is generated based on the webname parameter of dasite_env.pl. It is recommended that you use the registered name not the IP address of your webserver Note: Any changes to schools.txt or dasite_env.pl requires that you run infohio.pl and refresh the webpage.

7. Building Welcome Page • Building name generated from building line of schools.txt • Mascot line generated from dist_web.txt matching on either the district code or building code. • No line generated when no match • Dist_web.txt file is required but can be empty • URL setting key of Unicorn or unicorn_jr generated from “U” in schools.txt • URL setting key for specific building generated from building code in schools.txt and must equal the setting key paragraph coded in web2.set Note: Any changes to schools.txt or dist_web.txt requires that you run infohio.pl and refresh the webpage.

9. Easy Search • To filter holdings for a building, the Unicorn library policy code must be used in the setting key paragraph of web2.set: • Default_library • Highlight_library • Setting key home_library must point to a server target that is defined in the server section of web2.set • If it does not match exactly, hits could be returned from server 1home – see Options section of web2.set • If you consistently get 0 hits or not responding • Home_library value correct in that building’s setting_key? • Address/port correct in home_library server definition? • Is Sirsi Netserver running – auto_haltrun status? • Is user WEBSERVER registered in Unicorn? Note: Any changes to web2.set requires that you cycle Web2. Note: Documentation on web2.set is in the Web2 Management Guide

11. Advanced Search • To filter on one or any number of buildings in advanced search, the *membership parameter in web2.set setting key must equal the code used in advancedlibraries.html • If you received no hits, examine the values of the select statements in advancedlibraries.html – they must exactly equal the library policy codes entered into Unicorn. • Be sure to include a select line for ALL so that the whole district can be searched. • You can also include any search groups that have been defined in Unicorn search groups. • The parameter at the end of each select line is the exact text you will see in your dropdown menu. Note: Any changes to advancedlibraries.html or web2.set requires that you cycle Web2.

13. More Libraries • More libraries is your opportunity to create targets and groups of targets for searching outside of one's district. For targets to show up in the drop down menu, they must be • defined as a server or server_group in web2.set • must be listed in the specifically named more_libraries server_group in Web2.set • If you choose to create a group of libraries, eg. noacsc_libraries, you can create this server_group then include this group in the more_libraries server group and your users will be able to search a group of libraries without selecting them individually • Target servers can include multilis, unicorn, and publicly available Z39.50 servers. Defining Z39.50 targets is beyond the scope of this refresher training but can be reviewed in Web2 documentation Note: Any changes to web2.set requires that you cycle Web2.

15. More Libraries (cont.) • More libraries is also the opportunity for you to provide to your library patrons, any additional information or links that you wish to provide to the public. Otherlibraries.html can be coded by you using standard html coding standards. • It will best compliment the top section of the page by using a table that is 700 wide or two columns of 350. • Another tip is to employ the target parameter of the href when linking to a site outside of web2 so a new browser window opens. Note: Any changes to otherlibraries.html requires that you cycle Web2.

17. Reading Programs • To show the checkbox for checking building codes (526 subfield 5) for quizzes, make sure the *checkreadprog=yes is in the setting key section of web2.set for that building. • Be sure the indxreadprog is being run nightly to generate the 595 tag from the 526 tag. It is actually the 595 tag that is being searched in the reading program search. Note: Any changes to web2.set requires you to cycle web2.

18. My Account • To make the my account button available on the header you must have *circulation=yes in your setting_key for that building. • For my account to work, the value of the setting_key circserver parameter must match a valid patron_server definition in the server section of web2.set. • Still not getting user info? • Does the patron_server definition have the correct address and port? • Is the netserver is running on the server? • Is the webserver user registered? Note: Any changes to web2.set requires that you cycle Web2.

20. Bookbag • The maximum number of items that can be placed in the bookbag at one time (with one click) is controlled by max_cart_limit in the Options section of Web2.set. However, this does not limit how many total items can be placed in the bookbag on multiple clicks. • You can email the contents of a bookbag. If you wish to let a patron email the list only, set *emailist=yes in the setting_key section for that building. If you wish the patron to be able to send a comment along with the list, then *emailmsg=yes must also be included in the setting_key section. • For security purposes, email addresses set in from:, cc:, etc. are defined in web2.set and cannot be altered by html. This is an attempt to thwart the casual hacker from being able to “hijack" Web2 emails. Note: Any changes to web2.set requires that you cycle

22. Navigating Cat/Cat Jr. Using the banner icon to move back and forth between CAT and CAT Jr. relys on the default_library parameter in Web2.setting keys sections being equal to the name of the setting keys. For this reason only, the name of the setting_key paragraph and the default_library in that paragraph must be equal. Note: Any changes to web2.set requires that you cycle Web2.

23. Logging out of CAT • When you log out of CAT or CAT Jr. the welcome screen reappears. But remember that a welcome screen is building specific. The way that this is handled is by coding the welcome_screen=/login/avel/welcome.html parameter in the setting_keys for this building. The building code here must be equal to the one found in schools.txt. • The session_timeout parameter in the Options section of web2.set dictates how long in seconds that Web2 will allow an active session to remain open before automatically logging the session out. The next time any click is activated after session_timeout will cause the welcome screen to be displayed. Again the welcome_screen parameter will say which welcome screen is used. • However, the welcome_screen parameter is a persistent screen value. If the user exits Web2 to another website, then comes back to Web2 but does not execute a search, the persistent values are allowed to expire when the idle timeout logs this session out. That is why sometimes, when a search screen times out, it goes to the a "Expired" screen which says to click here to go to the initial list of schools. Note: Any changes to web2.set requires the Web2 be cycled. Any changes to schools.txt requires that infohio.pl be rerun.

24. Content enrichment • Content enrichment is "fetched" from a live server in Atlanta based on the first ISBN that is presented to it from the MARC record. There have been INFOhio reported cases when the "wrong" ISBN is not in the content database but actually in the MARC record. Please ask yourself: • does searching for the ISBN number at resources such as amazon.com, barnes&noble.com, google, or LOC, concur that the content is wrong? • is the ISBN in the MARC record suspect? • Are there are multiple ISBNs in the record? Could a reordering of the ISBNs resolve the problem? • If the MARC record is suspect, was its source the INFOhio Union Catalog? If so, this needs to be reported so that the UC record can be corrected.

25. Content enrichment (cont) • Content providers: • Syndetics – all content except below • CLCD – points to another website • Cahners – reviews only • Any one of the three vendors could be down and only some of the content would not be available. And when you find incorrect content, all three vendors are not necessarily incorrect • When reporting bad content, please attempt some of the above checking and verify which content was incorrect

26. FAQs • You may need to change the IP address of the webserver that houses Web2. You can work with your networking group to determine if this will impact the IIS definitions for Web2. • Web2 specific files that may be impacted are webname parameter in dasite_env.pl - this should not be affected if you use the recommended registered name rather than the IP. • If there is a firewall between Web2 and your Sirsi K-12 server, have networking check that as well for needed changes. Note: Any changes to dasite_env.pl requires that you run infohio.pl and refresh the list of schools.

27. FAQs (cont.) • If you wish to migrate web2 to another webserver, the program will need to be reinstalled. Generally, you can use the latest available distribution files to: • install the software on the new webserver • define Web2 to IIS • copy all files that have been modified by you from the old webserver to the new • rerun infohio.pl and startup Web2 Note: For specifics, please open a helpdesk ticket.

28. FAQs (cont.) • Searching Techniques • Filters and indexes are not equal. Information that is indexed means that this field is searchable within web2. A filter only applies to a list of titles that have already been identified as meeting the search criteria. See Searching Strategies doc for list of filters vs. indices. • GL3.1 boolean searching – a boolean operator can now be included in phrase searching by including the word in double quotes.

29. FAQs (cont.) • Complex searching is usually at the request of librarians. While we do hope the OPAC can serve the librarians as well as the patrons, our target audience is actually patrons. Please consider having your librarians explore the use of the report, CAT: Shelflist for constructing topical book lists. Any search that they can execute in Web2, they should be able to execute in WF and with CAT: Shelflist. To determine what to use in Reports, execute the search on Web2 and review the hitlist page to see the exact anatomy of the search. • Example search: finn {TI} and twain {AU} and river {SU} • Possible access points: AU, TI, SU, SER, PBYR, READPROG, CURR, any tag name (505, 500, 690, etc)

30. FAQs (cont)Inconsistencies and Issues • Netscape/Mozilla/Firefox vs. Internet Explorer - Web2 html was written to work with Internet Explorer. However it is a public interface and we cannot dictate what browsers users will use. On most screens in IE, the enter key will behave as if you clicked on whichever search button was highlighted on the page. However, the "other" browsers use the first submit button defined on the page. In some cases, this is the clear text or other button. We are aware of this anomaly but have not had the development time to address it. We hope to see progress this year. • Diacritics are still not showing properly in Web2 or Workflows. This is a data problem that we hope to correct within the next 6 months.

31. FAQs (cont)Inconsistencies and Issues (cont) • Easy/Advanced vs. More Libraries - The intention of More libraries was to allow a user to expand their search beyond their own district and look at other catalogs regardless of where they were located. This capability is available to use through the employment of the Z39.50 standard. However, realize that z39.50 only deals in USMARC 21 records. Therefore Sirsi fields are not available to us through this protocol. The record type icons and filters in this environment can only be interrogating MARC information and therefore cannot use Unicorn’s material type or item group to filter searches. • Visual Search was provided to us as is in the Web2 environment. To understand why a specific search from, say, the animal page is different than the same search on the stories page, you simply need to conduct the search and review the resulting hitlist to see what search strings were used in each case. We are reviewing these for more consistency, but they were not necessarily meant to be exactly the same across topics.