# Django Models

**URL:** <https://forum.djangoproject.com/t/django-models/10563>\
**Category:** Using Django\
**Created:** [November 18, 2021, 9:20am UTC](https://forum.djangoproject.com/t/django-models/10563 "2021-11-18T09:20:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aliman00](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/aliman00/32/6402_2.png) [@Aliman00](https://forum.djangoproject.com/u/Aliman00)\
**Post date:** [November 18, 2021, 9:20am UTC](https://forum.djangoproject.com/t/django-models/10563/1 "2021-11-18T09:20:26Z")

</div>

Hello good folks,

I’m new to Django and really love concept and idea behind it. With that said I’m having a bit hard time thinking or structuring stuff that’s inside my head down to models, so perhaps some of you can give me a pointer on how to go about this case.

What I need to make is this :

Section 1 / 1  
Next button , last button

npc\_1\_1 : input field  
player\_1\_1: input field  
npc\_1\_2 : input field  
player\_1\_2: input field

and so on…

Then when clicking on next  
It would give me  
npc\_2\_1: input field  
player\_2:1: input field  
npc\_2\_2: input field  
player\_2\_2: input field

Clicking last would take me back to first input with 1\_1

Now is it possible to structure something like this in models ?? I’m thinking it should be able to but not sure how to go about to do it ?? so any help would be more then welcome

---

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [November 18, 2021, 2:00pm UTC](https://forum.djangoproject.com/t/django-models/10563/2 "2021-11-18T14:00:59Z")

</div>

A Django model is a Python representation of a relational database table. The techniques and concepts that you would learn in studying database design apply directly to the design of your Python models.

What you want to be looking for are some tutorials on database design and data normalization. (No, I do not have any current materials on that topic to recommend at the moment.)

A proper database design starts with understanding what needs to be stored and how it’s going to be used. (Our internal process starts with identifying what we call “entities” - the real-life objects for which data needs to be managed. Everything builds from them.)

You haven’t really provided any details about your intended application or how the data needs to be structured or used, so it’s not really practical to offer recommendations regarding your model design.