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.

Sign up for GitHub

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

Jump to bottom

Check all API requests of Datasets for identifier compatibility #17

Open
1 task
skasberger opened this issue Jun 21, 2019 · 2 comments
Open
1 task

Check all API requests of Datasets for identifier compatibility #17

skasberger opened this issue Jun 21, 2019 · 2 comments
Assignees
@skasberger
Labels
pkg:api api related activities prio:medium status:confirmed Is a valid issue and will be moved forward soon. type:feature New feature

Comments

@skasberger
Copy link
Member

skasberger commented Jun 21, 2019 •
edited
Loading

Check which API endpoints are compatible with using as identifier the Dataverse database ID and/or the PID.

API Endpoints

  • ENDPOINT: RESULT
  • ENDPOINT: RESULT

After that, update the requests, so that both variations are possible and implemented.

See #71
@skasberger skasberger added type:feature New feature pkg:api api related activities labels Jun 21, 2019
@skasberger skasberger added this to the v0.2.2 milestone Jun 21, 2019
@skasberger skasberger self-assigned this Jun 21, 2019
@skasberger
Copy link
Member Author

have a look on the swagger output image.

@skasberger skasberger changed the title Check Api requests of Datasets, if dataset id and/or persistend id for requesting is possible Check all Native API Dataset requests for identifier compatibility Jun 19, 2020
@skasberger skasberger changed the title Check all Native API Dataset requests for identifier compatibility Check all API requests of Datasets for identifier compatibility Jun 19, 2020
@skasberger skasberger modified the milestones: v0.2.2, v0.3.0, v0.4.0 or later Jun 19, 2020
@skasberger skasberger added prio:medium status:confirmed Is a valid issue and will be moved forward soon. labels Jun 26, 2020
djbrooke pushed a commit to djbrooke/pyDataverse that referenced this issue Feb 9, 2021
@skasberger
fix travis ci error gdcc#17
82162b7
This was referenced Feb 15, 2021
Open
Open
@skasberger skasberger modified the milestones: Later, v0.4.0 Feb 17, 2021
@skasberger skasberger mentioned this issue Mar 14, 2021
Open
35 tasks
@pdurbin
Copy link
Member

pdurbin commented Feb 14, 2024

As discussed during the 2024-02-14 meeting of the pyDataverse working group, we are closing old milestones in favor of a new project board at https://github.com/orgs/gdcc/projects/1 and removing issues (like this one) from those old milestones. Please feel free to join the working group! You can find us at https://py.gdcc.io and https://dataverse.zulipchat.com/#narrow/stream/377090-python

@pdurbin pdurbin removed this from the v0.4.0 milestone Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@skasberger skasberger

Labels
pkg:api api related activities prio:medium status:confirmed Is a valid issue and will be moved forward soon. type:feature New feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pdurbin @skasberger