From 979937794956f802d4c2bd34798bde45e921bb95 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6hmer?= Date: Tue, 20 Dec 2022 15:11:57 +0100 Subject: [PATCH] Updated Concepts (markdown) --- Concepts.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Concepts.md b/Concepts.md index 62d9b38..98be436 100644 --- a/Concepts.md +++ b/Concepts.md @@ -5,6 +5,9 @@ This page explains the different concepts of Part-DB and what their intended use ### 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. 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. +A part entity have many fields, which can be used to describe it better. Most of the fields are optional: +* **Name** (Required): The name of the part or how you wanna call it. This could be an manufacturer provided name, or a name you thought of your self. The name have to be unique in a single category. +* **Description**: A short (single-line) description of what this part does ## User System ### User