Inmagic DB/Text for SQL and Inmagic WebPublisher PRO version 14 released

by Kathy Bryce Wednesday, July 03, 2013 8:32 AM

All clients with a current Inmagic maintenance subscription for either DB/Text for SQL or WebPublisher PRO should soon be receiving an email from Inmagic with the download information for version 14.  Version 14 of the non SQL version of DB/TextWorks was released last year.

If you have a current maintenance subscription but have not received a notification email in the next week, please email advantage@inmagic.com with your serial number and email address so it can be resent.  Please also remember to let us know if your contact information has changed so we can update our records and pass this on to Inmagic.

New and enhanced features in WebPublisher PRO include:

  • Support for renaming query logs and starting new ones on a scheduled basis.
  • Ability to edit validation lists.
  • Ability to expose the Find button and disable find-as-you-type in InmagicBrowse.
  • InmagicBrowse can now update records after a validation term is changed to another term already in the list.
  • Improved support for Internet Explorer v10.

Please contact us if you would like assistance upgrading or would like to renew an expired maintenance subscription. We can also help you update your current interface to include the latest features available in the software itself, or with our add-on products.

How to Use the DB/TextWorks Runtime Version for Read-Only Searching

by Kathy Bryce Monday, June 10, 2013 6:19 PM

The DB/TextWorks runtime version is a free, search-only version of the non-SQL DB/TextWorks.  It’s a useful tool for providing access to a textbase just for searching.   Originally it was a popular way of distributing a textbase on a CD, but now it's often used in these scenarios:

  • Archives or library reading rooms with no internet or network access.
  • Very small law firm libraries without an intranet for staff searching.
  • Prisons or correctional institutes where the inmates have no internet or network access or there is concern about tampering with the data.
  • One time anniversary projects to distribute searchable copies of a textbase.

Although there are multiple ways of publishing DB/TextWorks textbases on the web or intranet, we still regularly get requests for assistance with setting up runtime instances, so we’ve written up the following guidelines and best practices.

The first step in any runtime implementation is to read the DB/TextWorks online Help.  Search for “runtime” and read the licensing section, how to install the software and what to give end users or transfer to the PC where it is to be installed.  You will need to have downloaded the runtime installation kit from the Inmagic extranet.  Depending on the version this was included in the DB/TextWorks download zip file and appears as a  \runtime folder, or more recently it is available as a separate download.  Login using the credentials from your most recent emailed download notification from Inmagic to download the install kit.  

Important considerations:

  • Only one user can access the runtime version at a time.
  • Exclusive access to a textbase is required, so you cannot install the runtime on a network server and set it to search your live textbases.
  • The textbases are read-only once installed on the target PC.  This means you will not be able to adjust any query screens or reports on the target PC.
  • If you have links to images or documents in your textbases, the runtime version requires linked files to be in the same folder as the textbase.

Over the years our preferred procedure for creating and updating runtime versions has evolved to the following:

  • Create a folder called DB/Text_Runtime and unzip the install kit files.
  • Create a copy of the textbase that you wish to make available through the runtime version in this folder. (Name it to distinguish from the original such as CatalogRuntime.) (Menu screen > Manage Textbases > Copy Textbase).
  • If desired, open this new textbase and search for and Batch Delete any records that should not be included. (Records > Batch Delete)
  • Open this new textbase and set defaults for  query screens and forms appropriate for runtime users (Maintain > Change Textbase Defaults)
  • Optionally, remove extraneous forms to avoid confusion – most runtime users will only need a couple of reports (Maintain > Manage Textbase Elements)
  • Edit these chosen query screens and forms to add more search tips or information suitable for new or infrequent users. (Search > Design Query Screen or Display > Design Form)
  • Copy any linked image or document files that you want to make accessible into this same folder.BatchModify
  • Batch modify the fields for image or document links to remove pathing information.  (Records> Batch Modify. Choose Substitute Text and Affects Matching e.g. if a typical entry is N:\Archives\Images\2012-01-67.jpg  enter the path to the last \ in the Old Entry box (N:\Archives\Images\) and leave the New Entry box blank. This will leave just 2012-01-67.jpg  in the field.)  You may need to run several separate batch modifications if you have linked files in many different folders.
  • Create an introductory menu screen in the same folder setting the preferred query screen and forms. (Menu Screens > Design > Create > Box Properties > Initial Elements).  You may wish this to contain contact and additional explanatory information.

To install the runtime version:

  • Copy over the entire DB/Text_Runtime folder as created above (make sure to close the runtime textbase first).
  • Run setup.exe and follow the install instructions.
  • When DB/TextWorks first opens, Select the appropriate menu screen ( Menu Screens > Select).
  • Customize the toolbars to remove extraneous or confusing icons, i.e. the Sort Report and Select Form icons if you have specified only one report of each type. (Tools > Customize Toolbar).
  • Any adjustments to query screens or report forms or the data itself will need to be made on the original version and the files copied over again.  Always be sure the textbase is not open when copying the files.

To update the runtime databases:

  • Export and Import records from your working textbase rather than using Copy Textbase again unless you are OK with repeating all the steps above each time. 
  • Use Copy Textbase to create a new copy of the Runtime version of the textbase instead.import
  • In your working textbase, search for all new or modified records (or just the subset you wish to make available through the runtime version).
  • Export in Inmagic Tagged Format (File > Export. Inmagic Tagged | Current Record Set | All fields)
  • Switch to your Runtime textbase and Import.  (File > Import.  Inmagic Tagged | Add/Replace = Check for Matching Records & Replace Fields matching on your textbase unique record identifier field.  (You should always have an Automatic Number type field such as Record ID.) Accept New Record if Match Not Found)  The screenshot is from version 14 which added the ability to set up Import Profiles so you can retain these settings for the next update.
  • If you have image or document links you will need to batch modify these for any new or updated records and ensure that you copy over these files into the runtime folder too. 
  • Delete the original runtime textbase and rename the new version to the original name (Manage Textbases > Delete and then Rename). This ensures your menu screen still links correctly.

Setting up and maintaining the runtime version can be quite time consuming!  If you do have an intranet or web site, please contact us to discuss the various options for publishing your textbases.  We can also host authenticated sites if you do not have your own intranet or webserver. 

Capital Health in Halifax updates look and adds features

by Denise Bonin Friday, November 30, 2012 10:18 AM

It started with a simple request… “Could you help us add permalinks to our web Catalogue textbase records?”, but it ended with 3 new textbase interfaces, an ordering cart, a mobile interface, the ability to add records to RefWorks and, of course, permalinks.

At the beginning of this project with the Capital Health Library, it was quickly determined that, given the age of the current web-interface, adding permalinks to the records could only be accomplished using canned searches with rather long URLs.  That was rejected and a discussion ensued that resulted in the addition of many new features to the site.

Out with the old and in with the new. We started with the backend by revising the textbase data structures and ditching a bunch of unused fields and forms for the Catalogue and Pamphlets textbases.  The Catalogue had a separate interface for journal check-in and item ordering, which was also revamped.  Using the Andornot Starter Kit for Inmagic’s DB/TextWorks, we were able to provide nice clean desktop screens with a minimal number of forms, including a couple of links to saved sets from the menu screen, e.g. new catalogue items added in the past 30 days.  Given that the Capital Health library staff were already familiar with the Inmagic DB/TextWorks program, it was not a big jump to start using these new desktop interfaces and they adapted quite quickly. 

Screen shot of Pamphlets textbase search resultsMore clean up and integration. The web-interface overhaul followed using the Andornot Starter Kit for Inmagic’s WebPublisher PRO.  This included new search screens, brief report forms, and full display forms with “see also” links and Permalinks for the Catalogue, Journals and Pamphlets interfaces.  All of which was nicely integrated into the Capital Health Library website template.  Google book covers and links to Google Books were made available on both report and full display forms in the Catalogue.  Users of both the Catalogue and the Pamphlet textbases now have the ability to add items to a cart, for ordering, and/or Email, Save and Print.  In addition, within the interfaces, users can also link to selected websites, e-books, e-journals or to in-house PDF files.  Quick links to the other textbases and back to the Library website are readily available on every page.

Go-small-and-go-home. Why not let the users have access to the systems wherever they are located, even if it is on the bus, in the hospital, or at home?  Using the mobile version of the Andornot Starter Kit, we added a couple of mobile interfaces.  These included the Catalogue textbase as a whole, with all its links to e-books, e-journals, Google Books, websites, etc. as well as a separate journal subset.

Screen Shot of Catalogue textbase of RefWorks LinkResearch counts. A slight delay in the launch occurred when it was discovered that RefWorks was a big part of the Capital Health library world, but that it took about 10 steps to implement this in order to get catalogue records into RefWorks.  Some coding later and we were able to add the RefWorks feature to the Email, Save and Print portion of the cart allowing a much smoother path from catalogue to bibliography.

“We got much more than we expected when we asked about Permalinks! We now have an ordering system for our patient pamphlets, a direct-to-RefWorks button and mobile-ready search pages for our catalogue and our journals. All of this is based on the Inmagic software that our staff know so well. Andornot worked with our Information Technology department to get us to a new level of service. The look and feel is close to what our users know, so there is limited change for them, but behind the scenes, we now have more searchable fields, simpler systems, and, of course those Permalinks! All in all, an excellent experience!”
Penny Logan, Capital Health Manager Library Services

Future ready. With all these new features now in place the library is well positioned to move into the future, providing the Capital Health staff with an abundance of new information access options. 

