These are pretty cool solutions, I think maybe it is time for us to stop
logging them in every day :)
Ryan, I have one question about your example config. Have you had issues
using a 301 redirect rather than 302? It seems like that could potentially
prevent the cookie from being set on reload,
Hello Eva,
The AngularJS interfaces are using the built-in currency filter, which
supplies a dollar sign by default. More here:
https://docs.angularjs.org/api/ng/filter/currency
It does appear that the filter can specify a different symbol; it is fairly
limited otherwise. The newer Angular
Hello all,
It is my pleasure to announce general availability of the first stable
release for Evergreen 3.3. The download for Evergreen 3.3.0 is available
here:
https://evergreen-ils.org/egdownloads/
As we close out this development period, I think the overall theme of this
release can be
Hello once more,
Just a quick note that today we reach the penultimate milestone in the 3.3
release process, the Release Candidate stage. Any bug fixes which you
would like in the RC should be committed by the end of the day today,
3/20. We made some good progress during bug squashing, but
Hello all,
On behalf of the Evergreen community, I am pleased to (finally) announce
last Friday's release of Evergreen 3.3-beta1. The beta release is a
significant milestone in each version's journey, as it marks the point
where the release is considered feature complete. You can grab your copy
and we can
probably work it in. I intend to start doing internal building and testing
starting tomorrow morning, and will not be terribly keen on straggling code
walking in unannounced. Thank you for your diligence and understanding.
Sincerely,
Dan
On Wed, Feb 6, 2019 at 12:40 PM Daniel Wells
Dearest fellow Evergreeners,
After several months of quiet contemplation and tireless toiling by many
members of the Evergreen community, it is past time for a brief message
from me, your minimalist 3.3 release manager.
First, as we enter this final trimester of the release process, it seems
Praha 2
>
>
>
> čt 8. 11. 2018 v 19:09 odesílatel Donald Butterworth <
> don.butterwo...@asburyseminary.edu> napsal:
>
>> Dan,
>>
>> We are on 3-1-2. Thanks for looking into this!
>>
>> Don
>>
>> On Thu, Nov 8, 2018 at 11:26 AM Daniel Wells w
Hello Don,
What version of Evergreen are you running?
I believe this to be a bug. We are on a semi-custom but recent 3.0 and
seeing the same behavior. The titles are also not showing up in search
suggestions, so maybe that is related, maybe not. I am going to start
looking into this, and will
Dear Evergreen Community,
After some consideration, I am writing to offer myself as release manager
for 3.3.
Our library is an independent academic installation, and will be live on
Evergreen for 9 years this December. I served as Release Manager most
recently for 3.1, and previously for
Hello all,
Very happy to see the term "Holding" getting some traction. I would also
agree that changing the record-level "Add Copies" button to "Add Holdings"
makes a lot of sense!
Furthermore, after 9 days of suspense, I have finally found time to unveil
the one term I feel has been misused in
Hello all,
Based on volunteer availability, August point releases for Evergreen 3.0
and 3.1 are set for 8/22.
Sincerely,
Dan
Janet, I can speak to those textual changes, as I am probably responsible
for both. They were attempts to improve accuracy and consistency within
the great ball of changes touched by the omnibus branch. Whether these
attempts succeeded is of course debatable :)
To explain a little further,
Hello all,
Just a quick update, maintenance releases 3.1.3 and 3.0.9 are now
tentatively scheduled for next *Thursday*, June 28. If plans change due to
project activity or buildmaster availability, I will send another update on
or before that day.
Sincerely,
Dan
Hello Yamil,
This sounds like a fun and very doable project. Just spitballing:
1) From what I can understand, the conceptual requirement is a flag which
can both block circulation (etc.) and be changeable by the user (on their
own account). We certainly have things which do one or the other,
Hello all,
As part of my (glacially slow) attempts to move the dev docs project over
to the main wiki, I spent a few days right before the conference doing some
cleanup of the main wiki. Here are a few things worth noting about that
process:
1) There is a new namespace for "archiving" pages
Hello all,
After some consideration and consultation with the community, we have
decided to postpone point releases scheduled for today until Wednesday of
next week (or a bit later, please read on). There are a number of
high-priority bug fixes very close to completion (particularly for
Sandberg <sand...@linnbenton.edu>
wrote:
> Hi Dan,
>
> Are you still accepting responses for this survey? I know our circ
> folks were interested in this, but haven't had a chance to fill it out
> yet.
>
> On Thu, Apr 19, 2018 at 4:36 PM, Daniel Wells <dbwe...@g
Hello all,
There are currently a variety of bugs involving "lost" vs. "long-overdue",
and it appears (to me at least) some of that may be caused by different
understandings of what each status means (or should mean). We all want the
system to work as best as possible for as many people as
Hello all,
Our current practice is to only allow bugs to be targeted to a release only
if there is code ready for testing. This change was made several years
back to help focus community efforts on testing of existing fixes, and also
to avoid a lot of extra work in constantly moving huge numbers
Hello all,
After several positive reports from testers, and following shortly after
the security releases on Wednesday, the 3.1 release candidate has been
rolled over to become the official 3.1.0 release. As expected, the only
changes from RC to 3.1.0 were the template security patches and minor
Hello all,
As of yesterday morning, the Evergreen 3.1 Release Candidate is available
on the main downloads page:
http://evergreen-ils.org/egdownloads/
While we haven't always been consistent over the years, this release
candidate is meant to not be a final "beta", but to be a preliminary
Hello all,
Time marches on, and preparations for the 3.1 release candidate are already
underway. Please note, due to a personal scheduling conflict, I am
delaying the official cutoff for the RC by one day. You now have until
2:00pm (EDT) on Thursday, March 22, to push reviewed bugfixes freely
Hello all,
I am pleased to announce that the first (and likely only) beta release for
Evergreen 3.1 is available on the main Evergreen downloads page:
https://evergreen-ils.org/egdownloads/
Being a beta release, Evergreen 3.1 is now considered to be feature
frozen. Overall, we can all be proud
!
Sincerely,
Dan
On Mon, Feb 19, 2018 at 12:43 PM, Daniel Wells <dbwe...@gmail.com> wrote:
> Hello all,
>
> At some point in the last few weeks, I realized that I had broken one of
> the "rules" of release management. The period between feature-slush and
>
Hello all,
At some point in the last few weeks, I realized that I had broken one of
the "rules" of release management. The period between feature-slush and
feature-freeze is best attended to with undivided attention, but at it
would turn out, one of the two weeks for that period coincided with a
e documentation to evaluate and work
> on if someone is adding comments to a specific file.
>
>
>
> Josh Stompro - LARL IT Director
>
>
>
> *From:* Open-ils-general [mailto:open-ils-general-
> boun...@list.georgialibraries.org] *On Behalf Of *Daniel Wells
> *S
Hello all,
As I look out my window at a fresh 6" blanket of snow, I would like to
remind everyone that we have reached our "feature slush" point for the 3.1
release. What does this mean? From the wiki:
*feature slush*: major planning for features is complete
- at this point, all
Hello all,
We are now entering the busy period of the release cycle, so I would like
to take a moment to highlight a variety of efforts underway for the 3.1
release.
1) We are about two weeks away from "feature slush", currently set for Feb.
9. What does this mean? To quote from our
holdings. I'm not sure exactly why but it is my
> understanding that certain vendors that we work with need it there.
>
> If there is some other place we should be doing this I would like to
> know. It seems to me WWW/SuperCat.pm is the only place to do it.
>
> Thanks again!
>
Hello John,
This part of the code is pulling data from the unapi.bre() function in the
DB, so in this case, you want 'copy_id', i.e.:
...
f => $copy->getAttribute('copy_id'),
...
This said, I think we'd all be interested to know exactly what you are
trying to accomplish, as there are other
Dear Evergreen friends,
Welcome to Evergreen 3.1!
As a first order of business as Release Manager for this release, I propose
the following as a base schedule. This proposal is modeled heavily on the
successful schedule for 3.0, but getting us back within our typical time
frame (March release).
Dear Evergreen Community,
I am writing to offer myself as release manager for 3.1. The following
proposal may seem familiar, as it borrows heavily from my offer for 3.0 :)
Our library is an independent academic installation, and will be live on
Evergreen for 8 years this December. I served as
Hello Irene,
If "no." is the top level, and it just increments forever, then you don't
need a restart at all. So, something like this (untested):
["2","0","8","1","a","no.","i","(year)","j","(month)","w","q"]
Does that do what you are after? If so, I can update the wiki page you
referenced.
Hello Irene,
This issue is an inherent weakness in the MFHD specifications, as the "x"
restart only affects the top-level numbering, in this case volume (as you
discovered).
There is in Evergreen a (not well known) workaround, though, which is to
specify "4" issues, then list winter first.
Hello Glen,
The setting is an Org Unit setting, i.e. the ones you can set via the
"Library Settings Editor". It should be there under "Lost materials
processing fee". Does that help? I know the settings can get rather
jumbled. You might also need to change your Org Unit context in the editor
Not sure about Supercat; what about using unAPI instead? Something like:
http://ulysses.calvin.edu/opac/extras/unapi?id=tag:open-ils.org,2016-11-01:biblio-record_entry/568925/CALVIN=marcxml-full
In this example, 568925 = database ID and CALVIN = org_unit shortname.
Dan
On Thu, May 18, 2017 at
Hello all,
A bit later than hoped, here are an assortment of small proposals for
(re-)organizing the developer documentation on the Evergreen wiki. The
overall goal is to develop what we have and what will come into a useful
and cohesive corpus.
1. Use the wiki
As mentioned in our talk, after
Hello Jesse,
For your first issue, it appears you have some kind of encoding problem in
some of records. This is very common for any record with foreign
characters. Without getting into too much detail, MARC records are
generally supposed to use UTF8 encoding (a modern, universal encoding) or
Hello all,
Since our project adopted the idea of "release managers" in 2012, we have
managed to select each by consensus. While we typically had elections, the
nominees until now have always run unopposed.
I find this tradition to be a beautiful thing, and one I would like to see
preserved for
[I apologize for possible duplication; my calvin.edu email is getting
"greylisted" by the mailing list, so I am sending this a second time from
Gmail.]
Dear Evergreen Community,
I am writing to offer myself as release manager for the upcoming 3.0
release.
Our library is an independent academic
41 matches
Mail list logo
