DBTextWorks and WebPublisher PRO Version 15 Upgrade Tips: To Preserve or not Preserve CSS?

by Jonathan Jacobsen Friday, August 14, 2015 1:12 PM

Inmagic released version 15 of DB/TextWorks and WebPublisher PRO not long ago and many of you have or are upgrading to this new version, to take advantage of some of the great new features, especially in DB/TextWorks.

Please note that when upgrading, special attention must be paid to any forms and query screens inside your textbase that you use on the web. This may be forms that you developed yourself and use with WebPublisher, or they may be forms provided by Andornot as part of our Andornot Starter Kit or Andornot Archives Starter Kit. A change to DB/TextWorks in version 15 may affect the layout of your search pages and results.

The ReadMe file for version 15 notes the following:

Use Cascading Style Sheets to preserve formatting. In the Query Screen Designer and Form Designer the HTML tab of the Screen Properties or Form Properties dialog box includes this new option. Previous versions of DB/TextWorks asked the question each time you used Export Query Screen to HTML or Export Editing Form to HTML. In addition:

  • Whether cascading style sheets (CSS) are used is explicitly specified for each form, rather than for WebPublisher as a whole or by query screen.
  • The WebCSSOpt= DBTWPUB.INI option and the CS= URL parameter have been removed.
  • WebPublisher no longer tries to guess whether CSS will cause overlapping by automatically disabling CSS for forms that include Raw HTMLor Inline Images.
  • When DB/TextWorks upgrades a textbase for use with v15.0, all query screens and forms will be modified to have this option checked. If any of your forms include Raw HTML or Inline Images, which may cause overlapping, you may need to open them in the Form Designer to uncheck this option.

All forms that were provided by Andornot from our Starter Kits should not have Use CSS checked. With forms that you developed yourself, you may or may not wish to have this, depending on your form design.

If you've already upgraded and your web search layout is looking a bit like the morning after a wild night out (e.g. messed up), most likely it's due to the above and you simply need to open each form in the Form Designer, edit the Form Properties, and uncheck this box.

If you need assistance with the above, or have other layout issues, please feel free to contact us.

Track Inmagic DB/TextWorks Database Usage in More Detail

by Jonathan Jacobsen Tuesday, June 30, 2015 1:08 PM

Did you know that you can track quite a bit of detail about database usage in Inmagic DB/TextWorks? Every textbase can include a log file in which can track opening and closing a database, record locking, and record additions and deletions, including the Windows username of the person editing a record.

Time and time again, this log file has proven useful to Andornot and our clients. When errors appear in records, and especially when they have been deleted, perhaps erroneously, checking the log file usually helps clear up the mystery of when and by whom changes or deletions we made. While recovering a backup may be necessary to undo the changes, identifying how it happened goes a long way towards preventing future issues (as does adding passwords and other security to databases).

Full details and options for enabling textbase logs are provided in the help built in to DB/TextWorks. Just press F1 and read the entry for "Textbase log files." Here are some excerpts:

Textbase Log Files 

For each textbase, you can enable a log file to record textbase activity, including record and structure changes. A log file is a standard ASCII text file. It is saved in the same location as the textbase and has the same file name as the textbase, with the extension .log. You can enable, view, print, or delete a log file from within DB/TextWorks.  

Note: A log file does not record activity performed using Manage Textbase Elements.  

To enable a textbase log file 

Choose Maintain > Edit Textbase Structure > Log File.  

In the Textbase Log File dialog box, select Enable Logging to File.  

Select one or two fields with key identifying  information that will be written to the log file. We usually recommend selecting the Record ID field if you have one, plus the Title or similar key name field.

To record user activity in the textbase log file 

You can add a Details = parameter to the [LogFile] section of the <textbase>.ini file if you want the textbase log file to record who is opening the textbase, editing records, and locking records. 

Example:  

[LogFile] 

Details = 2  

 

