Andornot’s Professional Development Grant for 2019 Awarded to Marla Dobson

by Jonathan Jacobsen Wednesday, February 06, 2019 12:24 PM

For the third year in a row, Andornot is pleased to award a Professional Development Grant to a working professional, to aid them in attending a conference or workshop.

This year's recipient of the $1,000 grant is Marla Dobson, Curator of the Museum of Health Care in Kingston, ON.

In her application for the grant, Marla writes:

"As the Curator for the Museum of Health Care at Kingston, I have responsibility for planning, organizing, and supervising exhibition development, collections development and maintenance, as well as programming support. I care for a collection of 40,000 objects related to the history of medicine and health care in Canada. I also act as an ambassador for the museum, building its public profile within the regional community as well as at national and even international events."

The collection is available at https://mhc.andornot.com, with a search interface developed from our Andornot Discovery Interface, and hosted by our Managed Hosting service.

Marla adds:

"I wish to attend the Canadian Museums Association National Conference because it is vital that I develop and expand my professional network within the Canadian museum community. I am new in my position and as an emerging professional, wish to expose myself to workshops and networking events that will firstly, improve my ability to be a successful curator, and secondly, help me make connections with other organizations with which we could partner on projects and exhibitions."

Andornot strongly believes in the value of attending conferences to foster professional development. We attend events across Canada all year long to learn about new trends and technologies, meet with clients, and share our expertise with like-minded folks.

We receive many excellent applications for this grant each year and face a tough decision in choosing just one. We thank all who showed an interest in the grant and only wish we could send everyone to a conference.

We look forward to meeting you at one of the conferences we'll be attending this year.

VuFind 5.1 Released

by Jonathan Jacobsen Monday, February 04, 2019 11:48 AM

Version 5.1 of the VuFind Open Source discovery software has just been released. This minor release adds several new features and fixes.

Some key additions:

  • Configurable user account notifications, making activity (such as fines, available holds, overdues, etc.) more readily visible to the user.
  • A richer, fully customizable user feedback system, allowing the creation of custom forms in the VuFind interface for collecting not just feedback, but also purchase suggestions, survey responses, or anything else the administrator configures.
  • Optional dynamic DOI-based link augmentation in search results (currently supporting Third Iron's BrowZine service, but also extensible for other applications).
  • An experimental driver for integration with the FOLIO platform, available for early adopters (but subject to change as the platform evolves).
  • Better code generation tools, increasing the ease of creating new VuFind plug-ins.
  • Full Vietnamese language support in the user interface.

Additionally, several bug fixes, new configuration options, performance enhancements and minor improvements have been incorporated. Full details of this release are available at https://vufind.org/wiki/changelog#release_51_-_2_4_2019

Andornot offers development and hosting of VuFind as part of our Managed Hosting service. VuFind is an ideal entry-level discovery interface for small special libraries with primarily biblipgrahic information, provding the style of search experience users expect in 2019. For other kinds of cultural information, we recommend our Andornot Discovery Interface.

Learn more about VuFind and some of the sites we've developed here, then contact us to discuss VuFind, hosting and our other solutions for managing and searching cultural information.

How To Import Excel Data into VuFind

by Jonathan Jacobsen Tuesday, January 08, 2019 4:52 PM

Recently we had a new client come to us looking for help with several subscription-based VuFind sites they manage, and ultimately to have us host them as part of our managed hosting service. This client had a unique challenge for us: 3 million records, available as tab-separated text files of up to 70,000 records each.

Most of the data sets we work with are relatively small: libraries with a few thousand records, archives with a few tens of thousands, and every so often, databases of a few hundred thousand, like those in the Arctic Health bibliography.

While VuFind and the Apache Solr search engine that powers it (and also powers our Andornot Discovery Interface) have no trouble with that volume of records, transforming the data from hundreds of tab-separated text files into something Solr can use, in an efficient manner, was a pleasant challenge.

VuFind has excellent tools for importing traditional library MARC records, using the SolrMarc tool to post data to Solr. For other types data, such as records exported from DB/TextWorks databases, we’ve long used the PHP-based tools in VuFind that use XSLTs to transform XML into Solr's schema and post it to Solr. While this has worked well, XSLTs are especially difficult to debug, so we considered alternatives.

For this new project, we knew we needed to write some code to manipulate the 3 million records in tab-separated text files into XML, and we knew from our extensive experience with Solr that it's best to post small batches of records at a time, in separate files, rather than one large post of 3 million! So we wrote a python script to split up the source data into separate files of about 1,000 records each, and also remove invalid characters that had crept in to the data over time (this data set goes back decades and has likely been stored in many different character encodings on many different systems, so it's no surprise there were some gremlins).

