Dear Jason,
We have simply added *-v eg_version=2.3.1* to the script so that it became
*psql -U evergreen -h localhost -v eg_version=2.3.1 -f
version-upgrade/2.3.0-2.3.1-upgrade-db.sql evergreen*
Yet, the command did not work. Should we modify the command in a different
way? If it is not difficu
Hi all,
Evergreen 2.3.2 and 2.2.4 have been released. These releases contain
a number of bugfixes since the last releases back in November. See
this page for links to the source code, staff client, release notes,
changelog and more: http://evergreen-ils.org/downloads.php
The bugfixes covered in
Hi Everyone,
I have just started working with Evergreen and am new to this list. I am
replacing Jennifer Turner at PALS in supporting Evergreen. I only started a
couple of weeks ago, but I already have a question for you.
One of our libraries is wondering how to run a report with a filter for
Hey Jennifer,
Sitka has a lot of libraries and each one is pretty much walled off and has
its own circ policies. The most important part for Sitka is enforcing
hard hold boundaries so that holds don't get captured outside of the walls,
as this can create misleading expectations for patrons where
Hello!
I'm looking to have a call or two with implementers of Evergreen who have a
shared instance with more than 1 library but each library has it's own
permissions, circ rules and so forth. Basically, it all lives in 1 but each
library is walled off and on its own.
Has anyone done this? If s
So long as no one tries to rig the vote I don't think there is a big
danger. If multiple staff in a consortium are involved in the community,
are aware of it and respond I think that is right.
Now, if I were to say broadcast the form around SCLENDS and get everyone to
respond to it to never watch
Hi Yamil,
I don't see any reason to limit voting. I think this poll is meant to be a
"finger on the pulse" type measure rather than anything officially binding.
One of my GPLS colleagues and I have already voted and she and I probably don't
even have the same perspective on the ranking, for i
Should we limit our votes to one vote per consortium/system/branch, or
should we have an extra field stating if we are voting as an
individual or representing an institution?
Thanks for putting this all together,
Yamil
On Dec 20, 2012, at 8:55 AM, Peters, Michael wrote:
As Mike R suggest
Quoting Araik Manukyan :
Dear friends,
We are upgrading from Everegreen 2.2.1 to 2.3.1. The transition was going
smoothly untill the final step. When try to upgrade the Evergreen database
scheme with the command
Yeah, I think that upgrade script has a bug that was fixed later.
You can get
