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

Investigate using SWORD V2 when multipart deposit is fixed #8

Open
dac514 opened this issue Aug 24, 2017 · 0 comments
Open

Investigate using SWORD V2 when multipart deposit is fixed #8

dac514 opened this issue Aug 24, 2017 · 0 comments
Labels
book info related to the book info admin page, book metadata, or the relevant sections of a book's homepage dev tools related to tools/processes we might use in software development help wanted third party related to third party tools, services, integrations or plugins

Comments

@dac514
Copy link
Contributor

dac514 commented Aug 24, 2017 •
edited by SteelWagstaff
Loading

Description

This plugin uses SWORD V1 because we had issues with SWORD V2.

Investigate the feasibility of SWORD V2 when multipart deposit is fixed (or removed.)

Optionally, investigate doing a POST of an Atom Entry and a PUT of the Media Resource in two distinct HTTP requests over SWORD V2.
@SteelWagstaff SteelWagstaff added dev tools related to tools/processes we might use in software development third party related to third party tools, services, integrations or plugins book info related to the book info admin page, book metadata, or the relevant sections of a book's homepage labels Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
book info related to the book info admin page, book metadata, or the relevant sections of a book's homepage dev tools related to tools/processes we might use in software development help wanted third party related to third party tools, services, integrations or plugins
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dac514 @SteelWagstaff