Once the script was happily creating Solr-ready XML files, rather than use VuFind's PHP tools and an XSLT to index the data, it just seemed more straightforward to push the XML directly to Solr. For this, we wrote a bash shell script that uses the post tool that ships with Solr to iterate through the thousands of data files and push each to Solr, logging the results.

The combination of a python script to convert the tab-separated text files into Solr-ready XML and a bash script to push it to Solr worked extremely well for this project. Python is lightning fast at processing text and pushing data directly to Solr is definitely faster than invoking XSLT transformations.

This approach would work well for any data. Python is a very forgiving language to develop with, making it easy and quick to write scripts to process any data source. In fact, since this project, we've used Python to manipulate a FileMaker Pro database export for indexing in our Andornot Discovery Interface (also powered by Apache Solr) and to harvest data from the Internet Archive and Online Archive of California, for another Andornot Discovery Interface project (watch this blog for news of both when they launch).

We look forward to more challenges like this one! Contact us for help with your own VuFind, Solr and similar projects.

Andornot's November 2018 Newsletter Available: News, Tips and Tricks for Libraries, Archives and Museums

by Jonathan Jacobsen Monday, November 19, 2018 7:35 AM

Tags: newsletters

How To Create a DB/TextWorks Menu Screen

by Jonathan Jacobsen Thursday, November 15, 2018 10:36 AM

For some reason, DB/TextWorks menu screens are a little used feature. We often meet clients with many databases, but without a convenient way of seeing and accessing them all at a glance. Adding a menu screen to DB/TextWorks is quick and easy to do, but makes using your databases so much easier.

The screenshot above shows the menu screen from our Andornot Library Kit, with links to each of the many databases it includes. The one below shows one from one of our clients' systems.

What is a Menu Screen?

Like a Query Screen or Report Form in a DB/TextWorks database, a Menu Screen is a screen layout you create using the WYSIWYG designer in DB/TextWorks. You would usually add to it links to each of your databases, for searching or data entry. You might also add your organization's name or logo, contact or support info for anyone who might be using the system, a brief description of each database, etc.

Having links to all your databases on a single screen saves time and helps new users find their way around your collection of databases without having to hunt for them in folders on disk. It also allows you to specify, in each link to a database, which query screen and reports to load for that database. 

One way to create menu screens is to have different menu screens for different kinds of users. For example, in an archives or museum that relies on volunteers to help with data entry, you could have a menu screen for volunteers that only lists the Accessions database, and pre-loads a simpler query screen and data entry form designed specifically for volunteers. A more extensive menu could provide the archivist or curator with links to all databases, pre-loading the more sophisticated query and edit screens for their use.

Unlike a Query Screen or Report Form, the menu screen isn't stored in any one database, but rather as a separate file on disk (with a .tbm or .cbm extension). You would usually store it in the same folder as all your database files.

How do I create a Menu Screen?

  1. Open DB/TextWorks but don't open a database.
  2. Select Menu Screens > Design from the main menu.
  3. Choose "Create a New Menu Screen File."
  4. Browse to the folder where your databases are stored to save the menu screen in the same location, and give it a name.
  5. In the WYSIWYG Menu Screen Designer, you may now add links to textbases, your organization's name or logo, and other information. Use the examples above for ideas, or come up with your own design.
  6. To add links to textbases, choose Edit > Add > Textbase box.
  7. In the Textbase Properties Dialogue, select the textbase to link to, then on the Initial Elements tab, pre-select the query screen and forms to use by default. Note that these override the default screens and forms set in the textbase, and that in either case, users may still change to other screens and forms once they are in the database.
  8. On the Initial Action tab, be sure to select which window to open. For example, if your link is one such as "Search the Database", select a Query Window. If your link is "Add a New Record", select Edit New Record as the window to open.
  9. Save your new menu screen when your design is complete.
  10. If you ever create more than one menu screen, you can even add links from one to another on each of them.

How do I use a Menu Screen?

  1. On each PC that has DB/TextWorks, open DB/TextWorks but don't open a database.
  2. Select Menu Screens > Select from the main menu.
  3. Choose "Use the Menu Screen in a File", then browse to and select the Menu Screen file (ending with .tbm or .cbm) that you created earlier, usually stored in the same folder as your databases.
  4. Close and re-start DB/TextWorks and your menu screen will now automatically load, ready for use.

See this blog post from earlier this week about two other helpful but little used features of DB/TextWorks: Sets and Record Skeletons.

Month List