[
http://jira.dspace.org/jira/browse/DS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11436#action_11436
]
Tim Donohue commented on DS-524:
--------------------------------
Andrea,
I still don't understand why we shouldn't allow DSpace System Administrators to
have editing capabilities on the NetID in all cases. Full system
administrators should "know what they are doing", and should be allowed to edit
this field when necessary (and not be forced to ask someone to go into the
database to modify it via SQL queries). More and more we are making small
steps towards offering more Administrative activities in the UI, and I see this
as an Administrative activity.
(Sidenote: Eventually, someday, I feel we should move the majority of all
configurations to the Admin UI -- so that there's no need to stop/start
Tomcat/DSpace every time you need to modify dspace.cfg. However, in order to
achieve this, we need to *trust* that the System Administrator knows what
he/she is doing -- they should be allowed to make any change in the system.)
I'd agree that normal users (submitters) and Community or Collection
Administrators should *not* be allowed to edit the NetID -- this will ensure
that it doesn't get accidentally modified by someone who doesn't understand the
implications.
What I would recommend would still be to do the following:
* Modify JSPUI/XMLUI to always display NetID in the Admin UI -- however it
should be readonly for everyone *except* a DSpace System Admin. We should
trust that System Admins know what they are doing, and they should be allowed
to change the NetID when absolutely necessary. If need be, we could provide a
warning message next to the NetID field to let them know what its purpose is.
* I realize that LDAP uses the NetID heavily -- but, I still think there is a
need for a System Administrator to be able to edit the NetID when necessary
(e.g. NetIDs can change -- it's rare, but sometimes a person will switch NetIDs
after getting married.)
Andrea, please let me know if I'm still misunderstanding the problem. Would
this solution not be acceptable at your institution? Am I misunderstanding
the problem that has occurred at your institution?
Does anyone else have comments on how best to resolve this issue?
> Eperson netID is lost editing the record from the webUI
> -------------------------------------------------------
>
> Key: DS-524
> URL: http://jira.dspace.org/jira/browse/DS-524
> Project: DSpace 1.x
> Issue Type: Bug
> Components: JSPUI
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0
> Reporter: Andrea Bollini
> Fix For: 1.7
>
> Attachments: ds-524-jspui.patch, eperson-edit.jsp.patch
>
>
> Editing an eperson record from the WebUI we lost the netid value.
> The only way to prevent this is set to true the property: ldap.enable
> The property is related to LDAP so I'm not sure if there is other
> implications to use it... anyway, we need to separate these two concerns.
> I propose to:
> 1) add a new configuration property to decide if the webUI is allowed to
> change the netid value; the authorization logic should be checked in the
> Servlet and not only on the client side as now is
> 2) always show the netid field, when appropriate as a readonly box
> We need to check also the XMLUI to get a common behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
