mirror of
https://github.com/Part-DB/Part-DB-server.git
synced 2025-07-29 23:35:12 +02:00
Updated Concepts (markdown)
parent
0bc9a2d709
commit
c2c9a7dbc2
1 changed files with 1 additions and 1 deletions
|
@ -4,7 +4,7 @@ This page explains the different concepts of Part-DB and what their intended use
|
|||
## Part managment
|
||||
|
||||
### Part
|
||||
A part is the central concept of Part-DB. A part represents a single kind (or type) of a thing, like an electronic component, an device, an book or similar (depending on what you use Part-DB for). A part entity just represents a certain type of a thing, so if you have 1000 times an BC547 transistor you would create ONE part with the name BC547 and set its quantity to 1000.
|
||||
A part is the central concept of Part-DB. A part represents a single kind (or type) of a thing, like an electronic component, an device, an book or similar (depending on what you use Part-DB for). A part entity just represents a certain type of a thing, so if you have 1000 times an BC547 transistor you would create ONE part with the name BC547 and set its quantity to 1000. The individual quantities (so a single BC547 transistor) of a part, should be indistinguishable from each other, so that it does not matter which one of your 1000 things of Part you use.
|
||||
|
||||
## User System
|
||||
### User
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue