Emelia Sutton
My feedback
14 results found
-
28 votes
An error occurred while saving the comment -
77 votes
An error occurred while saving the comment Emelia Sutton
commented
The fix found in "Found in Alma's Know Issues Fix Schedule" is related to messages not coming in at all. Not related to our desire to see the original ISO message.
I would be happy to view even the xml, anything would be better than nothing.
Emelia Sutton
supported this idea
·
-
24 votes
An error occurred while saving the comment Emelia Sutton
commented
I would like to see this in borrowing. If we put a note on a request that an item needs to be posted out unless someone goes into the notes when the book is received we will not see the note and the book will not get processed correctly.
-
37 votesEmelia Sutton
supported this idea
·
-
221 votes
We have added it to our plan. We will share more details as part of the design phase
An error occurred while saving the comment Emelia Sutton
commented
I don't use this at all because when using DDC trying to choose a shelf list number when they go from 1 to 10 to 100 is just plain confusing!
eg.
170 1
170 10
170 100
170 101
[next page...]
170 102 etcSo the ability to sort in proper numerical order like in Primo would be great. And it would reduce the amount of duplicate shelf list numbers we have to correct.
-
16 votes
An error occurred while saving the comment Emelia Sutton
commented
The history tab should show every change that takes place on the record.
Changed in metadata, changes in location pickup, when someone adds a note to the request. Most importantly we should know when the request arrived and what time someone started working on it.
Eg. Express requests need to be completed within 2 hours. Currently we cannot fulfil these requests because we do not know what time the request has arrived. If we can't prove it was (or wasn't) done within the 2 hour time frame, how can we charge for it?
The original ISO message contains the timestamp for when the request was sent, and we could source the time from there if we had to, but we don't have access to that.
Kind regards
EmeliaEmelia Sutton
supported this idea
·
-
54 votes
An error occurred while saving the comment Emelia Sutton
commented
Hi,
If I could give this 1000+ votes I would! We write notes to be able to see what changes have happened with a request, yet we cannot use the notes to see trends in actions.
Example, if we are getting a lot of requests for items we hold. We add notes to say we hold the item, but there is no way to pull those requests out and see if there are any common factors, to see how many there are or to identify repeat offenders.
Example, notes get added when we cancel a request. There is no way to analyse those requests and why we cancelled them. Was it something we couldn't fill? Was it something we hold? Was it something the patron asked us to cancel?
Having access to these notes would be very helpful!
Thanks,
EmeliaEmelia Sutton
supported this idea
·
-
20 votesEmelia Sutton
shared this idea
·
-
144 votes
An error occurred while saving the comment Emelia Sutton
commented
Would love to see this for updating barcodes
-
35 votesEmelia Sutton
supported this idea
·
-
55 votesEmelia Sutton
supported this idea
·
-
55 votesEmelia Sutton
supported this idea
·
-
508 votes
We are investigating the options for enhancing the job reports as part of a general enhancement to the jobs UX, which will then allow gradually deploying report enhancements to the different jobs in Alma.
Emelia Sutton
supported this idea
·
-
59 votesEmelia Sutton
supported this idea
·
I agree, its confusing! A different colour bar, or where it says Alma Sandbox, make it say Alma Configuration. If someone clicks on config instead of the new ME, they won't have clue where they are. Not to mention how difficult the little images and writing is to see... and my eyes aren't even bad. Some of our older staff are going to struggle.