Andrew Welch
My feedback
19 results found
-
266 votesAndrew Welch supported this idea ·
-
72 votesAndrew Welch supported this idea ·
-
13 votesAndrew Welch supported this idea ·
-
4 votesAndrew Welch supported this idea ·
An error occurred while saving the comment -
6 votesAndrew Welch shared this idea ·
-
12 votesAndrew Welch supported this idea ·
-
16 votesAndrew Welch supported this idea ·
-
22 votesAndrew Welch shared this idea ·
-
73 votesAndrew Welch supported this idea ·
-
19 votes
An error occurred while saving the comment Andrew Welch commentedWe would like to see Portfolio Access Type added to the 'Change electronic portfolio information' job, as well as to the Retrieve Portfolio and Update Electronic Portfolio APIs.
Andrew Welch supported this idea · -
19 votesAndrew Welch shared this idea ·
-
38 votesAndrew Welch supported this idea ·
-
2 votesAndrew Welch shared this idea ·
-
331 votesAndrew Welch supported this idea ·
-
54 votesAndrew Welch supported this idea ·
-
5 votesAndrew Welch shared this idea ·
-
28 votesAndrew Welch supported this idea ·
-
176 votesAndrew Welch supported this idea ·
-
59 votesAndrew Welch shared this idea ·
We too would like to increase the number of conditions in VE Custom Scopes. One way to accomplish this would be to add "is in" and "is not in" operators, which would allow us to create groups of locations under a single condition. Other areas of Alma configuration include these operators, so it's unclear why VE scopes only have "equals" and "not equals," which is extremely limiting.
For example, we're in a Fulfillment Network of 9 libraries, and fulfillment to partner libraries is based on Location. In order to configure Primo VE, each library is having to create dozens of custom scopes because of the 3 condition limit. Adding more flexible operators would allow us to create just one scope per partner.