I look at the funding sources as the precise account used by the business
office.
I have examples here.
http://intranet.cwmars.org/node/932
Tim
On Tue, Sep 11, 2012 at 6:55 PM, Mary Llewellyn mllew...@biblio.org wrote:
I tell my libraries to think of the funding source as the big pot of
Rebecca,
If I were you, I would use the Classic Item List source, which contains all
the fields you're looking to display (including use count). Here's what I just
did for a test template:
Use Classic Item List source; nullability selection disabled
Displayed Fields:
Classic Item List -
Quoting Mary Llewellyn mllew...@biblio.org:
I see 2 ways to go: find and export all the bibs involved, delete the
obsolete 856s in a third-party MARC editor, then load the bibs back in and
replace the bibs in the database. Or, develop some backdoor way to remove
the 856s using SQL, just for the
This is the sort of thing that I'd do with perl, since there is the nice
MARC::Record module and the OpenSRF/OpenILS modules used by Evergreen's
backend have all the routines that you need to do this.
There's also a MARC Batch Edit UI, though I don't have any practical
experience with it.
Mary,
Here's a perl script I used to make some changes to 856 tags in our
system. You might be able to use it as a model for what you're trying to
do. Let me know if I can answer any questions about it.
J
***
#!/usr/bin/perl
use strict;
use DBI;
use Config::IniFiles;
use MARC::Record;
use
The MARC Batch Edit in Evergreen is still kind of clunky and I never get the
results I want from it.
Thanks to everyone who has offered up SQL/Perl solutions to my question. I
can see I'm in over my head for these approaches, so I'm using option 1,
exporting, doing an external edit, then
Hi all-
It's that time again. I need to collect news items for the Fall edition
(Sept/Oct) of the Evergreen newsletter.
So if you're sponsoring some new development or bringing up a new library or
doing something cool with the Evergreen OPAC or anything else you have going
on, please drop
Hey Chris,
I gave it a shot, and got the following error message when I went to output:
DBD::Pg::st execute failed: ERROR: relation reporter.classic_item_list does
not exist at character 265
I also tried Classic circulation view and enabling the nullability selection.
I'll keep poking at it
Rebecca,
I gave it a shot, and got the following error message when I went to
output:
DBD::Pg::st execute failed: ERROR: relation
reporter.classic_item_list does not exist at character 265
So you were able to create the template with the Classic Item List source but
you got this error?
I am going to assume that it isn't there because nothing installs it
by default.
There is an example reporter extension SQL file that contains it, but
it doesn't get run by default during an install.
Which makes me wonder if we should be removing, or at least commenting
out, the IDL
10 matches
Mail list logo