Ronald McDonald in the Library

by Denise Bonin Tuesday, October 30, 2012 10:34 AM

RonaldMacDonaldFaceFramedThe PG Family Resource Library in the Maternal Child Department at the University Hospital of Northern British Columbia was established with the generous donation from the Ronald McDonald Children’s Charities and provides access to a large number of materials about child health issues. The resources cover topics such as ADHD, bullying, dyslexia and Tourette's syndrome. 

Anne Allgaier, the British Columbia Northern Health Regional Librarian, included the bibliographic records for this collection of over 230 books and DVDs in her current library catalogue, and has also made them available on the library website. Users can search the catalogue database for just the Family Resource portion of the collection or chose from a list of topical searches on a webpage with a fun image of Ronald MacDonald in the background. 

Once the topic link is clicked, the user can see a list of items, with details about the item.  Most of the records for the books include book cover images, which link to Google Books for even more information about the resource and the ability to purchase, if desired.  Users can also add the items in their search results to a list and order them from the library. 

The Northern Health Regional Library has been a long time user of Inmagic DB/TextWorks as well as WebPublisher PRO software.  Their website is hosted by Andornot and the canned searches were designed using the Andornot Search Cannery Wizard

Anne says, “The images and links to the Family Resource Library will facilitate access to the resources for the patients and their families in the UHNBC Maternal Child department. The materials can all be borrowed and library staff will also help with accessing information not available in the Family Resource Library.”

“Thank you to Andornot for creating the special page for this unique collection.”

Parents and children in Prince George and indeed the whole Northern Health Region, will be delighted to have Ronald McDonald guide them through these wonderful resources. 

5 Ways to use DB/TextWorks with SharePoint

by Jonathan Jacobsen Monday, October 01, 2012 2:53 PM

With each new release, SharePoint becomes both more useful and more prevalent in organizations of a certain size. Used both for intranets and public-facing web sites, SharePoint provides tools to help users communicate, collaborate and share and manage documents and information.

While SharePoint offers document storage and search capabilities itself, many DB/TextWorks users prefer the interface and features they are most used to, and wish to continue using DB/TextWorks to manage their databases and collections. Replicating administrative workflow in SharePoint is often not practical or cost effective. Those with WebPublisher PRO may wish to continue providing web browser search access in that fashion.

Fortunately, it’s quite feasible to use DB/TextWorks and WebPublisher PRO with SharePoint as there are many options for integrating one into the other. However, before rushing to do so, one should consider the consequences, such as:

 

  • If users are used to a particular search interface or syntax, will a switch to SharePoint cause confusion or frustration? Will you continue to provide access to the previous interface?
  • How many records are in an existing SharePoint site compared to ones in the DB/TextWorks databases? Will including the latter in SharePoint overwhelm the site?
  • Will significant capabilities be lost, such as the ability in WebPublisher PRO to create See Also hyperlinks, browse indexes or bring in book covers from Google?

 

A few of the options for integrating DB/TextWorks databases into a SharePoint site are:

 

  1. Use the SharePoint Page Viewer web part to iframe Inmagic WebPublisher PRO search and results pages. This is the simplest approach, but requires that you have WebPublisher PRO and has usability drawbacks (iframes are harder to bookmark, navigate and size correctly). Search results will not appear in any SharePoint site-wide searches, which may be the desired approach if they would overwhelm the results.
  2. Export data from Inmagic databases to a CSV format and import into SharePoint Lists, where they can be searched, sorted, filtered, etc., the same as all existing data in the SharePoint site. A search scope can be defined in SharePoint to allow users to focus a search only on the imported data, if desired. This approach does not require WebPublisher and can be done manually with one or two connector tools, or automated with one or two more.
  3. Export data from Inmagic databases to XML and import as a SharePoint Data Source. As with #2 above, this can be automated. However, the data is less usable without further effort in SharePoint as a Data Source compared to a List.
  4. Set up a connection to the WebPublisher PRO SOAP interface as a SharePoint Data Source, either to import data, or to construct a real-time search interface. As with #1, this requires that you also have WebPublisher PRO installed, and will require further effort to make good use of the data within SharePoint.
  5. Write a custom .NET connector to WebPublisher PRO within SharePoint Business Connectivity Services either to import data or for real-time searching. This requires that you have WebPublisher PRO and requires the most initial effort and skill, but also offers the most options for customization to meet very specific needs.

 

Each of these options has pros and cons based on the effort and skill required to implement, and the features that result. For those with DB/TextWorks but not WebPublisher PRO, option 2 is an excellent choice in that it is not too complex nor costly to implement, but provides reasonably useful results.

This blog post outlines just a few of the issues and options for using DB/TextWorks and WebPublisher PRO with SharePoint. We would be pleased to advise you on the best strategy for your organization and needs.

Month List