Pauline Wheeler
My feedback
13 results found
-
22 votesPauline Wheeler
supported this idea
·
-
36 votesPauline Wheeler
supported this idea
·
-
5 votesPauline Wheeler
shared this idea
·
-
68 votesPauline Wheeler
supported this idea
·
An error occurred while saving the comment -
16 votesPauline Wheeler
supported this idea
·
An error occurred while saving the comment Pauline Wheeler
commented
We fully support this idea of adding a notes field at review/list level, which could be used to record key information to support our acquisitions workflows. The notes field could be displayed along with other list level information within each review, so that it is visible when reviewing each item.
Our purchasing is governed by set rules/ratios and budget codes, which are applied to lists based on student numbers, faculty, etc. Currently these cannot be recorded within reviews and have to be recorded against each reading list review outside of Aspire and cross-checked before orders are created. A notes field would allow us to record the purchasing rule and budget that applies when a review is received. Acquisition staff could then easily see this information as they review items without having to consult external information.
Purchasing is a key outcome of list reviews and incorporating information to support that process would be helpful to our workflows and improve efficiency.
Other universities may have other uses for such a field. By creating a general note field this provides flexibility to record and communicate other key information between review stages.
Posted on behalf of staff at: University of Nottingham
-
14 votesPauline Wheeler
shared this idea
·
-
21 votesPauline Wheeler
supported this idea
·
-
21 votes
We are looking to explore this further and make changes to the way the hierarchy is used within Talis Aspire.
An error occurred while saving the comment Pauline Wheeler
commented
At the University of Nottingham we have recently started updating the hierarchy on a regular basis with student numbers from our student records system. We would like these to be reflected in the reading list student numbers to help with acquisitions processes in reviews. So, this idea would allow us to made the most of our hierarchy updates and help improve library work flows. Is there any update on when this might be implemented?
Pauline Wheeler
supported this idea
·
-
61 votes
We are considering this for the next round of work we will do on the Reviews area of Talis Aspire and will feedback to our UX and Development Teams,
An error occurred while saving the comment Pauline Wheeler
commented
This has been identified in a recent process review carried out in conjunction with Talis for the University of Nottingham. We wondered if there was any update on whether this might go ahead and when the next round of work for the Reviews area is likely to be.
Please see Jenny Hill’s comment below on the value this would add to our current workflows.
Pauline Wheeler
supported this idea
·
-
24 votesPauline Wheeler
supported this idea
·
An error occurred while saving the comment Pauline Wheeler
commented
We have had some feedback from academics that this can be an issue where students are clicking it thinking they can get full text access as it is close to the online resource link. It would be great to be able to turn this off at list level for those list publishers that would like to do this rather than having to switch it off at tenancy level.
-
13 votes
An error occurred while saving the comment Pauline Wheeler
commented
When updating the hierarchy with student numbers for the next academic year it would be useful to be able to see changes made and be able to download student numbers at hierarchy level in the report.
Pauline Wheeler
supported this idea
·
-
63 votes
We have begun work on the anonymising of user profiles. If you have anyone that raises this under GDPR before this work is released then please do raise a support ticket with the details.
Pauline Wheeler
supported this idea
·
An error occurred while saving the comment Pauline Wheeler
commented
We would also like the ability to delete user profiles (preferably in bulk) to comply with our data policies and GDPR.
-
72 votes
Please do continue to vote and add your use case to this idea. As votes and comments are added we are able to use these to review and build a case for the idea.
Pauline Wheeler
supported this idea
·
We fully support this idea of adding a notes field at review/list level, which could be used to record key information to support our acquisitions workflows. The notes field could be displayed along with other list level information within each review, so that it is visible when reviewing each item.
At the University of Nottingham our purchasing is governed by set rules/ratios and budget codes, which are applied to lists based on student numbers, faculty, etc. Currently these cannot be recorded within reviews and have to be recorded against each reading list review outside of Aspire and cross-checked before orders are created. A notes field would allow us to record the purchasing rule and budget that applies when a review is received. Acquisition staff could then easily see this information as they review items without having to consult external information.
Purchasing is a key outcome of list reviews and incorporating information to support that process would be helpful to our workflows and improve efficiency.
Other universities may have other uses for such a field. By creating a general note field this provides flexibility to record and communicate other key information between review stages.