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

API Documentation Organization #1489

Closed
mercecrosas opened this issue Feb 21, 2015 · 11 comments
Closed

API Documentation Organization #1489

mercecrosas opened this issue Feb 21, 2015 · 11 comments
Assignees

Comments

@mercecrosas
Copy link
Member

The API guides should be organized in the following way:

Main APIs, more frequently used by external parties:

  • Deposit API (SWORD)
  • Search API
  • Dataset Metadata API (get metadata for a dataset in multiple formats)
  • Dataset File API (or Data API, get data files for a dataset)

Dataverse Native APIs (advanced APIs)

  • All native APIs
@posixeleni
Copy link
Contributor

@scolapasta can we meet next week to discuss what remains to be done for this? And who needs to work on documenting each API. @mcrosas and I spoke recently that the API Guides will need to be ready sooner than other guides (aside from User Guide) since we want others to easily be able to integrate with us ASAP after 4.0 is released.

@pdurbin
Copy link
Member

pdurbin commented Apr 9, 2015

Putting "all native APIs" on a single page at http://guides.dataverse.org/en/latest/api/native-api.html feels wrong since there are so many endpoints there.

Are we saying that creating a dataset with JSON is an advanced operation?

@eaquigley eaquigley assigned eaquigley and unassigned scolapasta May 14, 2015
eaquigley added a commit that referenced this issue May 14, 2015
updated order based on #1489
@eaquigley
Copy link
Contributor

Passing to @posixeleni to QA for me.

@posixeleni
Copy link
Contributor

now displaying as expected in http://guides.dataverse.org/en/latest/api/index.html

closing.

@pdurbin
Copy link
Member

pdurbin commented May 15, 2015

@posixeleni I'm a little troubled that my concerns at #1489 (comment) were not addressed at all. :(

@posixeleni
Copy link
Contributor

@pdurbin I'm going to create a new ticket related to your concern so that we can track it separately from this ticket which needed to be completed asap. Unfortunately I dont have an answer for you but if you have a proposal for how you want the Native API documentation to look like I would strongly recommend you put something together!

@pdurbin
Copy link
Member

pdurbin commented May 15, 2015

@posixeleni perfect! Thanks for creating #2174! We'll sort this out in a future version of the API docs. :)

@bencomp
Copy link
Contributor

bencomp commented May 19, 2015

It seems there is no Dataset Metadata API at http://guides.dataverse.org/en/latest/api/index.html. Am I missing something?

@pdurbin
Copy link
Member

pdurbin commented May 19, 2015

@bencomp since this ticket is in QA can we please discuss this further in #2174?

@bencomp
Copy link
Contributor

bencomp commented May 20, 2015

@pdurbin I think it has little to do with the native API #2174, so creating a new issue or reopening this one makes more sense to me.

@pdurbin
Copy link
Member

pdurbin commented May 20, 2015

@bencomp it sounds like you're going think some more about what the new issue would be: http://irclog.iq.harvard.edu/dataverse/2015-05-20#i_20044

And that you're ok with this issue going through QA for 4.0.

Again, we'll improve the API doc organization in #2174.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants