Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) s
Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) section of the release notes.
The reason for this need: Larger institutions have large numbers of Alma using staff to manage, oftentimes including student workers. It is important for Alma system administrators to have prompt awareness of changes to roles in order to make any necessary changes to staff accounts, profiles, etc. in order to maintain the security and integrity of patron data, cataloging data, norm rules, and the like.
Having changes of these nature given prominence in release notes, rather than buried within sections of a long set of release notes, will assist system administrators with maintaining appropriate access to Alma.
Curran Riley
shared this idea
-
Petra Bakera
commented
Of course, Exl is obliged to document new roles and it is not a new feature per se, but I think it would be good if this type of change were given its own chapter in the release notes.
As far as I know, roles are not changed so often that it would constantly clog up the release notes.
Incidentally, I would like to see a similar declaration in the release notes with regard to the letter configuration. -
Stacey van Groll
commented
While I completely agree with this need for documentation, I can't in good conscience give it any of my limited 25 votes, because it's not a new feature or improvement to existing functionality which is the purpose of this forum.
Ex Libris is responsible and expected to communicate and document their system and any system changes as a standard expectation of a system vendor.