How to handle pricing information for packages (Wiley Database Model)?

[Thumy Webb]

Hi folks,

I'm setting up Wiley scenarios and am not sure how to handle packages like Wiley's Database Model, which provides access to a set list of titles for a single price. I was hoping that putting a Big Deal Cost would be sufficient, but it looks like I also have to supply a pricelist, which is not available because it's a package deal.

How are other Unsub users handling this situation? 

Thanks,

--Thumy Webb

Electronic Resources Librarian

Fondren Library | Rice University | Houston, TX

[Ricky Patterson]

Hi Thumy,

As you can see, Unsub isn't really designed to handle packages in that way but in the past what I have done for other bundles of titles was to split the cost of the bundle across the individual titles. If I had list prices from some source for the individual titles, I would sum those up, and then compare that with the bundled price, and just scale all of the individual title prices down by that factor to get a new list price.

But to be honest, I've usually done this outside of Unsub.  Alternatively, I've just used Unsub to get the OA information, etc. for these titles (you can insert list prices, or just make up prices, since you won't be using the Unsub CPU for this) and then do a manual analysis, using the same formulae that Unsub would use, to get some effective CPU numbers for each title, etc.

But interested in other suggestions.

Best,

Ricky Patterson

Director, Research Data Services & Social, Natural, and Engineering Sciences
University of Virginia Library

[Alice Fairfield]

Our Springer package was like that. We got current individual list prices from Springer and used those, since we wouldn't benefit from our years of package price reduced costs once we broke the package and went to individual subscriptions.

Alice Fairfield

Serials Librarian

University of Connecticut