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.

Managing Digital Collections: A Presentation to Students

by Jonathan Jacobsen Tuesday, March 10, 2015 3:22 PM

Last night I had the pleasure of speaking to students at the School of Library, Archival and Information studies (aka iSchool) at the University of British Columbia. These students are taking LIBR 582: Digital Images and Text Collections and learning all the fundamentals of how to digitize materals, manage them, and provide online access. In particular, they are using Inmagic DB/TextWorks to build a database of digitized materials, and manage the metadata associated with them, as well as CONTENTdm from OCLC for web presentation.

In last night's class, I presented Andornot's common solutions for managing digital images and text. For those who missed the presentation, here's a recap.

Inmagic DB/TextWorks and an Andornot Starter Kit

We always recommend Inmagic DB/TextWorks as an easy to use database system for managing metadata about digitized objects, whether they are textual, photographic or audio-visual, and no matter whether born digitial or scanned from an analogue source. Paired with one of our starter kits, any library, archive, museum or other organization can be up and running in just a few hours. Information can be entered in simple data entry screens, by staff or volunteers, or imported from other sources.

Inmagic WebPublisher PRO

Inmagic's original web publishing platform, combined with an Andornot kit, can provide simple search access to a DB/TextWorks database. A modern web design can be applied so that the site can be used on tablets and phones. Features such as spelling corrections and facets are not available however.

Andornot Discovery Interface (AnDI)

The Andornot Discovery Interface (AnDI) uses the popular Apache Solr search engine to provide relevancy-ranked results, spelling corrections, and facets for search refinement. Websites built with AnDI include features for displaying images in various sizes, in list or gallery format, for embedding playback of audio and video files, and for viewing and browsing individual pages of digitized documents, with highlighting of search terms on the pages.

VuFind

The open-source VuFind discovery interface is very popular with academic and public libraries, and a growing number of special ones.

Inmagic Presto

Inmagic's current generation web publishing platform offers users the ability to configure their own screens and displays with no programming required, and now includes facets for search refinement.

Omeka

The open-source Omeka content management system can be used for metadata management as well as searching. It doesn't offer spelling corrections or facets for search refinement, but does provide a very easy to use web interface and an Exhibit Builder plug-in to develop exhibits of aspects of a collection.

BC Teachers' Federation Launches TeachBC Resource Sharing Site

by Jonathan Jacobsen Tuesday, December 02, 2014 3:04 PM

The B.C. Teachers' Federation (BCTF) has launched a new website to enable BC teachers to share resources relevant to the K-12 BC curriculum. Called TeachBC, the site allows teachers to search for lesson plans, activities and other material, as well as upload their own teaching resources and research to share with their colleagues. 

TeachBC is publicly accessible at https://teachbc.bctf.ca and is in the early development stage. It is anticipated that this will grow quickly as BC teachers realize the value of the site as a one stop resource for quality classroom teaching resources.

Andornot developed this new site with the BCTF using a couple of our most popular technologies.

1. A pair of Inmagic DB/TextWorks databases are used as the initial data store for resource submissions. 

DB/TextWorks was selected as it's already in use and familiar to BCTF staff, and provides a quick and easy way of reviewing, editing and approving submissions.

2. The Andornot Discovery Interface (AnDI) powers the web search interface. 

Features such as spelling corrections, relevancy-ranked results and facets to refine a search help users find relevant resources quickly. 

Teachers can search by keyword, then narrow the results by grade, subject and resource type. A recommendation system allows teachers to mark resources they find most useful, and they can also easily Share them on Facebook, Twitter, Google+ or Pinterest. Download counts are also tracked to provide another indicator of popularity.

Teachers can create an account on the site and there is an online submission form which feeds into DB/TextWorks to submit resources for review by BCTF staff before they are available for viewing publicly.

Contact Andornot for more information on developing a search interface for your unique collections.

Adding dot leaders between columns in a DB/TextWorks report

by Kathy Bryce Tuesday, September 30, 2014 5:29 PM

Have you ever tried to create an index report in DB/TextWorks and wanted to have a dots to line up the entries in the two columns? The index entries are invariably different lengths so the number of dots required needs to vary.

image

The trick is to add fixed text into the box for the first column – in this case after the title. In the Box Properties set the Paragraphs tab to No added paragraph breaks. The fixed text dots have to have a space between them as in . . . . rather than ……..  This allows any excess dots for long entries to be bumped to the next line.  Under the Position tab then set the Maximum height to 1 line.

image

You may need to adjust font size and margins if your index terms are longer than one line.

Contact us if you need help with your Inmagic DB/TextWorks report designs.

How to Add a Unique Record ID and Date to an Existing Database

by Jonathan Jacobsen Wednesday, May 28, 2014 6:09 PM

The principles of good database design suggest that every record in a database should have something that uniquely identifies it and distinguishes it from every other record. In a small library catalogue, it may be that every title is different from every other, but in any larger database, there's a good chance there will be more than one very, very similar record. 

When it comes time to do more with this information, such as import it into Inmagic Presto or the VuFind discovery interface, or clean-up some older records, it's imperative that every record be able to be uniquely identified.

It's also good practice to have fields that track the date a record was created and the date it was last modified, for similar reasons.

It's very easy to create these fields in your database structure, whether in Inmagic DB/TextWorks or another system, when you are first building the database. But what can you do if you already have a database with thousands of records, and no unique record identifier or dates created or modified? With DB/TextWorks, it's very easy to add this information even after the database was built and populated. 

There are four main steps to this:

  • Backup all your existing records, just in case of a problem.
  • Verify that these fields don't already exist.
  • Add the fields to the database structure.
  • Populate the fields with data.

Backup the Database

1. Open DB/TextWorks but don't open a database. Select Manage Textbases > Dump Textbase. 

2. Browse to the location of your database and select it. 

3. Next, pick a folder to store the export in and give it a meaningful name.

4. When the export is complete, you'll now have a backup you can reload, just in case anything happens.

Verify Fields

5. Open the database in DB/TextWorks and, if it has password protection, be sure to sign in with the Master password, so you have full access.

6. Select Maintain > Edit Textbase Structure.

7. In the Edit Textbase Structure window, scroll through the list of fields to check that you don't already have a unique ID and/or dates created or modified fields. You may be able to identify them by Name (e.g. RecordID, RecordCreated, RecordModified) or by Type (e.g. Automatic Number, Automatic ID, Automatic Date).

Add Fields

8. If none are found, select Edit Fields. You will now enter information to create the new fields listed below. Be sure to select Add rather than Change after entering information for each new field.

Field Name RecordID
Field Type Automatic Number
Other Settings By default, the automatic numbering will start at 1 and increment by 1; there's usually no reason to change this.
Field Name RecordModified
Field Type Automatic Date
Other Settings Update Entry: When Record is Created or Modified.
Date Components and Format: you may choose whether to include the time, or only the date, and which format. We usually select Date Only and Short Date Format, unless your data will be imported into Presto, in which case Date and Time is best.
Field Name RecordCreated
Field Type Automatic Date
Other Settings Update Entry: When Record is Created.
Date Components and Format: you may choose whether to include the time, or only the date, and which format. We usually select Date Only and Short Date Format, unless your data will be imported into Presto, in which case Date and Time is best.

9. With all of the information entered, click Finish and OK to save your changes to the database structure.

Add Data to Existing Records

10. Select Search > Find All Records to retrieve all records from the database. This may take some time, but you can click the Stop button in the bottom status bar of DB/TextWorks to stop the formatting on the screen.

11. When the records have finished loading, select Records > Batch Modify. The trick now is to make a perfectly innocuous change to every record in your database. As DB/TextWorks goes through every one, since the database now has Automatic Number and Automatic Date fields, they will automatically be populated. 

If you happen to have an unused field in your database, you could populate it with some value, and then remove that again in a second batch modification.

Or, you could add a new field and use batch modification to populate it with some value. You can then either leave it as-is, perform another batch modification to delete the data from the field, or delete the field altogether.

The batch modification feature in DB/TextWorks is quite sophisticated and an explanation of it would expand this blog post to unwieldy dimensions. However, the help built-in to DB/TextWorks explains all the options, including new features added to recent releases. 

12. When the batch modification is complete, every record will now have a unique identifier and the date the record was last modified. To verify, search for some records and view the ID and dates.

13. Now that you have a unique ID, you can configure DB/TextWorks to record it in the textbase log file every time a change is made to a record. This has proven invaluable to several clients this month when accidental changes were made to records. We were able to use the log to undo those changes. To configure your textbase log, select Maintain > Edit Textbase Structure again, then Log File. Select your RecordID field as the First Identifying Field, and something like title as the Second.

If you need any help with the above, just let us know.

Month List