Support #16441
closedDocument user merge by admin
100%
Description
The "user merge" feature is not completely documented in the admin section. The page https://doc.arvados.org/v2.0/admin/reassign-ownership.html doesn't describe --redirect-to-new-user.
Also, the "merge" API call is completely missing from the API documentation.
Updated by Peter Amstutz over 4 years ago
- Target version changed from 2020-06-03 Sprint to 2020-06-17 Sprint
Updated by Peter Amstutz over 4 years ago
- Target version changed from 2020-06-17 Sprint to 2020-07-01 Sprint
Updated by Peter Amstutz over 4 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 4 years ago
16441-user-merge-doc @ 3a6559843024bda72c9a7b0baed3578d8698223d
Document how to link user accounts by admin and add the method to the API docs.
Updated by Lucas Di Pentima over 4 years ago
Some comments & questions:
- File doc/admin/link-accounts.html.textile.liquid
- Line 22: I think the word ‘by’ is missing on “…records owned the old account"
- I think we are using
zzzzz
for cluster id examples on the documentation?
- To avoid confusions, would it be best to replace “old” and “new” with “from/origin” and “to/target” or something equivalent? That would make the clarification unnecessary at the link-accounts doc page. The downside is that the API params already use “old” & “new”.
- With that, LGTM.
Updated by Peter Amstutz over 4 years ago
Lucas Di Pentima wrote:
Some comments & questions:
- File doc/admin/link-accounts.html.textile.liquid
- Line 22: I think the word ‘by’ is missing on “…records owned the old account"
- I think we are using
zzzzz
for cluster id examples on the documentation?
Fixed.
- To avoid confusions, would it be best to replace “old” and “new” with “from/origin” and “to/target” or something equivalent? That would make the clarification unnecessary at the link-accounts doc page. The downside is that the API params already use “old” & “new”.
The goal is to document how to use the 'arv' command correctly, which uses the terms "old" and "new" from the API. I agree it is confusing, but I don't think using different terms would allow us to avoid the clarification about the use of "old" and "new" because the admin needs to understand it well enough to construct the command line correctly.
- With that, LGTM.
Will merge, thanks.
Updated by Peter Amstutz over 4 years ago
- Status changed from In Progress to Resolved