Experimented with part generation and determined that part-per-footprint export is the way to go, added documention within /conversion

Author: marshalltaylorSFE

Conversion/README.md

@@ -22,6 +22,33 @@ https://github.com/lachlanA/eagle-to-kicad
 
 **Note:** This is very hacky.  It would be best to establish the proper libraries first, then link to those rather than have the script spit out specific libs for each board.  This insures the resultant file is consistent with the KiCad libraries.
 
+#### Analysis of naming
+
+In order to write a script, it must link parts from two files.  It seems the only way to do that is by using the name of the component/footprint/etc, so let's explore that.  Using these eagle export scripts, there are a few options for naming convention.
+
+.. But first let's see what happened to a highly nested component in eagle... the 10uF cap.  In eagle, the part is called "10UF" and has sub-parts -0603-... etc for all packages.  In KiCad the symbol is called "10UF" and there are 4 suggested footprints within the footprint filter that are generated, 0603, 0805, 1206, 1210.  This is kind of a problem because I really want to retain a prod_id for each package, so these will need to be un-nested.
+
+To solve this, during library export select the drop down "Combine Parts/package variants where possible" and choos "Out put new part for every foot print type" instead.  The result is that each variant now has it's own (duplicate) symbol.  (note: the filter is still filled with all possible footprints.  **This will need to manualy be fixed**)
+
+For instance, eagle part in file "SparkFun-Capacitors.lbr", the 10UF is:
+
+* "deviceset name="10UF" prefix="C""
+  * "device name="-0603-6.3V-20%" package="0603""
+  * "device name="-1206-6.3V-20%" package="1206""
+  * "device name="-0805-10V-10%" package="0805""
+  * "device name="-1210-50V-20%" package="1210""
+
+The resultant parts in KiCad are named:
+
+* 10UF-0603-6.3V-20%
+* 10UF-1206-6.3V-20%
+* 10UF-0805-10V-10%
+* 10UF-1210-50V-20%
+
+.. The superfluous filters are mitigated by a new field "Footprint" which contains "0805", etc.
+
+The conclusion is that the script must identify parts by the part-per-footprint names within the exported libraries for application of prod_id fields.
+
 ### Combine footprints and have single source for common footprints
 
 A tool for moving symbols and footprints between .mod and .lib files: