Ticket #277 (accepted defect)
Opened 3 years ago
Last modified 3 years ago
books accessible via archive.org ids
| Reported by: | douglas | Owned by: | douglas |
|---|---|---|---|
| Priority: | major | Milestone: | Bugs |
| Component: | Booki | Keywords: | |
| Cc: | adam aco douglas |
Description
The archive want to be able reference booki books by their archive ID. Raj suggests http://booki.cc/edit/<archive-ID>/bookId.epub but obviously the exact form of the URL doesn't matter.
If the book doesn't exist, booki would import it from the archive, then present it for editing.
If a booki book based on that archive book does exist, then that book's edit page is shown.
If there are many booki books based on the same archive book, I guess it just has to pick one.
The simplest thing as far as I can see would be for this to be a redirect, with the url being something like /_archive.org/whatever.
This is very close to the http://is-this-book-on.booki.cc/ thing suggested for #276, though that service differs in two ways: it wants to know that a book has been edited, not just imported, and it would probably prefer to redirect to the archive s3 servers rather than to booki if it can.
Change History
comment:1 Changed 3 years ago by adam
comment:2 follow-up: ↓ 3 Changed 3 years ago by aco
Can you please explain more this "and it would probably prefer to redirect to the archive s3 servers rather than to booki if it can."? I guess my questions is, what is on s3 servers?
As i understand, if that book has been imported and edited, we show booki editor for that book. If that book does not exist, then it will import it and then open editor. Now, while doing the import we can show some "importing, please wait message..." and then after it has been imported do redirect on editor page. But i guess, that part is not a problem.
comment:3 in reply to: ↑ 2 Changed 3 years ago by douglas
- Owner changed from adam, aco, douglas to douglas
- Status changed from new to accepted
Replying to aco:
Can you please explain more this "and it would probably prefer to redirect to the archive s3 servers rather than to booki if it can."? I guess my questions is, what is on s3 servers?
The archive s3 servers.
The two cases are:
- When an archive info page is loaded, it wants to have a link to the "corrected epub" if there is one. This isn't an edit link, it is an epub link. If there is an up-to-date epub on the archive site, it will link to that, otherwise it links to a booki url that generates an epub (and uploads it to s3). This is the #276 case. s3 is acting as a caching server for booki.
- Every archive info page has a link saying "correct this book". If it is followed, it either imports that book into booki, or it finds a version of that book that is already there, then provides an edit interface. So yes, this is right:
As i understand, if that book has been imported and edited, we show booki editor for that book. If that book does not exist, then it will import it and then open editor. Now, while doing the import we can show some "importing, please wait message..." and then after it has been imported do redirect on editor page. But i guess, that part is not a problem.
I will make a simple proxy server that does the redirect stuff.
in addition...i think we should design somehting simple so that we can identify books by other kinds of id...ie. dont make this archive specific - there might be other orgs that would like to import content into booki but wish to retain their own identifier