How to make Evergreen "your own" in a consortial environment.
Can others add to this list? Comment on / disagree with the items? Thanks.
- While cataloguing, use the x90 tags with the $5 subfield to identify your
own library. The public PAC can be set to display or not display these to your
local patrons. Your reports (those that include bib info) can use the $5
subfield to manipulate data. Also the advanced search (marc tags and
subfields) can make use of it.
- Extract data and do something with it
a> report generator Evergreen's built in (limited)
b> FM_IDL reports (IDL= Intermediate Definition Language file) need
clarification here????
c> Crystal Reports with an interface planned?? you'll be able to
access data and write reports to your heart's content!
d> custom reports using SQL at the "ground level."
- Circulation modifiers - either as javascript or part of the database - allows
you to have your own loans periods, fines, non-circulating items etc.
- OpenSRF: access the functions that the staff client and the OPAC use
directly. Write your own OpenSRF methods.
http://journal.code4lib.org/articles/3284
This could evolve into something like the "OCLC Developer Network Handbook :
http://worldcat.org/devnet-real/images/3/37/Oclcdevelopernetworkhandbook.pdf
- Become a skilled Evergreen programmer and contribute directly to "the trunk."
(need a concise definition of "the trunk." )
Kevin Kierans
TNRD Library System
http://www.tnrdlib.bc.ca
(part of Sitka)
http://sitka.bclibraries.ca/
