CODI 2005 – Day Two (am)

Now You’ve Bought Web Reporter, So What? …So You’ve Bought Web Reporter, Now What? (Thurman Smith – thurman.smith@sirsidynix.com)

As we’ve just put our order in for Web Reporter, I’m trying to attend as many of the Web Reporter sessions as possible!

Thurman based his session on one he runs regularly (that should be freely available on the SirsiDynix web site?)

Here are my notes…

  • Web Reporter has over 100 general reports built in
  • due to differing databases, some of the delivered reports are broken but support are able to fix them
  • desktop client software used by Web Reporter admins, but end users use the web portal (i.e. web browser)
  • Web Reporter comes with 3 levels of users:
    • Web Reporter User â€“ least powerful, can run/print reports (but cannot export to Word/Excel)
    • Web Analyst â€“ also export reports, can create reports from a template (but not from scratch)
    • Web Professional â€“ also create reports from scratch, can save new reports to the public folders (where other users can access them)
  • …there’s also an Administrator login, but it wasn’t too clear when this should be used
  • Web Reporter monitors the named users (rather than simultaneous users), but (ignoring ethics, etc) several users could share the same named login
  • because MetaData is stored in the Horizon database, it gets backed up when you run your main Horizon backup process
  • terminology:
    • facts â€“ columns in the database that contain numeric data that it makes sense to run calculations against (e.g. age, number of CKOs) â€“ facts are not displayed in reports, but are wrapped in metrics
    • attributes â€“ all other columns (e.g. borrower name
    • metrics â€“ calculations on facts (e.g. the number of times a book has been checked out in a month)
    • filters â€“ return a subset of results that make sense (e.g. filter by certain borrower types), this is the same as the SQL “where” clause
    • prompts â€“ allow you to create an option that allows the user to specify specific choices (e.g. which locations do you want to run the report against?)
  • you can create new folders for each user, location, etc and then copy the reports that they want into them
  • some of the Web Reporter reports duplicate Horizon Item Editor reports
  • reports can be easily manipulated â€“ e.g. “page by” location can be dragged down into the report to show all locations in a single report (but only Web Analyst/Pro can do that)
  • to print reports, use the built-in Web Reporter print icon rather than using the web browser print button
  • Web Reporter uses a cache, so that running the same report again will display the cached version â€“ but the administrator can define how long the cached version is valid for (i.e. how long before it becomes stale)
  • metrics must always appear on the right-hand side of the report â€“ you can add more than one metric to a report
  • if you modify one of the default reports, then you should save it to a new folder (or it might get overwritten by a project upgrade)
  • you need OLAP services to get the full functionality (do we even have this?!?!?)
  • easy to add totals to a report
  • you can view the SQL that runs by looking at the “report details” (in one of the drop-down menus)
  • the look & feel for each report can be easily changed using “auto styles”
  • for reports that take a long time to run, use the subscription options to schedule the report to run:
    • make sure that the schedule times are realistic (i.e. not the every 15 minute default)
    • scheduled reports sit in the cache waiting to be viewed
    • try to avoid running scheduled reports at the same time as Day End, etc
    • to email reports to the user, you need to use NarrowCast
  • NarrowCast might be an optional extra purchase (I don’t remember it being listed in our Web Reporter quote – I hope we get it!!!)
  • you need to be careful not to filter by too many options, otherwise you might end up with no results
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

%d bloggers like this:
https://daveyp.wordpress.com/2005/11/08/codi-200t5-day-two-am/
daveyp.wordpress.com
crawl=CC-MAIN-2018-22
56311
application/http; msgtype=response
sha1:O5I7DNQBZM3PQ6WD4QRSWOID5RGB4NLS
<urn:uuid:6db45a2a-681d-4be9-a722-0e324fc04bd0>
2018-05-25T18:35:20Z
192.0.78.13
text/html
sha1:ZZXLAKXHPIDKI3UQMQ2RCQY4ZK74EMTT
<urn:uuid:6f864cb3-d9b7-4ab1-9ee8-b3f5a600db75>
https://daveyp.wordpress.com/2005/11/08/codi-200t5-day-two-am/
length
response
<urn:uuid:ba65aa3d-a162-497e-89d1-01c485442c72>
robots: classic
hostname: ip-10-228-146-143.ec2.internal
software: Nutch 1.6 (CC)
isPartOf: CC-MAIN-2018-22
operator: Common Crawl Admin
description: Wide crawl of the web for May 2018
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf