Hi,
On behalf of the buildmasters Dan Wells and Blake Henderson, the
release maintainers Kathy Lussier and Mike Rylander, and all who have
contributed to the releases, the Evergreen community is pleased to
announce two maintenance release, 2.11.8 and 2.12.5.
For details of the improvements in
Hi,
But without complications, would life be interesting? ;)
More seriously, I could envision a way for the web staff client to
link to the appropriate version (and section) of the community
documentation in a reasonably maintainable way. Most pages in the web
staff client have predictable
Life is complicated, isn't it?
What I had in mind with my "constantly updated" phrase was that the
documentation was at a community site that would consist of the most recent
documentation. I wasn't taking into account the need to have all the
different docs for all the different versions. I
Michelle,
Wow! That is really helpful – and a good step to try first. I had no idea of
the code even to be used for the ‘circulating library’ or where to find it.
Thank you for sending this. In this case, when patrons hit that reply
button, they will get closer to the library who can
I didn't think about this until I saw Kathy's message pop up but I could
also imagine a location where they don't want traffic going outside their
defined network for a variety of reasons and it would have to be easy to
modify or it would break for them.
Rogan Hamby
Data and Project Analyst
Hi,
I think it has some challenges also. One of these is that some
Evergreen users customize their installs. You can always say "oh, then
they have to modify their links to go to different docs too." I'd
want to hear from community members that might affect.
Yes, that was my first
Hi Donald,
When you say "constantly updated" I'm imagining that you're not thinking of
something bundled with the distribution but links that go back to the
community site? At the least this would have to be bound by version I
think and the granularity of the version it links to would have to be
Jillianne and Jane,
I like what you have done a *lot*. It makes so much sense and is less
intimidating for us cataloger types who shy away from system
administration.
I wonder ... could the concept be taken a step further to include hot
links, in Webby, to a constantly updated HTML version of
> This might be a bad way to do this, but you could clone the A/T
> template for each library and put in filtering logic on the target
> array. If the array ends up being empty, produce an empty document to
> send to the SendEmail reactor.
I think whenever I think up stuff like this,
On Wed, Aug 23, 2017 at 5:54 PM, Terran McCanna
wrote:
>>>Is there a way to group notices by circulating library?<<
>
> I'm not really sure - I would think it would have to group it by both usr
> AND circ library (so a user might get multiple emails, but each email
Jennifer,
The notice grouping discussion aside, you can try the following for your
>From address to get the email address of the library at which the checkout
occurred:
From: [%- params.sender_email || helpers.get_org_setting(
target.0.circ_lib.id, 'org.bounced_emails') || default_sender %]
I like the way things are broken down by user groups. It makes it much
easier to locate the needed documentation. Just through my quick review I
found a feature I was not aware of and will try using. So I think it is
great.
Meme
On Wed, Aug 23, 2017 at 4:37 PM, Mary Llewellyn
12 matches
Mail list logo