[OPEN-ILS-GENERAL] What are your requirements for Evergreen?

[Deb Bergeron]

Edward,

Another deal breaker is an ILL module.  Currently, our III system has an 
ILL system that we use for our consortial resource sharing.  Outside the 
consortium we use ILLIAD.  As someone else on the list mentioned, ILLIAD 
is a very good ILL system.  The only problem is due to the NCIP issues, 
it cannot fully integrate with the our system, thus requiring more work 
for staff librarians.  Additionally, we also have a state-wide system, 
MNLINK, for the same reasons, cannot integrate with our ILS system.  So, 
we have 2 ILL systems, all transactions from these systems have to be 
updated by a human to keep the catalog and circulation current within 
the III system.

What's needed is the willingness of the ILS and the ILL system to 
incorporate a fully functional NCIP protocol and standard that will 
allow the transactions to take place without human intervention, thus 
saving time and money.

Deb

Edward Corrado wrote:
>
>
> Dan Scott said the following on 02/04/2008 12:53 AM:
>> Hi Deb:
>>
>> I'm going to push you for some more information here - and remind you
>> that the question I asked was:
>>
>> "What are the base requirements that have to be in place before we, as
>> an academic library, or consortium of academic libraries, can migrate
>> to Evergreen?"
>>
>> Nice-to-haves are fine, too, but we need to keep them identified as
>> such to prioritize tasks appropriately (unless, of course, having the
>> nice-to-have would outweigh any other consideration - like: "If
>> Evergreen came with a built-in ice cream maker, I couldn't care less
>> if it supported EDI!")
>>   
>
> If Evergreen came with a built-in ice cream maker, I couldn't care 
> less if it DIDN'T supported EDI! The lack of a completed acquistions 
> module is also a deal-breaker, but it is in the works.
>
> Another deal breaker is a Z39.50 server (I know about Joshua's one 
> that Dan mentioned earlier, but we need one that is currently being 
> maintained and supported).
> Also, an academic holds/reserves functionality is important, hopefully 
> with built-in electronic reserves capability. Maybe if something could 
> be tied into something like ReservesDirect ( 
> http://www.reservesdirect.org ).
>
> The non-deal breakers, but things that would be rally nice to have....
>
>
>    Media/Room scheduling
>
>    Support for MARC Holdings format
>
>    Authority Control functionality (at a non-network level)
>
>    Bulk loading of records at a local level
>
> Edward
>
>
>

-- 

Deb Bergeron <mailto:bergeron at macalester.edu> System Admin: User Support
CLIC Consortium <http://clic.edu>
1619 Dayton Avenue, Suite 204A
Saint Paul, MN 55104
O:*651.644.3878* C:*651.487.7609* F:651.644.6258


-- 

Deb Bergeron <mailto:bergeron at macalester.edu> System Admin: User Support
CLIC Consortium <http://clic.edu>
1619 Dayton Avenue, Suite 204A
Saint Paul, MN 55104
O:*651.644.3878* C:*651.487.7609* F:651.644.6258

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-general/attachments/20080204/dd816577/attachment.html