Functionality of the Xgrain interface

Tim Stickland gave a demonstration of the prototype Xgrain interface to the participants. He also demonstrated the prototype ZBLSA functionality.

During the hands-on session that followed, participants were given a copy of the list of features discussed at the First Xgrain Workshop and asked to complete a form containing two headings:

1. Your comments on the prototype interface
2. Suggestions for other functions you would like to see.

The following feedback was received.

Your comments on the prototype interface:

1. With respect to access to web based HTML databases - this increases potential usefulness of the service of extending the coverage. On the other hand, it increases the amount of understanding of the service. If the user interface is aimed primarily at teaching and learning and especially undergraduates, it might be better to concentrate on shallow searching and a simple easy to use interface, i.e. maybe the addition of HTML databases complicates things too much for the target audience. Some databases might not have abstracts as a searchable field. Xgrain works well for keyword search / subject searches. There are obviously complications when searching by author. I like the way that switching between search and advanced search means that re-keying is not needed and also reselecting field its search is not needed.
2. Difficult to make comments as it is obviously very prototype! Can search be on same page as database selection (i.e.SALSER). Do we need an advanced and basic search? Can the basic search be a box at the top of the page and the advanced search menu be an extension of this box on the same page.
3. Confusion area under results summary (left). Not clear you click on results list (right). Confused about ERIC - perhaps because MAC person not PC - couldn't find interface.
4. a) Impressed by the demonstration which appears to do the sort of search that Xgrain intends. b) Just troubled by the databases that are valuable to search which might not be part of the JISC etc. Example - The RIBA produced - Architectural Publications Index (API).
5. Would it be possible to put the search box and database choice on the same page?
6. Clean and not cluttered, keep it that way if you can.
7. OK. Search box first. Will need method to decide which databases to search or do you search all and then allow user to select returns of interest and search again. Results summary - clean and clear. Database selection could be put on advanced search.
8. a) List of databases for cross-searching: add a direct link to service and add a link to a short description of the database. If the list of databases would grow exponentially, add a search interface for database (e.g. all databases relating to 'history'). b) Presenting indexes to be searched with list of databases selected is very useful: it can influence the decision which databases to select. c) Complete result list for all databases, not split out by database. d) Profiling of database selection by institution, subject area, and individual preferences. This will also need to have info on authentication (or link to local authentication information): if users go directly to the service they might be confused if challenged for a userid / password. e) Possibility to define / broaden a search (e.g. if too many hits). f) on search screens remind user which databases are selected. g) Short display: is it possible to add year of publication - very important to decide on relevance of item.
9. It is basic but that is a good thing! It is slow: students will expect results in seconds. Link colours change when they have been visited: The 'results list' buttons could change similarly (from results summary page).
10. It was easy to use in the example I chose, and the link to ZBLSA was the best bit. Moving around between the two probably needs (and I am sure will later on) to be clearer, at least explained. The ZBLSA presentation is nice; Xgrain still rates 'low key' loading (and is obviously in unfinished form anyway...)

Suggestions for other functions you would like to see:

1. a) It might be that simple shallow searching of only JISC services both satisfies a certain need, and also provides and easy to use and understand service. Perhaps adding other interfaces (in HTML) and non-subscription services actually makes the end product less focused. b) Search terms should always appear in brief record citations. i.e. fields search should be included in results summary. c) Like to use search keywords / abstracts / title in one go easily without going to advanced search.
2. a) Choice by faculty group but also choice by database. Results list should display number of results. b) I would like to see the results returned in order of relevance. So rather than returning 100 hits from BIOSIS and 50 hits from another database, it would be better if the results were returned most important first. It just seems too many steps for the user to go through! Ideal would be enter search term / s - then you are returned a list of the top 50 (or so) returns NOT categorised into which database they are from, although you would see in the details where the source was.
3. Quicker - simple interface.
4. a) I would like somehow, somewhere to keep in view the citation that I was Xgrain searching or is this asking for too much pampering. b) Find the layout clear but would prefer if 'dosearch' was 'do search'. c) Would like to have the ability to choose the selection of databases to Xgrain search if possible - this could speed up searching. d) Would like the search term to appear in the record highlighted in some way.
5. Results page - what did I search for?
6. A warning or notification that the results may take 30 seconds or so to come through. Maybe more detail on why a 'search could not be run', is the server down or is it my fault? Maybe a 1 or 2 word description of what each target covers so that I only include ones that are relevant to me. When locating with ZBLSA, it was not 100% clear that I needed to scroll down, it appeared to just show the full record again. Key more prominent (V?). Shopping cart ability to search for records then review later using ZBLSA? Maybe email results to oneself or save in my profile.
7. Should search when hit return, not have to click 'run search'.
8. a) Many searches will be done for purpose of creating a bibliography: export functions are essential (email, tab-delimited files, etc) b) Possibility of selecting / deselecting records for further action. c) Possibility of saving searches then re-running them. This would be a good first step in direction of alerting type services. d) Will have to clarify to users the difference between 'keyword' and 'subject' searching.
9. It seems that the profiling process could play a very important role. There is a role for an institution's own profile, which presumably would be activated when a user accesses the Xgrain service through the institutions VLE, or by IP address. There is also a role for an individual's profile. This could be provided by an MLE, and automated, and / or provided by the individual when logging on to Xgrain. I like the idea of profiles working behind the scenes to help students target databases of value to their needs.
10. No comments.