In Z39.50 search, could we see local catalog results at the top?

Bug #1850700 reported by Jane Sandberg
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Our tech services coordinator pointed out that native-evergreen-catalog records often appear near the bottom of search results (see attached picture from a 3.3.3 system), even though they are the results we tend to be most interested in!

Is there a way to make sure that native-evergreen-catalog records always appear at the top?

Revision history for this message
Jane Sandberg (sandbergja) wrote :
Revision history for this message
Janet Schrader (jschrader) wrote :

The native-evergreen search results are not consistent. In our system we use only local catalog and OCLC so I'm not sure where 'loc' would be in results so I can't entirely confirm Jane's behavior.

An ISBN or UPC search puts the native-evergreen results at the bottom of the list. A title or author/title search puts them at the top. Add a publisher or pub date to a title search and it's native-evergreen on the bottom. Keyword + subject has the native-evergreen at the top.

As the numeric ISBN or UPC searches are probably the most common, i.e. scan them in, it would be beneficial to have these results behave the same as the title searches. Because of the design of the Z39..50 screen, for many catalogers scrolling is required to see all results. Not readily seeing the native-evergreen items can result in duplicate records being imported.

Release 3.2.4
Release 3.2.8

Revision history for this message
Mary Llewellyn (mllewell) wrote :

I would rather be able to sort the results as we can in XUL.

Revision history for this message
Janet Schrader (jschrader) wrote :

+1 to being able to sort.

Thanks!, Mary. I had forgotten about doing that.

Revision history for this message
Elaine Hardy (ehardy) wrote :

+1 to be able to sort all fields

Elaine Hardy (ehardy)
tags: added: sorting
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Eva Cerninakova (ece) wrote :

Related to bug 1830442.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.