-
Notifications
You must be signed in to change notification settings - Fork 494
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
Idea: Move "Managing Datasets and Dataverse Collections" under API Guide #8539
Comments
seconded: #8527 (comment) |
@kaitlinnewson no objection but rather than a wholesale removal, on the "Managing Datasets and Dataverse Collections" can you please leave the headers and link to the sections of the API Guide? That's what we do at https://guides.dataverse.org/en/5.10/admin/user-administration.html (screenshot below). Here's the rst:
Hmm. I see there are a lot of headings under "Managing Datasets and Dataverse Collections"... ... if what I'm suggesting sounds unreasonable, please let me know. |
Here's a related issue where I'm looking for a place in the guides to link to scripts that the community has written for migrating data into Dataverse: |
Just mentioning that the issue at #8120 is related. |
Closing in favor of this issue: |
Overview of the Feature Request
As someone frequently using the User Guide, I often have a hard time finding the page "Managing Datasets and Dataverse Collections", which is primarily made up of API commands. It is currently under Admin Guide, but I would like to recommend moving it under the API section instead. I am happy to make a PR for this if others agree.
What kind of user is the feature intended for?
API Users looking for documentation.
What inspired the request?
I have a hard time finding this page! But I'm starting with an issue before a PR in case others feel differently.
What existing behavior do you want changed?
The location of the "Managing Datasets and Dataverse Collections" page.
Any brand new behavior do you want to add to Dataverse?
No
Any related open or closed issues to this feature request?
No
The text was updated successfully, but these errors were encountered: