-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upload does not work with new 4TU platform #73
Comments
Or perhaps we could figure out how to make it work with the new 4TU platform. :) |
Because the new platform is not compatible with the Figshare API it requires a new client. Similar endpoint URLs do not bring compatibility as long as their behaviour are significantly different from the reference implementation. If you provide a proper API documentation if will be useful. |
Well if that's what you conclude, then that is what you conclude. I'd like to see if perhaps after we work out some bugs in the new 4TU platform we can make it compatible for your purpose. |
Sure, we will be happy to report the issues we identified. I think some of them might be design decisions, not bugs, e.g. not providing account/categories end point. Do you target 100% compatibility? |
Just to clarify both options mentioned by @roelj and @manuGil are the same option. When Manuel refers to developing a new client, it means a new client extension within our fairly package with a client implementation for 4TU. So it wouldn't be a new package exclusively for 4TU, it would be an extension of the package, or a plugin for 4TU if you like ;) Indeed if 4TU web API is fully compatible with figshare, then we can simply reuse figshare. |
Uploading dataset fails due to changes in the endpoints of the new platform of the repository.
A new client for fairly should be developed to solve this issue.
The text was updated successfully, but these errors were encountered: