Add bulk action tools into Aspire itself
The bulk action tools produced by Joe Munzer at York St John University under the aegis of Talis Developer Network have been absolutely invaluable during the last year - thanks Joe! However, my colleagues and I have had some difficulties getting the tool set up on our work computers because they are Managed Desktop machines and not really intended to run applications like Docker and XAMPP, which are needed to use Joe's bulk tools. Ideally, we would like to see the functionality of bulk tools could be incorporated into Aspire 'Admin' menu or even added as a separate 'Actions' menu to prevent them becoming too long. This would make it possible for staff who don't have admin rights to their work computer - which I anticipate is a majority of HE librarians - to bulk-add items to lists, replace URLs, and all the other great features that we've come to rely on. Anecdotally, I know that quite a few people are having to use their personal machines to make changes to institutional reading lists, which isn't really OK.
Would anyone else like this to happen as well? Please vote generously if so!
Tom Kistell
shared this idea
-
Calvin Calvin commented
I would expect that the overall amount of modifications made via the API routes over the course of the previous year would be enough to make a strong argument for incorporating some of these services into the primary product.
----------
https://geometry-dash.io -
Tracey Middleton
commented
Yes.
-
Stuart Sharp
commented
Yes, I mentioned this at the May Insights. It has become a key function for us in the last year, especially as we moved historic URLs from http to https and the Dawson to Askews changes.
-
Richard Hughes
commented
Completely agree. Would love to see it added to the core product. I had to jump through various hoops to get XAMPP on my work computer and although the tool is great, it's not clear who we can get support from when updates don't take place exactly as intended.
-
Joseph Munzer
commented
Yes!
I imagine that the total number of changes made via the API routes over the last year would be a strong case for pushing some of these functions into the core product!
-
Kevin O'Donovan
commented
100% agree - the process should be replaced with a simple upload of a CSV file to Talis Aspire, with the same conditional formatting that Joe has explained in his tool. In the same way that we upload data to do a hierarchy update.
That is all that should really be necessary for customers to do. Would love to see this happen!