You can set this to one of the following:  

0 - No enhanced logging 

1 - Logs when a user opens or closes the textbase 

2 - Logs when a user modifies records (and opens/closes the textbase) 

3 - Logs when a user locks/unlocks record (and opens/closes the textbase or modifies records) 

 

The <textbase>.ini file will be located with all the other database files, including the log file.

 

See our series of "Spring Cleaning" blog posts about other recommended textbase management tasks.

Contact us for assistance setting this up, or for any other aspect of using DB/TextWorks.

New search interface for Interior Health - policy and procedure documents, guidelines and protocols.

by Kathy Bryce Monday, June 08, 2015 10:07 AM

Interior Health contacted Andornot to discuss possible options for providing better access to their policy and procedure documents, guidelines and protocols.  These were available in several locations and were indexed in separate PDF’s depending on service area.  Maintenance of this system of indexes was becoming problematic and unsustainable. Interior Health needed an easy to use search interface for clinical staff to quickly find and link to the documents, whether they be on their SharePoint intranet, a vendor site or part of their subscription to Mosby’s Nursing Skills. 

Interior Health already owned a copy of Inmagic DB/TextWorksand the library staff were familiar with it, so we created a new database to catalog these documents.  The intranet search application pulls data from DB/TextWorks and is powered by our Andornot Discovery Interface (AnDI) to provide a faceted, discovery style interface geared to be as simple and uncluttered as possible. AnDI features spell checking with Did you mean functionality to catch common misspellings and typos, and staff have added some common acronyms to the records to ensure that documents can be found using nursing jargon.

We were able to extract data from multiple PDF’s and SharePoint lists to build the ClinicalCareFindItinitial database and batch modified records to populate additional fields. As a result, searches can be refined by Interior Health site, practice area, agency responsible, format and keywords.   We also note which source document or manual a specific guideline is part of.  The relevance ranking of the search results was adjusted to ensure that Interior Health (IH) wide documents always appear first. This approach really helps IH staff quickly locate the policy or protocol they are seeking.

Behind the scenes, the database also tracks who developed a document, when it was endorsed, and review dates to allow library staff to better manage the administrative side.  The search interface is hosted by Andornot with access restricted by IP Address to Interior Health staff.

Since the launch the reaction has been overwhelmingly positive. Comments from nursing staff included:

  • WOW oh WOW.  My brief interaction with the Clinical Care find-it has been an incredible experience so far.  Congratulations!!!!
  • A thing of beauty doesn’t describe this work well enough.  It is definitely the birth of an amazing solution.  I had a look at it yesterday, and it is a very intuitive piece of work.
  • OMG! It IS a thing of beauty.

And from the person responsible for administering the system:

  • As far as managing workload the drudgery of adding links to 5 separate indexes x 3 alternate titles/keywords (so sometimes 15 entries for one link/document!!!!) has been almost eliminated.  Now there is only “ONE” and it’s great!

This project is a good example of how library staff can assist other groups within an organization to better organize and improve access to their information and resources.  Prior to the start of this project Interior Health had looked to develop a new system internally, however library staff were able to convince them to utilize their existing software and Andornot’s expertise and hosting service to create an efficient and easy to use new system.

Contact us to discuss how we can help you provide improved search access to any collection.

Inmagic releases version 15 of DB/TextWorks, WebPublisher PRO and DB/Text for SQL

by Jonathan Jacobsen Saturday, May 02, 2015 10:42 AM

Inmagic has released version 15 of DB/TextWorks, WebPublisher PRO and DB/Text for SQL

Highlights of this release include:

DB/TextWorks

  • New Field Type: Rich Text. The Rich Text field type permits you to change fonts (font name, size, color, bolding, italics, etc.) within a single field, align text, create bulleted lists, and so on. 
  • New Field Type: Call Number. When records are sorted by a field using the Call Number field type, Call Numbers are sorted the correct order.
  • Email Enhancements: Email dialogue more closely resembles sending mail from an email client, and includes fields for additional message text and a signature.
  • Limits on the number of fields, characters in field names, linked textbases, forms, query screens, and many other features have all been increased.
  • Substitution Lists: Additional Field Types now support Substitution Lists: Call Number, Code, Image, Link, and Number.
  • Import Document. Improved IFilter text extraction for PDF files, especially those with text in the margin. Also, line breaks are added after each period-space (". ") to improve readability.
  • HTML, XML and Text Encoding enhancements for increased compatibility.
  • As well as features for publishing to the web, assorted small fixes, and a few older, less-used features removed.

More information is available in the DB/TextWorks Version 15 Read Me.

WebPublisher PRO

  • Issues addressed with the InmagicBrowse app, and new features added for publishing to the web from DB/TextWorks.

More information is available in the WebPublisher PRO Version 15 Read Me, as well as the DB/TextWorks Version 15 Read Me and the DB/Text for SQL Version 15 Read Me.

DB/Text for SQL

  • In addition to the features added to DB/TextWorks and WebPublisher (see above), DB/Text for SQL is now supported on SQL Server 2014.

More information is available in the DB/Text for SQL Version 15 Read Me.

 

All clients with a current Inmagic maintenance subscription will be receiving emails from Inmagic with download instructions for this release.

This release also includes a new version of the PowerPack (Importer, Checker and Updater apps), popular for automating data import and full-text extraction and indexing, as well as the search-only DB/SearchWorks version of the software.

A new version of the ODBC driver is expected within the next couple of weeks.

 

Important Notice

Upgrading the Inmagic software to version 15 requires a change to textbase structures. Once made, only version 15 of DB/TextWorks and WebPublisher PRO will be able to access the databases. Therefore, plan to upgrade all servers, workstations and databases at once.

Clients using the ODBC driver should not upgrade to version 15 of DB/TextWorks, nor upgrade their textbases, until version 15 of the ODBC driver is released.

 

Please consult the system requirements and supported OSs and web browsers for DB/TextWorks, DB/Text for SQL and WebPublisher PRO,  available on the Inmagic Extranet.

 

If you have a current Inmagic maintenance subscription but have not received a notification email in the next week or so, 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.

As always, contact us with questions, for assistance with this upgrade, or to renew an expired Inmagic maintenance subscription.

Burnaby Art Gallery Online Collections Now Include Public Art

by Jonathan Jacobsen Wednesday, April 01, 2015 2:26 PM

The Burnaby Art Gallery is a long-time Inmagic user and was one of the first of Inmagic’s clients to adopt our Andornot Discovery Interface (AnDI). This innovative tool was used as the basis of a new public search of the BAG’s collections, including artworks and books and printed materials in a reading room at the gallery. Features such as spelling corrections and facets, combined with a gallery style layout of art, help researchers, curators at other galleries and the public appreciate the BAG’s collections from afar.

Recently the BAG was tasked with cataloguing the many works of art in public settings, such as parks, city streets and local institutions. Over 100 of these works, many of them unique sculptures, have been catalogued, photographed and located by means of a latitude and longitude. This information is all stored in the gallery’s Inmagic DB/TextWorks system.

Records for these public art works are now available in the search engine. Click here to view the public art specifically. While viewing a work, a “View in Google Maps” link is available to geolocate the art and help you plan a trip to see it in person.

Ironically, and delightfully, the work of public art shown in the screenshot above is called ‘The Search Engine’ and is described as:

This large hybrid sculpture of metal and plants … is a public artwork which recognizes the legend of the train engine which sank into Still Creek 100 years ago. This sculpture connects the adjacent Skytrain with the hidden history of the area. The 45 degree angle of the sculpture evokes a train either sinking or emerging from the soils.

Contact us to learn more about AnDI and how it can enhance discovery of your unique resources.

Month List