Electronic portfolios in an electronic collection/packages should inherit data displays from the collection's service
Data elements that are set at a Electronic collection service level should cascade down and be applied/display at the electronic portfolio level.
While portfolios that are part of an electronic collection/package inherit the properties that are set at the service level, those inherited properties do not display in Alma in the individual portfolios. For example, the proxy value in the individual portfolios will always display in Alma as "No" even when the true value inherited from the electronic collection's service is "Yes." Similarly, a public or authentication note entered at the electronic collection or service level does not cascade down to the individual portfolio display in Alma either. Currently, the only service level information that appears in a portfolio is the Service Parse Params. Request: Data elements that are set at an electronic collection's service level (specifically, proxy settings and public/authentication notes) should cascade down to the portfolio level display. Staff shouldn't have to check two places to see the correct setting
As part of Alma June release Advanced search query options were expanded to include Not Contains Keywords, Is Empty and Is Not Empty for electronic resources indexes.
For more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes
-
Karen Abel commented
I would like to add to this that the proxy settings only seem to cascade from the service to the portfolios if the setting is 'enabled' and not if the setting is 'not enabled':
Service Editor proxy enabled + Portfolio Editor proxy enabled = proxy enabled, and
Service Editor proxy enabled + Portfolio Editor proxy NOT enabled = proxy enabled
but:
Service Editor proxy NOT enabled + Portfolio Editor proxy enabled = proxy remains enabled
It would be useful to have flexibility over whether the Service Editor or the Portfolio Editor carries the greater power. For example, if I want to switch the proxy off in one go for all portfolios in a collection, I would like to be able to choose in the Service Editor that these settings override the portfolio settings. For clarity, I would then like to be able to see in the Portfolio Editor that the setting has been cascaded from the Service Editor (and what it is) and would expect the option to amend this within the Portfolio Editor to be greyed out.
Conversely, if I want to have the opportunity to opt individual portfolios in and out of the proxy, I would want to choose that the Service Editor settings cannot be overridden. Again, for clarity, I would still expect to see what the Service Editor setting is when I’m inside the Portfolio Editor but the Portfolio Editor settings would not be greyed out. -
Diana Brooking commented
Some elements like License and POL do inherit. Other values like Proxy should do the same. Right now, we have to run a job to update the portfolio proxy so it will match the proxy setting in the collection, just so as to not confuse staff and help with troubleshooting. The fact that the Alma documentation has a complex table to help you understand all the permutations of the proxy settings at each level is in fact a bad sign.
-
Naomi commented
You are right, It's very confusing. Please send your suggestion in Alma list, so more customers will vote for it.
Naomi