Bodil Wik
My feedback
22 results found
-
241 votes
Hi all, we're working on analyzing the request for batch item description updates and would love your input to make sure our solution fits your needs.
I would like to propose the following:
The "Rebuild Physical item description" job currently allows auto-generating a description for a set of items (based on enum/chron data) - this option will be kept as is, but the job would allow selection to either auto-generate the description (existing) or enter a description value as free text (meaning all items in the set would get the same description). The free text option would also support updating the field with an empty value as exists in other jobs.
1. What are some examples of descriptions that would be relevant across an entire set of items?
2. As discussed in previous comments, changing the description of an item (manually or via job) causes the pending requests for that…
An error occurred while saving the comment Bodil Wik supported this idea ·
-
0 votes
Bodil Wik shared this idea ·
-
33 votes
An error occurred while saving the comment Bodil Wik commented
At Uppsala University Library we would be very interested in reports on how many letters of various types have been sent during a specified time. We would also like to see which user groups have received them.
Not exactly the same thing as above but very close.
Bodil Wik, Uppsala University LibraryBodil Wik supported this idea ·
-
3 votes
Bodil Wik shared this idea ·
-
19 votes
Bodil Wik supported this idea ·
-
Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation
664 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 Bodil Wik commented
Dear Yael,
Here comes an attachement in order to show the problems we have at Uppsala university.
Best regards
Bodil WikAn 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 vote
Bodil Wik shared this idea ·
-
6 votes
Bodil Wik shared this idea ·
-
3 votes
Bodil Wik shared this idea ·
-
9 votes
Bodil Wik shared this idea ·
-
119 votes
Bodil Wik supported this idea ·
-
132 votes
Bodil Wik supported this idea ·
-
177 votes
Bodil Wik supported this idea ·
-
56 votes
Bodil Wik supported this idea ·
-
69 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 ·
-
5 votes
Bodil Wik shared this idea ·
-
13 votes
Bodil Wik supported this idea ·
-
17 votes
Bodil Wik supported this idea ·
-
2 votes
Bodil Wik supported this idea ·
-
46 votes
Bodil Wik supported this idea ·
1. We register (among other things) copy id in the description field in order to make requests for a specific copy, possible (older material means unique copies).
We also use copy id in the description field for items on related records in order to keep them separate from items not related (the system did some strange things with requests here). It is possible to process all items with copy id 1 together, all with copy id 2 together and so on.
2. We always have an Analytics list to start from. In that list we have Process type as a column in order to see what items are requested. We also have a separate report for requests in more detail. But the fact that Analytics gets updated only once a day is a problem. We have to check and run things in the morning in order to be sure that we do not delete a request by mistake. This is one of the major disadvantages with Alma: not having direct access to the database (SQL!).
It is also possible to use Resource Request Monitoring, but there is no way of choosing location there so it is easy to miss requests.