Bodil Wik
My feedback
26 results found
-
Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation
656 votesHi all,
We are currently reviewing this idea together with Alma.
We will update with any new information we have.
Best regards,
Yael.
An error occurred while saving the comment An error occurred while saving the comment Bodil Wik
commented
Uppsala university also strongly supports this request. When relations for 830 $x generates related items in Primo, it gets very difficult for users to request the right material. There is no way to stop another item from the same series to be requested instead of the item bound with the item the user wants.
Bodil Wik
supported this idea
·
-
1 voteBodil Wik
shared this idea
·
-
6 votesBodil Wik
shared this idea
·
-
3 votesBodil Wik
shared this idea
·
-
188 votes
An error occurred while saving the comment Bodil Wik
commented
Clarification: At Uppsala University we do not want the letter triggered when a due date is changed, but we do want to schedule the letter to be sent at intervals for all users. As it is now, we have to plan ahead when to send the Borrowing Activity Letter and only activate it when the job is running or we will get these extra letters sent when due dates are changed (the users do not understand why they receive the letter and contacts the library). We would like to be able to just activate the letter and letting it run by itself like other letters and we are also troubled by the ‘fail’ message for staff.
An error occurred while saving the comment Bodil Wik
commented
At Uppsala university we want to send the letter, but not triggered by renewals or changing due dates in Alma.
-
7 votesBodil Wik
supported this idea
·
An error occurred while saving the comment Bodil Wik
commented
I agree. It is often important for our users that they find the exact right print material, the merging of these records makes the choice for our users impossible when records are hidden behind other records.
But at the same time it is very valuable when, for example, a print journal merges with an e one.
The ideal for us at Uppsala university would be if there was an option for making records for local print material not to merge with each other. But at the same time keeping the possibility of them merging with e material.
-
6 votesBodil Wik
shared this idea
·
-
167 votes
Hi all,
This is planned to be handled in the Primo Next Discovery Experience User Interface.
More details on the new interface planning can be found here -
Best regards,
Yael.
Bodil Wik
supported this idea
·
-
7 votesBodil Wik
supported this idea
·
-
49 votesBodil Wik
supported this idea
·
-
121 votesBodil Wik
supported this idea
·
-
128 votesBodil Wik
supported this idea
·
-
172 votesBodil Wik
supported this idea
·
-
19 votesBodil Wik
supported this idea
·
-
235 votesBodil Wik
supported this idea
·
-
54 votesBodil Wik
supported this idea
·
-
66 votes
An error occurred while saving the comment Bodil Wik
commented
I just voted for this. At Uppsala university we would very much like to have statistics for this and it is just not possible. If we use for example loan date and filter out a date period for that: then we will not count the automatic renewals for the loans where the automatic renewals are made at a later date. We need to be able to count the automatic renewals by dates directly connected to automatic renewals.
Bodil Wik
supported this idea
·
-
180 votes
Hi,
The login for an account that is managed in an external IdP (such as a Shibboleth IdP), is done by the IdP and not by Alma. Alma does not control the success of this type of login.
Alma does control the login status if the user record is internal, i.e. its password is managed in Alma. In that case, we will indeed allow the login to succeed even if the user is expired.
The user record status will be verified when calculating:
- GetIt services (hold/digitization/resource sharing)
- My Account renew loan option
In either case, the account will be considered active only if:
- The user record status is active
- The user record expiry date is not in the past
- The user’s patron role is active
- The user’s patron role’s expiry date is not in the past
The login, however, will not be affected by these conditions.
Thank you,
MosheAn error occurred while saving the comment Bodil Wik
commented
More details from Uppsala university:
We are not able to use a Student Information System in order to register users in Alma. We use the API. Then the Alma user expiration date will not be synchronized with any local expiration date.
When our users logs in using the university SAML authentication, the university server logs the user in, but in Primo the user is not logged in and the user will not receive any message explaining why. After the log in the user is just left in Alma without a clue to what just happened. The user is not logged in and thinks something went wrong and tries again but the same thing happens. The user is not given the possibility to understand what is happening.
When a user (not affiliated to our university) logs in with the Alma authentication, the user will not be logged in, but there is a message that we have changed now so that it reads: “Invalid number and/or password. Or it is time to renew your account.” So at least these users have some chance of understanding what is happening.We would prefer that the user gets logged in and is able to see his/her loans and fines and fees but that there is a clear message displayed about the expiration date and the user will not be able to make requests or renew loans.
This idea is planned. When?
Best regards
Bodil WikAn error occurred while saving the comment Bodil Wik
commented
This is something Uppsala University is looking forward to as well.
-
5 votesBodil Wik
shared this idea
·
-
13 votesBodil Wik
supported this idea
·
Dear Yael,
Here comes an attachement in order to show the problems we have at Uppsala university.
Best regards
Bodil Wik