Customizing Horizons Views: A Sampling

1. Customizing Horizons Views: A Sampling Steven J. Orton Education Services

2. MQ Views MQ stands for Marquis which was one of the original names for Horizon software. • Views control the interaction between the data and the users. • Be careful when changing the views. If available use a training database first. • Record your changes in the Customization database.

3. Why Modify MQ Views? • To remove redundant redundant data. • To re-arrange the order of data. • To supply default data. • To provide the lists of data needed.

4. Why Modify List Displays? • To add or remove default elements. • To re-arrange the order display elements. • To change the default width of a display element. • To add or remove column headers. • To change a code display element to the code or the description.

5. Why Modify Edit Displays? • To add or remove elements. • To re-arrange the order of the elements • To enter default data.

6. Why Edit Linked Views? • To remove or add related edit links. • To fix views after upgrades. • To make staff happy. • To post a complaint and then the fix on horizon_l.

7. Some Examples • BIB Date Search • Checkout Screen • Item Editing for one location • Reserve Book Room • Item-based Collection Development

8. Bib Date Search • Acquisitions staff and Catalogers want a way to review titles added on a certain date or a range of dates. • Your library uses the status field on the bib and wants a simple way to search for records with a specific status. • You want to batch change the status on a group of bib records.

9. Creating the Bib Date Search View • Open the table editor. • Enter mq_view for your search. • Using the table index search for “bib_control.” • Copy the bib_control record. • Change the name of the view to something unique like “bib_date_search.” • Change the view type to “General.” • Click the secured button. • Click the Save button.

10. Bib_Date_Search: The List View • Add the elements to the list view as shown here:

11. Bib_Date_Search: The Edit View You can change the items to edit or leave it with the copied portions.

12. Bib_Date_Search: The Navigation Bar • After you create a custom view, you can create a shortcut on the navigation bar or on the toolbar for that view. • Decide which Preference Group to change. • Make a copy of the Table Editor. • Change the Label and Icon as needed. • Move the Process to an appropriate place on the navigation bar. • In the Arguments field enter “/v” and the name of the view. For example, “/vBib_Date_Search”. • Use the “/e” for expanded search. • Set up Security so others can use the process.

13. Checkout Screen • When you checkout an item the system lists data about the checkout. Sometimes it displays more data than you need. • It is redundant for systems with only one library to display the location of the item, the location of borrower, the location of the transaction. • A library may want to display the price of the item when checking it out. • If you don’t display the check-in notes at check out, you lose the chance to inform the borrower of specific issues about the item you are checking out.

14. Item Editing for One Location • Your library has item catalogers at separate locations. • You want the location to add items for their own locations and not others. • You want the item catalogers to edit their own items and not items that belong to other locations.

15. SQL View for the Item Creation by Location • Many of the alternate views are based on SQL views. The SQL to create the tables contains the limits. Sometimes the tables are based on location, other times it might be collection code or itype. • Make sure you include all required columns of the table when creating an alternate view.

16. The SQL to Create the SQL View create view item_southas select item#, ibarcode, bib#, location, collection, call, call_reconst, copy, copy_reconst, volume, source, price, creation_date, last_update_date, last_inventory_date, notes, fast_add_flag, delete_flag, itype, item_status, cki_notes, last_cko_date, n_ckos, borrower#, due_date, due_time, n_pieces, n_renewals, n_phone_renewals, reserve_date, saved_location, saved_itype, saved_collection, saved_call, saved_call_reconst, saved_copy, saved_copy_reconst,saved_n_ckos, owning_instructor#, withdraw_catalog_action, withdraw_instruction,proxy_borrower#, copy#, staff_only, internal_note, call_type, saved_call_type, last_status_update_date, n_opac_renewals, csa_call, csa_reconst, timestamp, cko_location, last_cko_time, n_inhouse_uses, last_inhouse_use_date, call_reconstructed, copy_reconstructed from item where location = "South"

17. Copy the Mq View • Change the code. • Change the table name to match your SQL view. • Change the Window Title.

18. The Copied View

19. Changing the Default • Change the default location.

20. Create a View Set • A View Set can be assigned to a user.

