-
Notifications
You must be signed in to change notification settings - Fork 476
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
[doc] Emphasize diferences between Dataverse Native API and SWORD API auth mechanism #7441
Comments
djbrooke
added this to Up Next 🛎
in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
Nov 30, 2020
Thanks @joenio, it should be an easy addition. |
@joenio thanks for creating this issue. Are you interested in making a pull request? The file to edit is doc/sphinx-guides/source/api/sword.rst. If not, no worries, we'll get to it someday. 😄 |
pdurbin
moved this from Up Next 🛎
to IQSS Team - In Progress 💻
in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
Dec 18, 2020
pdurbin
added a commit
that referenced
this issue
Dec 18, 2020
pdurbin
removed this from IQSS Team - In Progress 💻
in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34)
Dec 18, 2020
kcondon
added a commit
that referenced
this issue
Jan 5, 2021
emphasize differences with SWORD auth (vs. native) #7441
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would be nice if Dataverse SWORD API doc emphasize that the SWORD API does have a quite different auth mechanism then the Dataverse Native API doc.
The Dataverse SWORD API doc where would be nice to be updated:
Forum thread where this point emerged:
The text was updated successfully, but these errors were encountered: