-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4406 dataverse move api #4543
4406 dataverse move api #4543
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use curl syntax. Thanks!
|
||
Moves a dataverse whose id is passed to a new dataverse whose id is passed. The dataverse alias also may be used instead of the id. If the moved dataverse has a guestbook, template, metadata block, or featured dataverse that is not compatible with the destination dataverse, you will be informed and given the option to force the move and remove the association. Only accessible to superusers. :: | ||
|
||
POST http://$SERVER/api/dataverses/$id/move/$id?key=$apiKey |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please replace this with a full curl
command using the syntax is uses such as -X POST
?
|
||
Moves a dataset whose id is passed to a dataverse whose alias is passed. If the moved dataset has a guestbook that is not compatible with the destination dataverse, you will be informed and given the option to force the move and remove the guestbook. Only accessible to superusers. :: | ||
|
||
POST http://$SERVER/api/datasets/$id/move/$alias?key=$apiKey |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above. Please use curl
syntax.
|
||
:: | ||
|
||
GET http://$SERVER/api/admin/list-users |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make this a working example with curl syntax.
} | ||
} | ||
|
||
.. note:: "List all users" ``GET http://$SERVER/api/admin/authenticatedUsers`` is deprecated, but supported. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's weird that someone marked this as deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it not deprecated? Should this line be removed?
Also, both are supported. Nothing is deprecated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good as of 10fbfc4
This pull request extends the Native API to allow a superuser to move a dataverse.
If a move is forced, the functionality is as follows:
These rules should also follow for any children of the moved dataverse.
This pull request also adds the ability to remove a dataverse or a dataset link through the API. This endpoint is only available to superusers.
Related Issues
Pull Request Checklist