Book list shows the oldest additions first, not the newest

Nobody has started this yet — be first.

Business impact

This is a personal library tracker -- the whole point of the list view is "what did I just add." Right now the default GET /api/books/ order buries every new addition at the very last page instead of the first, which for anyone with more than a page of books means the app looks "broken" or "stuck" every time they add something, since the thing they just did is invisible until they page all the way through. It's the kind of regression that doesn't throw an error anywhere, so it won't show up in a smoke test -- only in a user actually scrolling and asking "where did my book go?"

Problem

GET /api/books/ (no query params) returns books ordered oldest-added first.

Current behavior

A freshly created book appears on the last page of the list instead of the first.

Expected behavior

GET /api/books/ returns books ordered newest-added first -- the most recently created book appears on page 1.

Steps to reproduce

cd django/library_tracker source ../library_tracker_venv/bin/activate python manage.py shell -c " from books.models import Book Book.objects.create(title='First', author='A') Book.objects.create(title='Second', author='B') print(list(Book.objects.values_list('title', flat=True))) "

-> ['First', 'Second'] -- the newest addition ('Second') is last, not first

Why this matters

Book.Meta.ordering is the single line that controls the default queryset order for every unfiltered list request -- DRF's ModelViewSet doesn't add its own ordering on top, it just executes Book.objects.all() as-is. A leading "-" on a field name means descending; without it, ascending. That's the entire difference between "newest first" and "oldest first," and it's trivial to drop by accident when typing the field name.

Suggested approach

Look at Book.Meta.ordering in books/models.py and compare it against what "most recently added first" requires for a DateTimeField like date_added.

Acceptance criteria

GET /api/books/ with no query params returns the most recently added book first.
practicetickets/test_ticket02_ordering_flip.py passes.

Verification

python manage.py test practicetickets.test_ticket02_ordering_flip -v 2

Hints (0/2)

Try it without hints first — the reading is the exercise.

Working on this ticket

Work on a branch named for the ticket — that's what you'll submit.

Branch off your fork

$git checkout -b fix/ordering-flip

Fix it and commit

Meet every acceptance criterion, and add a test that would have caught this.

Push the branch

$git push -u origin fix/ordering-flip

Submit it below

Paste your fork URL and the branch name, with a short write-up of the root cause.

Submit your fix

Questions

Stuck on something?

Ask about anything unclear in the ticket — the maintainer and anyone who has solved it can answer. Please don't post full solutions.

No questions yet. If something in this ticket reads ambiguously, you are probably not the only one — ask.

The project

Library Tracker — A Django REST Framework Reading Log

A compact Django + DRF book-tracking API where the same handful of business rules -- a rating is 1-5, a read book needs a finish date -- are deliberately enforced at three independent layers (model validators, serializer validation, a database CheckConstraint), and the interesting bugs live in the gaps between them.

Fork on GitHub

Download

Setup

Library Tracker — A Django REST Framework Reading Log

git clone <your-fork>
cd <your-fork>/django/library_tracker
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

python manage.py migrate
python manage.py createsuperuser
python manage.py runserver

The API is then at and the admin at . , , and are read from the environment with sensible local defaults -- no secrets are hardcoded.