From 6b9ef431ee456b2e398527df3809e5e01b9a048c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6hmer?= Date: Thu, 5 Jan 2023 12:38:00 +0100 Subject: [PATCH] Updated Concepts (markdown) --- Concepts.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Concepts.md b/Concepts.md index fd05ff2..66018c6 100644 --- a/Concepts.md +++ b/Concepts.md @@ -22,6 +22,13 @@ A part entity have many fields, which can be used to describe it better. Most of * **Internal Part number** (IPN): Each part is automatically assigned an numerical ID which identifies a part in the database. This ID depends on when a part was created and can not be changed. If you want to assign your own unique identifiers, or sync parts identifiers with the identifiers of another database you can use this field. ## Attachments +### Attachment +An attachment is an file that can be associated with another entity (like a Part, Storelocation, User, etc.). This could for example be a datasheet in a Part, the logo of a vendor or some CAD drawing of a footprint. + +An attachment has an attachment type (see below), which groups the attachments logically (and optionally restricts the allowed file types), a name describing the attachment and a file. The file can either be uploaded to the server and stored there, or given as a link to a file on another webpath. If configured in the settings, it is also possible that the webserver downloads the file from the supplied website and stores it locally on the server. + +By default all uploaded files, are accessible for everyone (even non logged in users), if the link is known. If your Part-DB instance is publicly available and you want to store private/sensitve files on it, you should mark the attachment as "Private attachment". Private attachments are only accessible to users, which has the permission to access private attachments. +Please not, that no thumbnails are generated for private attachments, which can have an performance impact. ## User System ### User