<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>eclectic librarian - Latest Comments in NASIG 2008: Next Generation Library Automation &amp;#8211; Its Impact on the Serials Community</title><link>http://eclecticlibrarian.disqus.com/</link><description></description><atom:link href="https://eclecticlibrarian.disqus.com/nasig_2008_next_generation_library_automation_its_impact_on_the_serials_community/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 11 Jun 2008 16:54:12 -0000</lastBuildDate><item><title>Re: NASIG 2008: Next Generation Library Automation &amp;#8211; Its Impact on the Serials Community</title><link>http://eclecticlibrarian.net/blog/2008/06/nasig-2008-next-generation-library-automation-its-impact-on-the-serials-community/#comment-3571083</link><description>&lt;p&gt;Yes, I meant EDI. Tried to stay away from the curse of the &amp;lt;acronym title="three letter acronym"&amp;gt;TLA&amp;lt;/acronym&amp;gt; in my reply.&lt;/p&gt;&lt;p&gt;As for the presentation, Steve, I kind of agree with you. I wish he would have skipped to the last part instead of rushing through it, since it seemed to be the bit that was actually related to serials. Also, then it wouldn't have been so much like the presentation I saw at Computers in Libraries and more focused for NASIG.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anna Creech</dc:creator><pubDate>Wed, 11 Jun 2008 16:54:12 -0000</pubDate></item><item><title>Re: NASIG 2008: Next Generation Library Automation &amp;#8211; Its Impact on the Serials Community</title><link>http://eclecticlibrarian.net/blog/2008/06/nasig-2008-next-generation-library-automation-its-impact-on-the-serials-community/#comment-3571084</link><description>&lt;p&gt;Joshua, I agree with Anna. (Mind you, it has been about two years -- I think -- since I last took a close look at Koha.)  Having an acquisitions and serials module (or separate modules for each, whatever) doesn't mean that they are sufficient and rich enough in functionality yet, and that was certainly true when I last checked.  EDI is but one part of that.  (I think EDI is what Anna refers to but maybe not.)  There needs to be rich functionality for check-in, claiming, and many other things as well.  What about ledger/funds management?  What about ways to ease the burden of recreating them each year?&lt;/p&gt;&lt;p&gt;On a more general level I want to say that I thought Marshall's presentation was good but it wasn't what I would have expected from a vision session and was therefore a bit disappointing. But YMMV as they say.&lt;/p&gt;&lt;p&gt;Steve&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steve Oberg</dc:creator><pubDate>Wed, 11 Jun 2008 15:42:46 -0000</pubDate></item><item><title>Re: NASIG 2008: Next Generation Library Automation &amp;#8211; Its Impact on the Serials Community</title><link>http://eclecticlibrarian.net/blog/2008/06/nasig-2008-next-generation-library-automation-its-impact-on-the-serials-community/#comment-3571086</link><description>&lt;p&gt;Joshua: If it does, they certainly aren't at the level we need them to be in order to function. For example, the acquisitions module cannot handle electronic invoicing, which is essential for most libraries these days. We don't have the staff to hand-enter each line item!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anna Creech</dc:creator><pubDate>Mon, 09 Jun 2008 23:31:26 -0000</pubDate></item><item><title>Re: NASIG 2008: Next Generation Library Automation &amp;#8211; Its Impact on the Serials Community</title><link>http://eclecticlibrarian.net/blog/2008/06/nasig-2008-next-generation-library-automation-its-impact-on-the-serials-community/#comment-3571085</link><description>&lt;p&gt;um ... Koha has had serials and acquisitions for several years now Marshall.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joshua Ferraro</dc:creator><pubDate>Mon, 09 Jun 2008 07:59:15 -0000</pubDate></item></channel></rss>