To echo Dan, and without reading ahead to the weekend's posts,
developers usually talk about APIs in terms of methods of accessing
the functions of a system. Usually, the APIs are bundled and
published because the core system is closed in some way or licensing
is involved. If you want
Hi Steve,
I'm on version 2.0.7 and the hard due date I have created is called end of
semester with spaces. Does this mean that later versions will not accept the
spaces and that we should rename prior to upgrading?
Thanks!
Gordana
On 5/13/2012 at 12:29 PM, in message
Thanks, All. I know we don't need APIs in the same sense that a
proprietary system does. However, I've spoken to some developers of other
products who are interested in integrating their product with Evergreen and
I keep hearing that this is very challenging because it isn't clear what
does what
Is anyone cataloging and circulating audio visual equipment with Evergreen?
If so, would you share what you are using for a fixed field 'type'?
We are interested in putting these records in the first time ( ;D) in such
a way that our patrons will have a filter or an easy way to locate all the
AV
Hi Trisha,
You can create a MARC record for just about anything. We added one really
basic one for a bike pump that we sign out (we are by the bike racks at our
school).
If all the AV stuff lives together, I'd create a shelving location for
them, so you can filter on that or do a search on that
I had written:
*please* let's not develop an *integrated* link checker for Evergreen at all
On Fri, May 11, 2012 at 06:17:21PM -0400, Duimovich, George wrote:
Disagree -- there's no reason why link checker code couldn't be
developed to be used (or easily adapted) to service both general
I would be surprized if there isn't a link checker already out there that could
meet the needs. Probably thousands have been written by now. For example,
Debian has a package: http://linux.die.net/man/1/linkchecker.
That said, sometimes it just makes sense to write one that very specifically
thousand answers. A
librarian
can
bring you back the right one. The Guardian (London)
-- next part --
An HTML attachment was scrubbed...
URL:
http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20120514/c59a722d/attachment-0001.htm
PINES catalogers catalog equipment for circulation frequently. However, we
do our original cataloging on OCLC and bring the record into PINES. We
don't catalog directly into PINES unless the item is ephemeral in nature
and won't be retained.
The Type would be r : Three-dimensional artifact or
Hi all-
Plans are underway for the June edition of the Evergreen newsletter. It
will hit the presses sometime in mid-June, but there's no time like the
present to send me your Evergreen news item or items.
Just come up on Evergreen?
Have some bit of Evergreen development in the works?
Today, the Evergreen development team released Evergreen 2.0.11, the
final bug fix release for the Evergreen 2.0 series. This release
includes fixes for over 35 publicly reported bugs as listed here:
https://launchpad.net/evergreen/+milestone/2.0.11
This announcement ends the community's
I think better documentation might help. It's been awhile since I looked,
but in February at code4lib some people wanted to play around with
Evergreen APIs and they reported having a tough time finding the
information they needed. I think Karen Coombs, from OCLC, contacted Dan
Scott directly to
12 matches
Mail list logo
