Google Books API integration strategy #3

Open
opened 2026-08-23 11:16:36 +02:00 by gaetan · 0 comments
Owner

Part of #1

Question

Design the Google Books API integration for adding books. Key decisions:

  • Search flow: User types a query → we search Google Books API → show results → user picks a book → we fetch full details → create Book record
  • Manual entry fallback: User can manually enter title + author (no ISBN lookup). What fields do we capture in this case?
  • ISBN validation: Should we validate ISBN-10 and ISBN-13 format before lookup?
  • Edition conflicts: If a book with the same ISBN already exists, update it or skip?
  • Rate limiting: Google Books API has limits. Do we need caching for frequently searched books?

The integration should produce a clean Book record in our database from whatever source (API or manual).

Part of #1 ## Question Design the Google Books API integration for adding books. Key decisions: - **Search flow**: User types a query → we search Google Books API → show results → user picks a book → we fetch full details → create Book record - **Manual entry fallback**: User can manually enter title + author (no ISBN lookup). What fields do we capture in this case? - **ISBN validation**: Should we validate ISBN-10 and ISBN-13 format before lookup? - **Edition conflicts**: If a book with the same ISBN already exists, update it or skip? - **Rate limiting**: Google Books API has limits. Do we need caching for frequently searched books? The integration should produce a clean Book record in our database from whatever source (API or manual).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gaetan/Argus#3
No description provided.