[Evergreen-catalogers] Patron view in Angular staff client

[Elaine Hardy]

It also means you can't check the 856 links as displayed' Something I do
often.

The point of the OPAC/patron view within the staff client is so it works
and looks the same way there so that we DON'T have to go somewhere else to
check our work.

J. Elaine Hardy, PINES and Collaborative Projects Manager
------------------------------

Georgia Public Library Service

2872 Woodcock Blvd., Suite 250 | Atlanta, GA 30341

(404) 235-7128 | ehardy at georgialibraries.org

(404) 548-4241 | Cell

<https://www.facebook.com/georgialibraries>
<https://www.twitter.com/georgialibs>
<https://www.instagram.com/georgialibraries/>

Join our email list <http://georgialibraries.org/subscription> for stories
of Georgia libraries making an impact in our communities.


On Mon, Nov 23, 2020 at 4:09 PM Thomsen, Elizabeth <et at noblenet.org> wrote:

> We're working with the Angular version of the staff catalog on Release 3.6
> on our training server, and having a hard time with the Patron View with
> all the links disabled.
>
> The pre-Angular staff catalog is used by library staff who are searching
> the catalog for a various reasons, including cataloging ,but also
> reference, readers advisory, collection development, working on course
> reserves, booklists, displays, etc., and in all of these functions, it's
> not always as simple as "find a record, add an item" or "find a record,
> place a hold," etc.  Staff use the links in the catalog to navigate around
> between related records, just like patrons do (actually, probably more than
> patrons do.)  So they click on the author's name to see other works by the
> author, they follow the subject heading links to find related works, they
> click on the "View other formats and editions" to see what other versions
> of the title they have that may work for their patron or their project, and
> they click on the links for electronic resources for all the same reasons.
>
> I support this comment from Bill: "I'd also like to suggest we make
> changes to the Angular staff catalog proper to support whatever staff work
> flows are needed. Having the embedded TPAC be integral to any staff work
> flow, apart from simply seeing what displays, is a big step backwards."  [
> * ] <https://bugs.launchpad.net/evergreen/+bug/1849137/comments/9>
>
> It's not the embedded TPAC itself that's integral to so many staff
> workflows, it's the functionality that is only found there -- how can we
> bring this into the Angular Catalog?  Otherwise I know our staff will just
> want to stick with the Traditional catalog as long as possible, missing all
> the good things about the Angular catalog.
>
> WIsh I had realized what an issue this is going to be and brought it up
> earlier!
>
> --
> Elizabeth B. Thomsen
> Member Services Manager
> NOBLE: North of Boston Library Exchange
> Danvers, Mass.
> www.noblenet.org
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20201208/7a492113/attachment.html>