Handling expired accounts needs to be improved
Users come and go in an IPT, therefore handling expired accounts needs to be improved in the following ways:
- Allow any admin to set any admin as the primary admin.
- Allow any account to be deactivated:
- Only applies to an account set as the creator of one or more resources (otherwise the account just gets deleted).
- Deactivation/reactivation can only be done by an admin.
- The primary admin account cannot be deactivated.
- Following deactivation the user cannot login.
Original issue reported on code.google.com by burkeker.gbif on 2011-05-15 21:16:08
This sounds like a recipe for more issues to me. Would it not be sufficient to allow
any Admin to set any Admin as a primary Admin?
Original issue reported on code.google.com by gtuco.btuco on 2011-05-16 02:52:02
Yes, to have admin granting primary Admin to another is enough for the 1st issue.
I think there are 2 issues here. I'll create another specific one later.
Original issue reported on code.google.com by burkeker.gbif on 2011-05-16 09:23:53
About primary admin:
Two ideas comes to my mind:
1. Create a drop-down list showing admin users in "User accounts manager page" (ipt/admin/users.do).
Maybe I could add a radio button in a new column in the table - only for admins.
In either case, I would have to add a new button to save the changes.
2. Or, I could add a check box in "Create/Edit User Account" that will be displayed
only if user role is marked as Admin.
For this two ideas, a popup should be displayed asking again if are you sure to make
this kind of change and explaining a little bit the decision and what will happen.
About users who no longer work for the institution:
- I'm agree with your implementation. (deactivate option).
Original issue reported on code.google.com by htobon on 2011-05-16 19:42:34
- Labels added: Milestone-Release2.0.3, Priority-Medium
(No text was entered with this change)
Original issue reported on code.google.com by kyle.braak on 2011-07-04 14:38:01
- Labels added: Milestone-Release2.0.4
- Labels removed: Milestone-Release2.0.3
(No text was entered with this change)
Original issue reported on code.google.com by kyle.braak on 2011-11-04 09:59:47
- Labels added: Milestone-Release2.0.x
- Labels removed: Milestone-Release2.0.4
(No text was entered with this change)
Original issue reported on code.google.com by kyle.braak on 2013-03-19 11:50:49
- Labels added: Milestone-Release2.1.X
- Labels removed: Milestone-Release2.0.x
(No text was entered with this change)
Original issue reported on code.google.com by kyle.braak on 2014-03-19 18:21:24
- Labels added: Milestone-Release2.2.X
- Labels removed: Milestone-Release2.1.X
(No text was entered with this change)
Original issue reported on code.google.com by kyle.braak on 2015-02-24 21:19:35
- Labels removed: Milestone-Release2.2.X
I was trying to find a way to inactivate, rather than delete, accounts that haven't been used in > 1 year. I was going to pull a new issue, but it seems like my thoughts might be better added here.
It would be nice if the user profile page (https://ipt-obis.gbif.us/admin/[email protected]) included a table of the datasets over which they have management rights. This would be the same table that the user sees when they click on "Manage Resources."
This would make it easier for the Admins to quickly understand (1) whether the account is actually linked to any datasets and, (2) gain some context for why the account hasn't been active.
Oops, I should have dug a bit more before I commented. It looks like #1251 says this ticket should have been resolved a few releases ago. @MattBlissett What's the status of the discussion here?
I have the same problems with some datasets. The dataset was created with the curator from the collection (at the date) as the manager. Now the person no longer works on the institution so i manually add the new curator as manager for the dataset. Now the previous person still needs to use the IPT to publish resources on the new institution so i can't delete the account.
How can i transfer the property to the new curator (as the dataset from a scientific collection is managed form the new curator)
Thank you for your comments.
@sformel-usgs unfortunately, that issue (1251) was not resolved.
I can see that this feature can be very useful. Let's see if we can include in one of the next releases.