[Evergreen-catalogers] Angular staff client catalog

Thu Sep 19 07:12:52 EDT 2019

Thanks, Jane!  I wish I had found that Launchpad bug yesterday -- it helps
a lot, especially the screenshots!    I would love it if we could revisit
this again at a meeting, maybe we should do this on a regular basis to keep
in touch with the progress.

On Thu, Sep 19, 2019 at 12:06 AM Jane Sandberg <sandbej at linnbenton.edu>
wrote:

> I'm a fan of the experimental staff catalog.  It has some nice
> quality-of-life improvements (like the holdings view, which -- as far
> as I'm concerned -- takes the best of the XUL and Web client holdings
> views).  And I think there will be more and more of those improvements
> as the project progresses.
>
> Bill Erickson has been adding more and more data to the experimental
> catalog lately: https://bugs.launchpad.net/evergreen/+bug/1839670
>
> I'll also say that Bill has been very receptive to feedback from this
> group.  Maybe in an upcoming Cataloging Working Group meeting we could
> take a look at the very latest version of the experimental catalog and
> put together some feedback about what is missing.
>
> On Wed, Sep 18, 2019 at 6:16 PM Thomsen, Elizabeth <et at noblenet.org>
> wrote:
> >
> > Thanks, Terran, that's helpful and reassuring.  As proof of concept, and
> the way the search elements are displayed and work and all that, it's
> fine.  I have no problem with what's there, only what's not there!
> >
> > On Wed, Sep 18, 2019 at 9:10 PM Terran McCanna <
> tmccanna at georgialibraries.org> wrote:
> >>
> >> I have not had a chance to play with 3.3 or 3.4 yet, but it was my
> understanding from Bill's demos earlier this year that he only put enough
> content into the initial display so that it could function as a proof of
> concept to be sure the core search functions and filters were working
> correctly, and that the additional displayed elements were still to be
> worked out after that.
> >>
> >> As for the public and staff catalogs matching or not, I could go either
> way as long as all parties are presented with what is most useful to them.
> Having a single catalog with select elements hidden/displayed for each
> audience is easier to maintain over time. I expect that once the new staff
> catalog is fleshed out to everyone's satisfaction, it could then be re-used
> in the redo of the public catalog, so we would then be back to having the
> same experience in the staff and public catalogs.
> >>
> >> Terran McCanna
> >> PINES Program Manager
> >> Georgia Public Library Service
> >> 2872 Woodcock Blvd, Suite 250
> >> Atlanta, GA 30341
> >> 404-235-7138
> >> tmccanna at georgialibraries.org
> >>
> >> On Wed, Sep 18, 2019, 5:04 PM Thomsen, Elizabeth <et at noblenet.org>
> wrote:
> >>>
> >>> How are people feeling about the Angular staff catalog?  Have you
> shown it to library staff?  We have 3.3 on a test server and this morning
> we turned on the Experimental Catalog to showed to our catalogers for
> feedback.  They were really unhappy with it.  They value having the staff
> and patron views of the catalog match, and they want to see the full view
> of the bibliographic record whether they are determining whether or not the
> record is a match for an item they are inputting, or looking at record they
> added from a workform or Z39.50 to spot and correct problems.
> >>>
> >>> The grid only has a few pieces of information from the bibliographic
> records that are useful in terms of matching the record to the item in hand
> -- the author, the title, the year and the edition statement, if any.  No
> format, publisher, description, ISBN, no links to other formats and
> editions, no cover image.  I appreciate that they added a link to View in
> Catalog, which takes you outside the staff client to the public catalog,
> but that seems very cumbersome for something people are going to have to do
> for practically every record.  And won't public service people have all the
> same problems looking up records for patrons to place holds?
> >>>
> >>> I understand the need to Angularize this, and appreciate the work
> that's gone into it.  There's a lot I like here in terms of the UI, but
> with this sparse display of the bib record, it looks like a real step
> backward to us.
> >>>
> >>> --
> >>> 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
> >>
> >> _______________________________________________
> >> Evergreen-catalogers mailing list
> >> Evergreen-catalogers at list.evergreen-ils.org
> >>
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers
> >
> >
> >
> > --
> > 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
>
>
>
> --
> Jane Sandberg
> Electronic Resources Librarian
> Linn-Benton Community College
> sandbej at linnbenton.edu / 541-917-4655
> Pronouns: she/her/hers
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers
>

-- 
Elizabeth B. Thomsen
Member Services Manager
NOBLE: North of Boston Library Exchange
Danvers, Mass.
www.noblenet.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20190919/a04b6ca9/attachment.html>