Bib record browser with 'see also', etc from linked authority headings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
For Evergreen master:
This feature provides a patron-oriented OPAC interface for browsing
bibliographic records.
Users choose to browse by Author, Title, Subject, or Series. They then
enter a browse term, and the nearest match from a left-anchored search
on the headings extracted for browse purposes will be displayed in a
typical backwards/forwards paging display. Headings link to search
results pages showing the related records. If the browse heading is
linked to any authority records, and if any *other* authority records
point to those with "See also" or other non-main entry headings, those
alternative headings are displayed a linked to a search results page
showing related bib records related to the alternate heading.
The counts of holdings displayed next to headings from bibliographic
records are subject to the same visiibility tests as search. This means
that the org unit (and copy location group) dropdown on the browse
interface affects counds, and it further means that whether or not
you're looking at the browse interface through the staff client makes a
difference.
There are three commits here:
http://
Sites may want to note the two default-off features described at the bottom of the included release note. These are the 0-9 A-Z shortcut links and the leading-article warning global flag.
tags: | removed: pullrequest |
Changed in evergreen: | |
status: | New → In Progress |
assignee: | nobody → Lebbeous Fogle-Weekley (lebbeous) |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
milestone: | 2.5.0-m1 → 2.5.0-m2 |
Changed in evergreen: | |
milestone: | 2.5.0-m2 → 2.5.0-alpha1 |
Changed in evergreen: | |
assignee: | Ben Shum (bshum) → Dan Wells (dbw2) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Regarding the warning on users entering articles:
11:21 < senator> this might need to be an org unit setting instead of a global
flag. since with browse, as with search, it's easy to see
holdings anywhere in the consortium (hm, didn't think about
how this interacts with opac hiding), i was thinking it didn't
make a ton of sense to tie the setting to a location. thinking
about it some more though, maybe using physical_loc actually
does make sense.
There might also need to be more (or clearer text) in the warning itself. Awaiting the results of some site testing on that front.