Skip to content
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

Docs: Review API and Options functionality not listed in main api or config sections to see whether should be added to reference-style list. #5155

Closed
kcondon opened this issue Oct 9, 2018 · 5 comments

Comments

@kcondon
Copy link
Contributor

kcondon commented Oct 9, 2018

There are several places in the guides where api endpoints and jvm options are listed in topics but not in the configuration section or the api guides:

S3 jvm options
Shibboleth
Admin
Big Data
Other?

This ticket is to review what is there to see if this is intentional and whether it makes sense to consolidate into a reference section in addition to where the currently live.

@pdurbin
Copy link
Member

pdurbin commented Aug 20, 2019

@kcondon in pull request #6107 I tried to address this in a new "Lists of Dataverse APIs" section that looks like this:

Screen Shot 2019-08-20 at 5 46 55 PM

Does this help?

I also added a new FAQ page and the question "Where is the Comprehensive List of All API Functionality?" that references #5794 and the fact that if we upgrade to Payara (#4172) we can get a complete list of API commands in Swagger/OpenAPI format. Here's how that question and answer look:

Screen Shot 2019-08-20 at 5 49 57 PM

I also mentioned the Payara thing in my API talk the other day. Here are my notes from that talk: #6086 (comment)

@kcondon
Copy link
Contributor Author

kcondon commented Aug 21, 2019

@pdurbin Seems reasonable. Minor quibble, I might adjust the SWORD description from saying a standards based approach to saying using the SWORD standard.

@poikilotherm
Copy link
Contributor

poikilotherm commented Feb 11, 2022

Today I had to lookup some stuff in the API docs and it bothered me that it's sometime complicated to parse the information or find out that an endpoint is missing from the docs and it would be nice to have more examples.

Looking at #5794 and this issue, maybe one day we can do something like one of these:

@poikilotherm
Copy link
Contributor

Today I learned about https://github.com/SAP/swagger-plugin-for-sphinx to include Swagger HTML pages within your Sphinx build.

@pdurbin pdurbin added the Type: Suggestion an idea label Nov 16, 2023
@cmbz
Copy link

cmbz commented Aug 20, 2024

To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.

If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.

@cmbz cmbz closed this as completed Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants