Peta Hopkins
My feedback
121 results found
-
44 votes
An error occurred while saving the comment -
42 votes
An error occurred while saving the comment No votes left, but it would be a nice feature
-
66 votes
An error occurred while saving the comment +1
-
8 votes
An error occurred while saving the comment This would be helpful for us. Due to constraints/challenges with course date from source systems, our course data is a mix of course loader and manual updates. Having a history would help us unpick the threads when troubleshooting.
-
64 votes
An error occurred while saving the comment +1
-
28 votes
-
148 votes
An error occurred while saving the comment No votes left. But this sounds reasonable. Perhaps non-RapidILL libraries might like to have it hidden though.
-
32 votes
An error occurred while saving the comment I have no votes left, but this would assist us with our historical reporting such as KPIs like... the proportion of courses that had published resource lists. We have to manually retain the count of courses in the past or avoid deleting old ones.
-
22 votes
-
24 votes
An error occurred while saving the comment Sounds like this could add some useful flexibility.
-
25 votes
An error occurred while saving the comment This sounds like a worthy idea to meet regional ontologies
-
9 votes
An error occurred while saving the comment Nice idea too. Keep the trail of the request handling all in the one system.
-
40 votes
-
275 votes
An error occurred while saving the comment If you like this, you might also be interested in flexibility for brief records based on format/resource type
-
18 votes
An error occurred while saving the comment Yes please.
-
15 votes
-
19 votes
-
34 votes
An error occurred while saving the comment I would support more flexibility for this letter.
-
37 votes
-
44 votes
An error occurred while saving the comment This would be helpful for us to monitor usage of various systems that are generating resource sharing requests. Right now I'm trying to understand how many requests might be coming via LibKey Nomad, but we also have other integrations which we could better report in if the source field was in analytics.
.png){kind=link}
.png){kind=link}
It would be good to know what proportion are opting out, and whether we should be consulting with a focus group on why, suggestions that would help them see only the crucial updates they want.
We tend to also send a once a term notification to the "daily digest" about resource lists. Next time I might put a reminder in there of how to opt back in again.