I really like the demo - it looks very sleek and "modern", especially when
compared to the current staff client.
One thing I'm wondering - how would it handle i18n? Currently all the texts in
the demo html-files are hard-coded. I guess one way would be to turn all the
html "templates" into TT
On Wed, Oct 16, 2013 at 3:50 AM, Kallinen Pasi wrote:
>
> I really like the demo - it looks very sleek and "modern", especially when
> compared to the current staff client.
>
> One thing I'm wondering - how would it handle i18n? Currently all the
> texts in the demo html-files are hard-coded. I g
Hi Chris,
i finished today morning new testing server hosted on my home
server/desktop/router/virthost...
New testing virtual server has this configuration 4GB RAM, 2core, 50GB HDD
64 bit Debian 7, EG 2.4.2
Import currently running over seven hours. 6k5 bib records (with minimal
record complex
Hi Chris,
i finished today morning new testing server hosted on my home
server/desktop/router/virthost...
New testing virtual server has this configuration 4GB RAM, 2core, 50GB HDD
64 bit Debian 7, EG 2.4.2
Import currently running over seven hours. 6k5 bib records (with minimal
record complex
Broadly, the reports module needs better documentation. Specifically, what
the fields are, what they do, and how they relate.
When I used to work with Millennium you had Item records, Bib records,
Patron Records, and Order records (and that was it).
You could use Bib records connected to item a
I would echo John's words. I know most people cringe when it comes to
reports and having better/more documentation might alleviate some of that.
On Wed, Oct 16, 2013 at 11:11 AM, John Mundy wrote:
> Broadly, the reports module needs better documentation. Specifically,
> what the fields are, w
John,
I'll share this, since I don't know of anything better that has superseded it.
In 2008, PINES/GPLS staff, with assistance from a volunteer from a PINES
library, created a basic and an advanced reporting guide that applied to
Evergreen 1.2, but is still somewhat useful since the basics of
Hello, Amy.
Here is a quick update from PALS.
East Grand Forks Campbell Library (East Grand Forks, MN) will begin using
Evergreen Acquisitions starting in January of 2014. EGF Campbell Library
migrated to Evergreen in August of 2012. The library and PALS staff have been
testing the Evergreen A
Hello all,
I am pleased to announce that Evergreen 2.5-rc1 is now available for download.
Once again, thank you to the many folks who put in some extra time to help us
get to this point! You can grab RC1 from the downloads page here:
http://evergreen-ils.org/egdownloads/
Given the relatively
Thanks John, couldn't have said it better.Lynne WalshChesterfield County Library843.623.7489Chesterfield, SChttp://www.chesterfield.lib.sc.us
Original Message
Subject: Re: [OPEN-ILS-GENERAL] Need community suggestions for
back-filling EG documentation
From: "John Mundy"
Thanks for your suggestion, and the others that chimed in on your topic! Lets
keep the suggestions coming.
Yamil
On Oct 16, 2013, at 11:11 AM, John Mundy wrote:
> Broadly, the reports module needs better documentation. Specifically, what
> the fields are, what they do, and how they relate.
Dan,
+1 for your list of goals
I do have 1 tiny commit, but I think that we could satisfy #4. Our
database was started in the 1.6 days and has encountered problems at
pretty much every upgrade which makes it good to test against in my
opinion. Also, Blake is new to the upgrade process so a fr
Dan,
We will also be upgrading our test server to 2.5-rc1 from 2.5-beta1 some time
this week.
I'll report back with any problems.
Hope that helps!
Chris
- Original Message -
> From: "Justin Hopkins"
> To: "Evergreen Discussion Group"
> Sent: Wednesday, October 16, 2013 2:54:35 PM
>
My suggestion would be for more detailed documentation on the Alternate Serial
Control View, creating a subscription specifically. I'd like to see step by
step instructions with screen captures on what to expect.
This is not an area where we have no documentation, however, what is available
is
Hi all,
Looking for wisdom from the group if you have a moment or two.
-
Looking at the stat cat editor in the staff client, I see a field for OPAC
visibility. However, I can't seem to find where or how this is implemented
in the TPAC. Any ideas or leads or links you can share will
Do you load bib records and holdings (via MARC tag 852) from
TitleSource into Evergreen?
If so, would you share a screen shot of your MARC profile on
TitleSource?
I'm using the default Evergreen 852 export format. I've set up the
MARC profile on Titl
Michele,
If I recall correctly (not near EG at the moment), owning lib is subfield b
for that holdings format, but so is circ lib, so the holding tag will need
two subfield b's. What I don't remember is whether they can be short names
or if they need to be database id's.
--
Jason Etheridge
| Su
17 matches
Mail list logo