Chris Jones
My feedback
58 results found
-
3 votes
An error occurred while saving the comment -
7 votesChris Jones
shared this idea
·
-
2 votesChris Jones
supported this idea
·
An error occurred while saving the comment Chris Jones
commented
Hi, This issue still remains, even after the Feb 2023 release when List ID was added to the Persistent Search indexing in Alma for Reading lists
An error occurred while saving the comment Chris Jones
commented
Completely agree with this, such a frustrating limitation and sets created from Analytics reports have not always created the right number of lists.
Documentation on this could also be improved significantly:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/070Managing_Jobs/060Managing_Search_Queries_and_Sets -
4 votesChris Jones
shared this idea
·
-
8 votesChris Jones
shared this idea
·
-
197 votes
An error occurred while saving the comment Chris Jones
commented
An update here would be useful (also admin may need to review/remove some spammy comments from last year)
-
92 votes
An error occurred while saving the comment Chris Jones
commented
Is this a function specific to the front-end, or intended for Students/Instructors/Library staff? Was wondering whether the Reading List Bulk Update Job in Alma with the Export to PDF could also serve as a basis to bulk export, although makes more sense front end with multiple selections from Find lists/My Lists etc
-
5 votes
An error occurred while saving the comment Chris Jones
commented
It is now possible to configure the display fields of Citations (in Edit Citations page) to show each of these fields, via the Cog/customisation checkboxes and moveable fields. They should be exportable as columns at that point.
-
4 votes
An error occurred while saving the comment Chris Jones
commented
Delivered in Sept 2020, referencing 2020 NERS #6870 https://knowledge.exlibrisgroup.com/Leganto/Release_Notes/2020/Leganto_2020_Release_Notes?mon=202009BASE
-
2 votesChris Jones
shared this idea
·
-
2 votes
An error occurred while saving the comment Chris Jones
commented
I thought there was a "detach from repository" option in the Reading List Citation Update Task job? Have you been ale to try that? Admittedly having reports in place to point to the metadata deletions would be necessary I suppose.
-
1 vote
An error occurred while saving the comment Chris Jones
commented
basically same idea originally raised in 2016 https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/15057603-loan-transfers-between-patron-accounts
Chris Jones
shared this idea
·
-
20 votes
An error occurred while saving the comment Chris Jones
commented
Is there any developer scope for a Cloud app which might assist with this at all?
An error occurred while saving the comment Chris Jones
commented
Hi, this Idea describes a problem common to many institutions. Even if it is not a frequent event, when it does occur it is highly inconvenient to library staff and can frustrate the provision of efficient customer service to patrons. The manual re-issuing from one account to another (especially if over 20 loans/a single page etc) provides opportunities for errors to creep in, so it would be a very beneficial addition to the Fulfillment options to staff in the Manage Patron Services view. This is something we would hoped to have seen by now.
-
3 votesChris Jones
supported this idea
·
Chris Jones
shared this idea
·
-
2 votesChris Jones
shared this idea
·
-
23 votes
An error occurred while saving the comment Chris Jones
commented
By way of further explanation, case 05327094 explains "When a request is canceled, it moves from one Oracle table (active requests) to another (Requests history). In any Oracle table, the creator is the one that 'created' the entry in this table, so when a request is moved to the request history table, the creator is not the user that created the request but the one that moved the request to the history table".
This is extremely unsatisfactory as it rewrites the history of the request in terms.
Completely support this idea. Lack of documentation around this (and after extensive work on Requests analytics when released in 2014) is not great.Chris Jones
supported this idea
·
-
77 votesChris Jones
supported this idea
·
An error occurred while saving the comment Chris Jones
commented
An error occurred while saving the comment Chris Jones
commented
This is still an issue. It would be nice to be able to set some mandatory fields in the customization rather than having to set mandatory only at Book or Article level. We lose much time and cancel requests which lack basic information which would not be submitted in the first place is the custmization allowed making the form mandatory (admittedly this may need some qualification for Books versus Journal.
-
17 votesChris Jones
supported this idea
·
An error occurred while saving the comment -
97 votes
An error occurred while saving the comment Chris Jones
commented
Anything to reduce the number of clicks here will help.
-
24 votes
An error occurred while saving the comment Chris Jones
commented
Agree, this is a real frustration for bulk handling of citations. Together with few fields in citation search/advanced search it makes management of lists and list items over time harder than it should be.
It would be useful to understand more about how the LTI tool was registered in this instance, and what user/course ids are passed to work with. IF not supported by Field Normalization or custom ids in the LTI, would it perhaps need a reverse look up by user id of the courses they are associated with? If no course in Alma unsure how would work.