I do like Holdings transfer. I think it is a good descriptor of what we are
doing with the functionality.
A little quibble, though with not having the button labelled Add volumes
and copies. I realize that is cumbersome, however, it is more descriptive,
especially from a cataloger's point of
> From Jennifer:
>
> If we stick with item (which implies copy, call number, and barcode), that
>> keeps it very simple. Copies has the implication of multiple copies of
>> a title of a book, whereas we mean more than that in most systems because
>> we will have different kinds of physical
Thanks for the feedback everyone! We certainly can tackle the call number /
volume issue on the survey, though I suspect I know where the votes will
fall on that question.
>From Dan:
As we do so, we should also keep in mind how these labels overlap and
> interact. Otherwise, we might paint
+1
I agree with Jennifer about consistency being desirable, and preferring the
term items.
On Wed, Aug 8, 2018 at 12:07 PM, Walz, Jennifer wrote:
> All –
>
>
>
> I would prefer the ITEM and ITEM LOCATION designators – and consistency
> across all functions / buttons / screens / views etc
All –
I would prefer the ITEM and ITEM LOCATION designators – and consistency
across all functions / buttons / screens / views etc would be very welcome.
As Dan and Lynn point out below, there have been VAST inconsistencies and also
problems with function.If we stick with item (which
Also, it might be helpful to collect a little more information about
your iPads too. Like what version of iOS they're running and whether
you're using Safari browser on them to access the web client.
Just a cursory test with a public Evergreen 3.1.4 server with Safari
on my iPhone running iOS
Nadine,
I don't have a solution but just to get some ideas rolling. The timing
sounds very much like the SSL warning and/or certificate minimum
requirements that Google has told the world about:
https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html
Effective August 1st
Hi all,
let me add a few notes about consistent terminology both from the
perspective of a person who trains staff to work in Evergreen and from the
point of view of the Evergreen translator.
In both cases I would definitely advocate for the maximum consistency of
used terms (however, I also
