Collection level access model setting
Please create a setting where we can choose the ebook access model at the collection level. We have many ebook collections where we know everything in them is the same access model, usually unlimited (UA). It would be helpful to be able to set this at the collection level so every portfolio in that collection will have the access model display in Primo.
Elizabeth York commented
I support this as a much-needed feature. The Public Access Model field in Alma is configurable at the portfolio level. This field shows the number of simultaneous users who may access a book, and it can be displayed to users in Primo. It is automatically populated with values from GOBI, OASIS, and RIALTO. This field works well for cases where we buy individual ebooks with varying purchase models. However, because there is no viable way to enter a Public Access Model at the collection level, our individual ebook purchases through GOBI, OASIS, and RIALTO display a Public Access Model in Primo, while ebooks we purchase as collections do not. This produces an inconsistent user experience.
“Public Access Model” should also have the option to be configurable at the collection/service level (I think either would work), and if a “Public Access Model” is entered at the collection/service level, it should be inherited by all portfolios in the collection. This is needed because, in many cases, we buy or subscribe to an entire ebook collection, and all its books will have the same access model. We want to be able to enter a “Public Access Model” for the entire collection and have it be inherited and display for all portfolios in the collection.