21. Assign the View Set

22. Reserve Bookroom View • The use counts for items placed are moved to a field called “saved_n_ckos”. • The counts (n_ckos) are set to 0. • The total count is a combination of the two.

23. The SQL View for Reserve Bookroom create view iliff_rbras /* View created by Steven Orton of Dynix for Iliff-- April 2005 */ select t.processed, t.reconst, r.instructor, r.i_reconst, c.name_reconstructed , r.bib#, r.reserve_date, r.withdraw_date, r.reactivate_date, r.creation_date, 'reserve_ckos' = i.n_ckos, 'previous_ckos' = i.saved_n_ckos, 'total_ckos' = i.n_ckos + i.saved_n_ckos, i.call_reconstructed, i.ibarcode, i.copy_reconstructed from rbr_ict_view r, item i, title t, course c where i.bib# = r.bib# and r.bib# = t.bib# and r.course# = c.course# and i.location = 'mainres'

24. The MQ View for Reserve Bookroom • Add the Columns to the List View, but not to the Edit View—report only.

25. The Reserve Bookroom MQ View

26. Collection Development View • You can include derived data in a view: • Publication Date • Days Old • Sit Days • Ranking

27. Create a view for the Pubdate create view sjo_pubdate as select bib#, 'Pubdate' = substring(text, patindex ('%[0-9]%[0-9]%[0-9]%[0-9]%',text),4) from bib where tag = '260' and charindex (char(31)+'c',text)< patindex ('%[0-9]%[0-9]%[0-9]%[0-9]%',text) • This Pubdate SQL View can be used in many of your SQL reports. • It displays only 4 digits.

28. Create the SQL View for the Collection Development • create view sjo_item_review • as • /* custom view created for collection development by Steven Orton of SirsiDynix */ • select • i.item#, ibarcode, i.bib#, i.location, collection, call, call_reconst, • copy, copy_reconst, volume, source, price, creation_date, • last_update_date, last_inventory_date, notes, fast_add_flag, • delete_flag, itype, item_status, cki_notes, last_cko_date, last_cko_time, • n_ckos, last_inhouse_use_date, n_inhouse_uses, • i.borrower#, proxy_borrower#, due_date, due_time, n_pieces, • n_renewals, n_phone_renewals, reserve_date, copy#, call_type, • internal_note, last_status_update_date, staff_only, • n_opac_renewals, processed, reconst, owning_instructor#, • withdraw_catalog_action, withdraw_instruction, cko_location, i.timestamp, • 'use_ranking' = (10000*n_ckos)/ ((select datediff (dd, "1 Jan 1970", getdate ()))-creation_date), • 'days_old' = convert(int,((select datediff (dd, '1 Jan 1970', getdate ()))-creation_date)), • 'shelf_days' = case • when last_cko_date is null and last_inhouse_use_date is null • then ((select datediff (dd, '1 Jan 1970', getdate ()))-creation_date) • when last_inhouse_use_date is not null and last_cko_date is null • then ((select datediff (dd, '1 Jan 1970', getdate ()))-last_inhouse_use_date) • when last_inhouse_use_date > last_cko_date • then ((select datediff (dd, '1 Jan 1970', getdate ()))-last_inhouse_use_date) • when last_inhouse_use_date <= last_cko_date • then ((select datediff (dd, '1 Jan 1970', getdate ()))-last_cko_date) • when last_cko_date > 0 • then ((select datediff (dd, '1 Jan 1970', getdate ()))-last_cko_date) • end, • enroute_to = convert (varchar (7), • isnull( rc.location, isnull (rq.pickup_location, i.location) ) ), • rq.pickup_location, request_timestamp = rq.timestamp, recall_timestamp = rc.timestamp, p.pubdate, 'title' = t.processed • from item i, title t, request rq, recall rc, sjo_pubdate p • where t.bib# =* i.bib# • and p.bib# =* i.bib# • and rq.item# =* i.item# • and rq.request_status in (1,2) • and rc.item# =* i.item# • /* End of the view */

29. The MQ View for Collection Development

30. Collection Development--Add the Display Columns

31. The Collection Development MQ View