Jennifer, You could definitely create a report to accomplish this. However, I know many of our libraries would like some of this information to be exposed as part of the interface in some way so you don't have to create a separate report and run a report from a template. There are other areas for tracking and monitoring where money is spent that would be nice to have an interface that did not involve running a report template. However, I think as Rogan and others suggest, it would be good to sit down with end users and come up with a specification and fund development for improvements. There is no need to mimic any other ILS but identify the best possible workflow and develop according to that.
Tim On Fri, Jul 12, 2013 at 12:27 PM, Jennifer Pringle (Project Sitka) < [email protected]> wrote: > > Hi Robert, > > When you print your invoice in Evergreen at the bottom of the invoice it > lists each fund that is used with the total spent on the invoice for the > fund. Is this what you are looking for? > > As well, I suspect you can create a report in the reports interface where > you list the totals spent for each fund for a specific invoice. (I haven't > put together such a report myself.) > > Jennifer > -- > Jennifer Pringle > Sitka Support > Email:jpringle@sitka.**bclibraries.ca<email%[email protected]> > > > > > Quoting Grace Dunbar <[email protected]>: > > That's a pretty big leap to say the comment was an intent to derail the >> request for information. I think Lebbeous was simply trying to discourage >> sharing screenshots of proprietary software. If this can't be done in >> Evergreen today and someone were to develop it based on the screenshot >> provided, it could potentially lead to problems. >> We all just want to err on the side of caution when it comes to these >> matters. >> -Grace >> >> >> On Fri, Jul 12, 2013 at 11:54 AM, Jim Taylor <[email protected]> wrote: >> >> I think the question was simply what it was...is there a way to create a >>> >>> similar summary? I don't believe it was a plea for someone to turn >>> Evergreen into Symphony. Would seem like useful information no matter >>> what ILS one was using and, while also not being a lawyer, it would seem >>> difficult for someone to argue that only they are allowed to produce a >>> report which tells someone how much and from which budget lines they are >>> spending their money.**** >>> >>> ** ** >>> >>> >>> Guess I'm sticking my nose into someone else's discussion but seemed like >>> an unfair accusation against Mr. Meeks and one likely to derail his >>> request >>> for information.**** >>> >>> ** ** >>> >>> Jim**** >>> >>> ** ** >>> >>> *From:* >>> open-ils-general-bounces@list.**georgialibraries.org<[email protected]>[mailto: >>> open-ils-general-bounces@list.**georgialibraries.org<[email protected]>] >>> *On Behalf Of *Lebbeous >>> Fogle-Weekley >>> *Sent:* Friday, July 12, 2013 10:01 AM >>> *To:* Evergreen Discussion Group >>> *Subject:* Re: [OPEN-ILS-GENERAL] ***SPAM*** fund summaries from >>> invoices* >>> *** >>> >>> ** ** >>> >>> Hi Robert,**** >>> >>> ** ** >>> >>> >>> I am not a lawyer, but I do have a vague idea that Evergreen development >>> can't just mimic proprietary ILSes without running into potential legal >>> trouble. Nobody here is trying to produce a clone of Symphony or >>> anything >>> else; even setting aside legal concerns, that's just not a goal of the >>> Evergreen project.**** >>> >>> ** ** >>> >>> >>> That said, if you would be open to discussing your workflows and needs in >>> a somewhat more abstract form, I do hope you find that the mailing list >>> and >>> the IRC channel[1] will help lead you down any of these paths:**** >>> >>> ** ** >>> >>> >>> - Finding alternative workflows that libraries already using Evergreen >>> can >>> recommend to accomplish your essential goals**** >>> >>> - Finding volunteer effort to develop new features**** >>> >>> >>> - Finding vendors who can develop the features you want for Evergreen, >>> ideally blending your requirements harmoniously with those of libraries >>> in >>> a similar position**** >>> >>> ** ** >>> >>> Thanks,**** >>> >>> ** ** >>> >>> Lebbeous**** >>> >>> ** ** >>> >>> [1] See >>> http://www.open-ils.org/irc.**php****<http://www.open-ils.org/irc.php****> >>> >>> ** ** >>> >>> >>> On Fri, Jul 12, 2013 at 10:25 AM, Robert Meeks < >>> robert.meeks@asburyseminary.**edu <[email protected]>> >>> wrote:**** >>> >>> >>> Hi all - another question as I continue to nail down my acquisitions >>> workflows.**** >>> >>> ** ** >>> >>> >>> When I finish with an invoice and successfully pay everything in >>> Evergreen, I need to be able to create some kind of summary that displays >>> how much money is coming out of which funds in an invoice. This is >>> crucial >>> to our payment process, as I send copies of the invoice to be paid and >>> this >>> summary to my business office, who then cuts the check to our vendors. >>> The >>> attached screenshot is the summary I used to be able to get from Symphony >>> when I paid an invoice. Is it possible to create such a summary after >>> finishing with an invoice in Evergreen?**** >>> >>> ** ** >>> >>> **** >>> >>> * >>> Robert Meeks***** >>> >>> *Acquisitions Specialist - BL Fisher Library***** >>> >>> Asbury Theological Seminary**** >>> >>> 204 N. Lexington Ave.**** >>> >>> Wilmore, KY 40390**** >>> >>> p: 859.858.2397**** >>> >>> ** ** >>> >>> ** ** >>> >>> ** ** >>> >>> >>> >>> **** >>> >>> ** ** >>> >>> -- **** >>> >>> Lebbeous Fogle-Weekley**** >>> >>> | Software Developer**** >>> >>> | Equinox Software, Inc. / The Open Source Experts**** >>> >>> | phone: 1-877-OPEN-ILS (673-6457)**** >>> >>> | email: [email protected]**** >>> >>> | web: http://www.esilibrary.com**** >>> >>> >> >> >> -- >> Grace Dunbar, Vice President >> Equinox Software, Inc. - The Open Source Experts >> [email protected] >> 1-877-OPEN-ILS www.esilibrary.com >> >> > > > -- > Jennifer Pringle > Sitka Support > Email:jpringle@sitka.**bclibraries.ca<email%[email protected]> > > -- Tim Spindler [email protected] *P** Go Green - **Save a tree! Please don't print this e-mail unless it's really necessary.*
