Andornot Newsletter – March 2011

by Kathy Bryce Thursday, March 24, 2011 2:06 PM

Please check out the latest issue of our newsletter.


Andornot News

Latest Andornot Projects

  • Société historique de Saint-Boniface Upgrades Archives Search Interface and Launches Voyageurs Contracts Database
  • WorkSafeBC Launches Mobile Version of Library Catalogue
  • Horizon Health Network - 4 catalogues - search individually or all at once
  • RCHC launches a new site look and implements site searches with dtSearch

Inmagic News: DB/TextWorks and WebPublisher Pro v13

Andornot on the Road: Conferences and Inmagic Training and Ideas Days

Blog Posts for Developers

Tweets of Interest

Tips and Tricks

  • Anatomy of a Genie Add-In
  • F11 - a little known keyboard option
  • @Date - for new acquisitions lists
  • Accented Characters

Cool Tools: IE9 and Firefox4

Please contact us for further information or to be added to our newsletter list.

DB/TextWorks Manuals

by Denise Bonin Tuesday, March 15, 2011 4:29 PM

HelgaThere was a time in the not too distant past when each release of a software program came with a printed manual.  The ones from Inmagic, featuring a cover with Helga adding to the information highway, were well-thumbed treasures, enhanced with highlighter pens, sticky notes, doodles or emblazoned with the owners name.  They were taken to their owners beds, savoured on the bus, and even treated to long lingering baths.  Such was the life of a prized manual before the age of the green economy. 

Librarians and archivists seemed to be particularly obsessed with these print manuals and rue the day when they were no longer shipped.  Did we ever hear about it!  But there are PDF versions produced we announced or online help available at the click of a button; where you need it, when you need it.  To please some users, we even went so far as to print and bind the manuals from the PDF version.  Thankfully, it seemed that most users resigned to accept this change in technology and moved on. 

When the last PDF version of the DB/TextWorks manual was published for version 9, but no longer shipped with the product, we put up a link on our website, so that students and new users could still have the pleasure of reading and yes, occasionally printing sections to take on delightful little trips.  We were asked if there was going to be an update, when versions 10, 11 and 12 were released, but alas there were none.

With the release of Version 13, a new age has dawned.  It’s back to the future.  Inmagic  has decided to produce a PDF version of the Help file.  There should be joy in the land again.  This gem can be found on the Inmagic Extranet under Product Documentation.  It is fully searchable with your PDF reader and you can even print all 425 pages if you want.  Inmagic has even called it a “Printed Help File” to somehow appease the paper-hungry crowd.  However, to save trees, you might just read and search this on your computer or perhaps just print small parts of it, double-sided. 

Also with the release of version 13, DB/TextWorks online help is now using a WebHelp format. This format is compatible with the newer Microsoft operating systems, and can be accessed from the server hosting DB/TextWorks in a multi-user environment.

I would love to hear feedback on printed vs. online manuals.   Do you still dream of owning a printed DB/TextWorks manual?  What is your favourite manual story?  Did you ever leave your copy on a bus or drop it in the tub? 

Andornot @ SLAIS – One Day DB/TextWorks Workshop a Success

by Jonathan Jacobsen Monday, March 14, 2011 11:38 AM

On Saturday, March 12, 2011, Andornot conducted the annual DB/TextWorks training session for the student chapter of SLA at SLAIS, the library and archival school at the University of British Columbia.

As in previous years, about two dozen MLIS and MAS students came out for this Saturday session. Many had prior experience with DB/TextWorks from past jobs and co-op placements, or were actively using it in a current class, but all wanted a more solid understanding of its features and how to use them.

In the morning session, we came at the software as newbie users, learning how to search and edit records. In the afternoon we put on our database designer hats and created a simple database for managing oral histories – audio recordings and transcriptions.

To cover all the features of DB/TextWorks in one day is a lot to take in, but thanks to regular infusions of sugar from a tray of donuts, we all made it through.

We look forward to next year’s session, and are available any time to provide training on any Inmagic product.

How to replace those long canned query URLs with short, memorable ones

by Jonathan Jacobsen Monday, March 14, 2011 10:45 AM

Andornot has long recommend using canned queries into your databases as a means of surfacing information for users. On a web-accessible database, a canned query takes the form of a URL with some search terms in it that retrieve records from the database with a single click. Common uses are to retrieve:

  • new items added to a database, such as the latest books catalogued in a library, or latest legal memos in a law firm database;
  • items on a particular subject in a library catalogue, or a finding aid for a particular archival fonds;
  • a list of all journals, maps, DVDs, etc. in a library catalogue.

By constructing the search for the user, we can guide them towards new, interesting or relevant resources in a collection, and help new users in particular to quickly and easily see what the database contains. From there, users can begin their own searching, knowing what sort of information and keywords to use.

Andornot provides a web-based Search Cannery Wizard to help you construct URLs that will search your database. By filling in fields on this form, you can create a URL such as the following, which searches the sample library catalogue database included in our Andornot Starter Kit for all the journals:

