X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=ogRM8KktEgExCY4iar4jgLIPu/P10gAWZdglCE6O7Qk=;
        b=ncXhzqlb4TgZwy/Z8ZnwdcKiz5BOcxA0gMUWB4F1gANT6R6XS1yS+fIUPEaHYVj6tm
         74ACoH90Mhta2vfYFeCLOmqE1khWdZRtnw9mMPc3c87q9DVzlgzvdr1wppL2MB9vMkZ8
         1OdMff0uwzG9uwT8IGxFkSiYAa3CmRRp+BkE9FccvaTNF8dzWg4n8VjxjylFkaK8IVw/
         iGMzK0DMRjZme/0nhApRZU6vg+4kgqn33yKBmfLJAncYfopyGbj1tjbtaHM5GwuCIpXh
         u8wQoqoNAQSGqTlFKbQ2peqFqiqfs0tVd0wLZnTf29quWEBSwx2/II+GUHJTNEBj41mi
         38MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=ogRM8KktEgExCY4iar4jgLIPu/P10gAWZdglCE6O7Qk=;
        b=pkXqKm/7U25PcX5wGLhCe5OGR86BYxMpdLQAEKULjiCtKwHmsqRfF2W++WuPWYb1Mg
         SaAfxy5MfGJVAh+w3j7Oq24uj0ep+N/F2/wjHPFZ2t7QKT5o/6aeQsEa7CnZ2dEHeWZo
         jeeY+RU5jcP5P8fsOnE5iteyaGbjY0gmbNAl1K/Gi71c9BjBlLrGfpCKCovDKpckGZHx
         cP1HSZn2UvPmWMnHKJ7x0KyCZpzHusKtSQWLZ6d6imgKsMSMhScBOt6eAL6UJHzZkkoF
         iqKStsd7lGUaByH4evx/HkK8lMyPcpl9zLl/usgBjCWH9bKFvv/5/fFjFfmfhOEY0h+D
         UU0g==
X-Gm-Message-State: APjAAAUif6bvM7gAnR8f+sAY7pBauZm63zKoyfyo/c/bjdIyLfi1pjdS
	LJngYRlZXTO1qy0CYGCeCbBN87VF
X-Google-Smtp-Source: APXvYqw0ye/XfIX1n6hB7Mv1sONlidRG/Np2r4VqPI5j3Fd1YQr8d2ODS4RNBZXkqzQuRBCj8FagBA==
X-Received: by 2002:ac2:54b4:: with SMTP id w20mr8495316lfk.67.1580150321678;
        Mon, 27 Jan 2020 10:38:41 -0800 (PST)
Date: Mon, 27 Jan 2020 19:38:39 +0100
From: "N (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Engineering BOM Functionality
Message-Id: <20200127193839.4b5d72da5b2edbf72d2f9ac8@gmail.com>
In-Reply-To: <475A993D-7E38-4968-8E14-218A7B47B12D@fastmail.com>
References: <475A993D-7E38-4968-8E14-218A7B47B12D AT fastmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Had time to read a little bit more at the url you sent below. I found some text "The EBOM feature of bbcmd allows one or more symbols, in the schematics, to refer to a purchased part." and downloaded schematics. It did find symbol so no graphics for symbol but never the less I could edit the attributes and as I understand it you use scd attribute to reference a part in form of a json file, for example "100000.json" 

Do not have any comments if json is a good choice or not so not comment about this. I conclude the .json files work like a database with parts there each may have a list of "real" physical parts which could be bought from manufacturer(s).


My comment is I think it might be a really good idea to reference part from symbol so that part is chosen from symbol by using an attribute as you do in your schematic with the "scd" attribute! As I do now is to deduce part from attribute there I sometimes add an attribute with manufacturer part number but not always as there sometimes are many to chose from. I guess it should be straight forward to write a DRC checker to check attributes in part file against attributes in schematics against attributes in part which you have in the .json files.

If however attributes in symbol could be used to filter which parts are available for the list in the dialog then choosing value for the "scd" attribute referencing part you probably have something really good I have not seen in other schematic capture software, easy to use and understand. It would be a lLight symbol with all the advantages from a heavy symbol.



> Hello,
> 
> On some of my designs, manufacturing has come back asking for part substitutions. Currently, my BOMs are 1:1 with manufacturer part numbers — So, resistor would only have one source.
> 
> I’m creating a command line utility, that separates the component specification from the schematic symbol, for EBOMs. The project can be found here:
> 
>     https://github.com/ehennes775/bbcmd
> 
> Does anyone run into this issue? Is anyone interested in this functionality?
> 
> Thanks,
> Ed