Bug 816: Add distributor tables

Open
  • Is something wrong?
#237 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
django, python
Domain
backend

Research direction

The issue asks for new distributor and printer tables, display pages, and forms modeled after the existing publisher implementation. Start by locating the publisher model, view, and form files in the codebase to understand the pattern. Then create analogous components for distributor and printer, and verify by running the test suite.

Written by the indexing model from the issue text.

Description

board indexing

Originally Opened: 2013-08-05 05:42 PST

Per board vote http://www.comics.org/voting/ballot/186/ add a distributor and a printer table to the db; each modeled after the publisher table: name, year began and year ended for general business and for comics business and uncertainty flags for each year, URL, notes, keywords. Create display pages for each table similar to publisher display page. Create data entry forms and change set review forms for each similar to publisher forms.

Dominant language
Python
Stars
122
Forks
36
Avg merge
2d 16h
Merged PRs (30d)
28

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GrandComicsDatabase/gcd-django

All issues in GrandComicsDatabase/gcd-django

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.