Matthew Cock, Head of web, British Museum
In a recent post, I wrote about the launch of our new collection search beta. Well, we’ve now gone a bit further, and released an overhaul of the ‘advanced search’ functionality.
At heart, it works the same as before – users begin their search by selecting the ‘controlled terms’ that are used by our curators and cataloguers when creating the records, and retrieve all objects in the database that have been tagged with that term, or set of terms in combination. So, for example, you can find groups of objects for any combinations of terms – all the prints made in Japan between AD 1800 and 1835 perhaps, or all objects from London, Exeter and Glasgow made of bronze and so on.
Most of the lists of terms are also structured in hierarchies – for example, Paris is under France – so a search for objects from France retrieves all objects tagged with France, and any objects tagged with one of the many place names that are nested under France. In addition, we allow people to filter on the different ‘associations’ after they have made a search, for example, they can choose whether or not to include objects based on whether they are made by, attributed to, a depiction of, an artist.
In the current collection search interface (launched 2007), the user had to follow quite a process to build up their search terms and get to a page of results, and the interface wasn’t very intuitive. Only a small proportion of people used the advanced search, and most people we talked to said it wasn’t obvious how to use it.
There are two main changes that we have made to improve it. Firstly, we are using “auto-complete” – so that as you write the first few letters of your search term, a set of possible complete terms is shown based on the terms that we have in the database, along with some description so you can be sure it is the term you intended (for example, dates to help distinguish several artists with the same surname).
Secondly, we have kept the search criteria and the results showing on the same page. The user doesn’t have to travel back and forth between different pages to update their search.
We’re very aware that we have been looking at this for quite a while, and it is about time it was let loose and tested in the wild. We are really interested in any comments or questions that you have on how it works – whether you are a regular user, or using it for the first time. We hope to release this as the main interface to the collection database in the Spring.
Please add a comment below, or email us at email@example.com and include COL Beta in the subject line.