Hi Dan, On 2/1/08, Dan Scott <[EMAIL PROTECTED]> wrote: > Just to try to clarify ERMS support, are you talking about all 47 > functional requirements in Appendix B of > http://www.diglib.org/pubs/dlf102/ or just some subset?
I think a subset would be sufficient to start with. I hope current and potential ERMS users chime in, as my experience lies in supporting implementation of an ERMS, not using one, but my own subset of important requirements would include license management, managing the selection and acquisition of electronic resources, collection of usage information, well-designed reporting, and making current licensed holdings information available to patrons. An ideal ERMS module would also minimize the amount of work required to pass metadata between the ERMS, ILS, and OpenURL resolvers. > Exchanging acquisitions and other information with a stand-alone ERMS > should be quite possible, subject to building connectors for each > stand-alone ERMS (I'm guessing that no standards have emerged yet). Some work has started -- the DLF published a white paper about the issue at http://www.diglib.org/standards/ERMI_Interop_Report_20080108.pdf, and some vendors have started the CORE (Cost of Resource Exchange) initiative to set up a NISO working group to establish a standard for exchange of acquisitions data between an ILS and ERMS. As yet there is nothing concrete to code against. > Or would enabling easy integration of CUFTS2 > (http://cufts2.lib.sfu.ca:8033/trac/CUFTS/ - sharing Perl/PostgreSQL > sensibilities with Evergreen) satisfy the bulk of the requirements, > while leaving open the possibility for sites to use other standalone > ERMs? The last time I tried installing CUFTS2 was over a year ago, but > I think Todd has worked out a number of the little bugs since then. Sounds plausible in principle -- I haven't looked at CUFTS2 in any detail, but I see from the development blog that Todd has been working on ERM features. There's certainly a natural overlap in the basic knowledgebases required by an ERMS and an OpenURL resolver. Regards, Galen -- Galen Charlton Koha Application Developer LibLime [EMAIL PROTECTED] p: 1-888-564-2457 x709
