Alasdair MacDonald
My feedback
3 results found
-
202 votes
We are considering adding a field to the course record in Alma, reportable in Analytics, for the faculty/school. It could be used for reporting purposes but not for discovery purposes. In other words, you would be able to pull list usage by faculty/school, but end users would not be able to browse by faculty/school. Would it still be helpful?
Alasdair MacDonald supported this idea · -
336 votesAlasdair MacDonald supported this idea ·
-
140 votesAlasdair MacDonald supported this idea ·
An error occurred while saving the comment
I have no votes left until some planned ideas reach fruition, so cannot add my support for this until I get some votes back.
To add though, I would support allowing individual cataloguers the option of defining their own default templates and also allowing Cataloguer Extended the option of editing and managing their own templates. it is a bit of a problem having one default for all.
Yesterday, we wanted to upload an Excel file to create basic records for a local electronic collection, which required a custom template. In order to get this to work, I had to make it the default template, meaning that all my team had this as their default while the job was being run.
If Cataloguer Extened people can delete things, surely the can be trusted with template creation?