internetarchive / internetarchive/openlibrary

Reading Check-Ins enhancements

Open
#7,546 0 comments 0 reactions 0 assignees View on GitHub
Lead: @jimchamp Priority: 4 Theme: Yearly Reading Goals Type: Feature Request
Dominant language
Python
Stars
6.7k
Forks
2k
Avg merge
2d 19h
Merged PRs (30d)
138

Description

When users mark book as Read in Open Library they can add optional Reading Check-in date when they finished reading the book.

This issue is intended to track possible enhancements for Reading Check-Ins

Some of the features that are needed:
- [ ] Adding multiple Check-Ins

One of the expected features for book tracking is to be able to add multiple finishing dates per book for rereadings. Currently, this is not possible in Open Library which might prevent some users from fully moving their book tracking efforts into our site. This is not nice-to-have feature, but is to-be-expected
- [ ] Being able to set when I started certain Read of the book

I remember seeing, that this date might be stored somewhere internally, but is not exposed to user. This would also be useful from data standpoint since we might get enough data to provide something like "Readers usually finish this book in X days"
- [ ] Being able to manually specify which edition I read for each Check-In

I am not sure how many users will benefit from this, but I often read different editions of books and this might be a useful feature if it is ever implemented. Maybe, this can be hidden behind some Advanced mode.

Other:
- [ ] Progress tracking

Sites like Goodreads allow users to update their progress during reading the book. It can be in the form of pages or percentage:
I've read X pages out of XXX pages from the edition
I've read 10% of the edition

Progress tracking is to be split into a separate issue

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points and groups several possible Reading Check-Ins enhancements. Start by selecting one enhancement and clarifying its requirements with the project maintainers; done is not defined until the chosen behavior and scope are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.