New role for Manage Import Profiles
Currently users must have a Cat Admin role or Gen Sys Admin role to be able to Manage Import Profiles (change/add profiles). This also gives them access to the Configuration area of Alma. There should be a role to permit users to Manage Import Profiles that does NOT also give them access to the Alma configuration area. Access to the Alma configuration menu should be separate from the ability to Manage Import Profiles.
Corinna Baksik
shared this idea
Hello all,
I’m currently working on a detailed solution for this request and would appreciate your input. Could you share the reasoning behind the need for a completely new user role to manage import profiles?
An alternative approach could be to introduce specific privileges for managing import profiles and add them to the existing Purchasing Manager and Catalog Manager roles, with these privileges turned off by default. This way, institutions can decide whether to enable them for these roles.
The advantage of this approach is that it leverages existing manager roles without requiring the creation of an additional new role, while still avoiding granting full administrative access to configuration settings.
Looking forward to your feedback.
Erez
-
Kimberley Ferriere
commented
At our institution, Administrator access is unnecessary for this role since configuration is handled by different staff. The Catalog Manager role could be sufficient.
-
Anonymous
commented
The manage import profiles privilege can live within another role. As far as I know for cataloging, Catalog Manager should be OK for that. Not sure if Cataloger Extended would be sufficient?? Totally not sure where it should live for acquisitions. The basic idea is that managing import profiles should not give access to configuration.
-
Mike Rogers
commented
Hello Erez - from my institution's perspective, the Cataloging staff who follow up and check the status of record loads are different than the staff who configure and manage the import profiles themselves. Catalogers typically need access to the "History" area, where they can check load errors, view records that were added or not added due to merge issues, etc. We do not want them to have full administrative access since it is a different job responsibility that manages that aspect of import profiles. I agree with Jamen, that it does not need to be a completely separate role but could be added to the Catalog Manager role, for instance.
-
Jamen McGranahan
commented
Erez - I do not believe it is necessary to create a whole new role for import profile management, but it should not require an Admin role. That really is the issue. Several comments have suggested adding it to one of the Manager roles so I think that would be sufficient.
-
Ann Kucera - Central Michigan University
commented
I would like to see this developed. Thanks!
-
Peter Joseph
commented
I thank the author for creating the post; it was really useful to me and I enjoyed it. I made a note about it on the https://bit.ly/3B7imEG. I'd appreciate it if you could read it and accept it. Thank you for taking the time to express your issue.
-
Jamen McGranahan
commented
as the others have commented, this ability to manage Import Profiles should not be limited to an Administrative role. It would make sense for something like Catalog Manager or Repository Manager be able to manage their own Import Profiles.
-
Manu Schwendener commented
6662 in NERS, now open for voting.
-
James Hammons
commented
Why not just add the privilege to the Catalog Manager role?
-
Mike Rogers
commented
As others have mentioned, most of our staff who work with Import Profiles are in the Cataloging Unit and should not have access to configuration. Having a separate role for Import Profiles would solve the problem of simply telling them, "don't touch anything else!"
-
AN - UNSW
commented
Those who manage the importing are not those who need administration access.
-
Peta Hopkins commented
I would also suggest that the role for permitting users to manage import profiles could also allow them to use the FRBR/Dedup utility - another cataloguing-related function.
-
Bill Constantine commented
I agree. The resources staff need to be able to quickly set up and take down import profiles as we get many types of files coming in from different vendors and they sometimes need slightly different profiles. Yes, import profiles are a very powerful tool and they need to be managed carefully. However resources staff have access to other equally powerful tools eg Normalization Rules and I am sure that each library has worked out how to work with them and which staff have access to them and which ones do not. We should not have to get systems admin staff to have to set up import profiles for profiles we may only use a couple of times for particular files. Systems admin staff should be configuring more long term parameters, eg opening hours, terms of use, etc, etc.