Allen Jones
My feedback
21 results found
-
100 votes
Allen Jones supported this idea ·
-
70 votes
Allen Jones supported this idea ·
An error occurred while saving the comment -
1 vote
Allen Jones shared this idea ·
-
292 votes
An error occurred while saving the comment Allen Jones commented
great this will be implemented going forward (as Im looking for my cert renewal email now)
An error occurred while saving the comment Allen Jones commented
+1, this would also be great if it were view-aware so that we might have different subdomains for different views (alumni.library.newschool.edu vs. search.library.newschool.edu). This is just me being greedy, though.
Allen Jones supported this idea ·
-
3 votes
Allen Jones shared this idea ·
-
11 votes
An error occurred while saving the comment Allen Jones commented
Laura, we are having this issue now and it's crushing. We have staff who are clearing the same item 2-3 times because a faculty member indiscriminately cloned their reading list. it would be helpful to have a system setting to prevent this from happening since it's creating a lot of work, particularly for streaming videos.
Best case scenario -> instructors are prevented from creating a second reading list if one already exists. There should be a link to mange all of their lists so they can delete the errant reading list.
Allen Jones supported this idea ·
-
3 votes
Allen Jones shared this idea ·
-
9 votes
An error occurred while saving the comment Allen Jones commented
I would also like to echo that adding a logical set could significantly increase the power of the tool.
I would also advocate for a citation loader column of operation similar to the course loader to allow overlay of citation fields in batch.
Allen Jones supported this idea ·
-
3 votes
Allen Jones shared this idea ·
-
9 votes
Allen Jones shared this idea ·
-
91 votes
An error occurred while saving the comment Allen Jones commented
This would be exceedingly helpful for those of us that have central acquisition departments and multiple libraries where patrons might pick up requests.
Allen Jones supported this idea ·
-
1 vote
Allen Jones shared this idea ·
-
2 votes
Allen Jones shared this idea ·
-
196 votes
Allen Jones supported this idea ·
-
72 votes
Allen Jones supported this idea ·
-
101 votes
An error occurred while saving the comment Allen Jones commented
Laura,
I saw this and had questions. Can you say more about "control location"? Do you mean you want to be able to set the order of the send locations area in the full-display in the middle column or do you wish it to also be able to live where the bx-recommendations live?
-
93 votes
Allen Jones supported this idea ·
-
204 votes
Allen Jones supported this idea ·
-
100 votes
Allen Jones supported this idea ·
-
193 votes
An error occurred while saving the comment Allen Jones commented
there is some confusion about this feature request as well - there are instructions on how to configure SMS for the Primo system using clickatell (our university has an account with this SMS provider), but unfortunately, the action is not available in the new UI.
This request seems to have gotten stale. This is a strongly needed API endpoint for borrowing requests to write integrations against systems from other vendors, particularly in Library Open Workflows.
Basically, we need the following:
1) be able to query requests in a particular state and for a particular partner within a specific IZ
2) be able to create/cancel/update requests (such as adding a remote record identifier to the request, add a label, or move to another status)
3) be able to 'send' the request to the partner from Alma upon save.
it would be great if we might be able to send a request such as :
GET /almaws/v1/resource-sharing-requests?status=CREATED_BORROWING_REQUEST&&partner=PARTNER_CODE&limit=100
There are create and delete/cancel actions for resource-sharing requests, but not update functions (https://developers.exlibrisgroup.com/alma/apis/users/#Requests)
A script would perform remote record ID lookups automatically before sending to a specific network/partner using their local 001 identifiers to improve fill rates. Once the request was updated, a parameter in the GET request would be included to submit the request to the partner (submit_to_partner=true) and advance the request to "request sent to partner".
Ideally, we should be able to run a separate script to see if a particular RS transaction (based on the external identifier) submitted to a partner has gone 'end of rota', then update the alma resource sharing request by changing the status to "REJECTED_BY_PARTNER".