This is a very useful URL to be able to give a user. This one in particular can be given to new staff to ask which titles they’d like routed to them. There are just a couple potential problems with the URL:

1. It’s long and in some email clients, the text will wrap to a second line and the link will be broken.

2. The URL isn’t easily read to decipher what it might lead to (unlike, say,, which can be predicted to lead to our website).

URL Rewriting

A great solution to these two issues is to use a technique known as URL rewriting to replace the lengthy URL with a shorter, friendlier one, such as

This short URL is easily read and can be predicted to lead to a list of journals in the starter kit sample database.

A short URL like this can be emailed to colleagues or published on an intranet. When the web server receives a request for this “page” in the website, it translates it into the longer URL that performs the canned query. This all happens behind the scenes, so while the user immediately sees the list of journals, only the friendly URL remains in their browser address bar.

The permalink portion of the URL is a common term used to indicate that the URL will be around for a while and the user can reliably bookmark it. Though it’s not strictly necessary, it helps to differentiate these types of URLs from ones that correspond to folders in the website.

URL rewriting is also a great technique for linking to specific records in a database. For example, this short URL Record leads to the catalogue record for the Architectural Record journal. The link can be generated using the unique ID or number that every record in a database should have, and a rewrite rule that translates it into a search.

Real-World Examples

The Law Society of Saskatchewan Library has a series of short, friendly URLs set up to retrieve the latest works from their catalogue in different legal practice areas. The URLs also correspond to the RSS feeds set up in the same way. Both provide a means for lawyers to stay abreast of new items of interest to them, whether by bookmarking a short URL, or by subscribing to the RSS feed.

Here are a few examples:

More are listed on this page, along with the RSS feeds (which are described in detail in this blog post).

The Provincial Resource Centre for the Visually Impaired (PRCVI) runs most of their website content from an Inmagic database (we blogged about this here). We recently replaced lengthy canned query URLs with short, friendly ones, such as:

These URLs are easily emailed to the students and teachers that PRCVI serves, yet always retrieve the latest information from their database.

Detailed instructions for setting up URL rewriting is provided below for DIY types who like to roll up their sleeves and get hands-on with their server. If you’d like our assistance, please contact us – we’d be happy to help you take advantage of this simple technique to improve service to your users.


URL Rewriting – How To Do It

diyCaution: technical jargon ahead!

URL rewriting can be set up in IIS, the Microsoft web server, quite easily. In IIS 7, for example, you would download and install the URL Rewriting module from Microsoft, if it’s not already installed, then set up rewrite rules such as this one:



<rule name="Journals">

<match url="^permalink/journals" />

<conditions logicalGrouping="MatchAll" />

<action type="Rewrite" url="/results.aspx?AC=qbe_query&amp;TN=starter&amp;RF=WebBrief&amp;DF=WebFull&amp;DL=0&amp;RL=0&amp;NP=255&amp;MR=10&amp;QY=find+MaterialType+=Journal" />




As you can see, this rule takes an incoming URL that matches this


and translates it to this


which is a canned query into a sample database that finds all records which are journals.

Note that you could still use the Andornot Search Cannery Wizard to construct this URL.

Here’s one that can take a URL that includes a unique record ID and a title, such as Record and translate it into a search for a specific record in the database, using a regular expression (RegEx), to parse the ID and title from the URL .

<rule name="Permalink">

<match url="^permalink/([0-9]+)/(.*)" />

<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />

<action type="Rewrite" url="/results.aspx?AC=qbe_query&amp;TN=starter&amp;RF=WebFullPURL&amp;DF=WebFullPURL&amp;DL=0&amp;RL=0&amp;NP=255&amp;MR=10&amp;QY=find+RecordId+%3d{R:1}" />


In the above, the title is discarded and the unique record ID is used as a parameter in a search.

Rewrite rules can be added through the IIS management console GUI, or simply by editing your web application’s web.config.

You can learn more about the IIS 7 URL Rewrite module and download it here.

In IIS 6, we recommend using the open-source URL rewriting module available from Instructions are provided for installing and configuring the module and making appropriate entries in your web application’s web.config file. Once installed, rules similar to those shown above for IIS 7 may be used. For example, this rule can be used to link to a specific record in a database.

<urlrewritingnet defaultPage = "default.aspx" xmlns="" >


<add name="Permalink" virtualUrl="^~/permalink/([0-9]+)/?default.aspx"



ignoreCase="true" />



Other Rewrite Rules

In addition to rewrite rules to link to a specific record and to replace long canned query URLs, we recommend that you set up two more additional rules, to add or remove trailing slashes, and to convert all URLs to lower case.

To a human and a web server, and are similar, but to a search engine, they are quite different. It's a good idea to set up a rule to consistently add or remove the trailing slash, to improve search engine ranking.

The same applies to mixed upper and lower case in URLs – it’s a good idea to enforce all lower case so that the page appears as one to a search engine. Examples of these rules may be found here:

Month List