oh man, we spend so much money on hosting fees! i need to start thinking about how we’re going to nip this problem in the bud. we are charged a hosting fee when we purchase an electronic resource; the provider usually charges us an annual fee for upkeep of that resource on their platform. in this way a purchase isn’t just a purchase, it’s an initial outlay of cash with additional payments every year, in perpetuity. i don’t see how we are going to be able to sustain this model.
i bumped into this screen shot on our shared network drive, of how we used to have to ask our system to give us a report of all the order records that had some kind of hosting fee. we weren’t consistent in our note-making of how we identified these fees. sometimes we called them ‘hosting fees,’ sometimes we called them ‘access fees,’ etc. we resolved this problem by creating a new fund code, ‘hose,’ and all of our hosting fees for e-content are now paid on order records using that code. no more notes, and a one-line report request: show me all the active order records with ‘hose’ as the fund. this new fund makes report-pulling very easy.
(good grief)
