Daniel Sandbecker
My feedback
9 results found
-
94 votes
An error occurred while saving the comment Daniel Sandbecker
supported this idea
·
-
19 votesDaniel Sandbecker
supported this idea
·
-
24 votesDaniel Sandbecker
shared this idea
·
-
2 votesDaniel Sandbecker
shared this idea
·
-
68 votes
An error occurred while saving the comment Daniel Sandbecker
commented
This is still troublesome.
Currently our Primo Instance allows anyone to anonymously send a reference to anyone else, and a logged in user to anonymously send a reference and a message to anyone else.
To prevent abuse both of the following steps need to be taken by Ex Libris:
1. Trigger a login if a user that is not logged in clicks the share by E-mail button.
2. Use the logged in users e-mail address in the From field of the sent e-mail. -
14 votesDaniel Sandbecker
shared this idea
·
-
1 voteDaniel Sandbecker
shared this idea
·
-
4 votesDaniel Sandbecker
shared this idea
·
-
28 votesDaniel Sandbecker
shared this idea
·
Some fields are not just marked as not supported, but intentionally misused.
There is a specific idea registered for supporting "unavailable holds count" and "unavailable hold items fields": https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44459898-alma-to-support-sip2-response
Alma does not support this field, but furthermore also specifies in the documentation for the supported "holdItemsCount" that unavailable hold requests are counted there instead. The items summary also includes data for the unsupported "unavailableHoldsItems" field in the "holdItems" field. This causes real issues when self check machines that actually supports the standard trusts the Alma SIP2 implementation.