Footprint Metadata Support

[davidperrenoud]

From brendan....@gmail.com on October 13, 2008 10:42:02

What steps will reproduce the problem? 1. Try to find a footprint file when you don't know the name of the package or file name. What is the expected output? What do you see instead? The footprint files should have some sort of metadata in them so that parts creators can easily find parts based on various properties as well as text search.
Suggested solution is to add fritzing:tag namespace tags to footprint SVGs as well as adding intermediate UI based choices/filter in the parts editor. Using something like "provides/properties" would work as well.

Original issue: http://code.google.com/p/fritzing/issues/detail?id=173

[davidperrenoud]

From andre.knoerig@gmail.com on October 15, 2008 06:37:28

Not sure I understand this: Is this about finding a footprint that could work with my newly created part? But then I could look for similar parts and see what footprint they are using, or not? Could you elaborate a little bit?

[davidperrenoud]

From brendan....@gmail.com on October 15, 2008 07:33:58

This is about searching through footprints during part authoring process.

Right now the user only has a file name for a footprint. If the file is named TO-220.svg and the part creator knows that she needs that footprint, then everything is fine. However, some parts don't use standard package names, and some footprint creators may use file names that will not be obvious.

The ability to context filter footprints will also be necessary as the number of potential footprints expands from dozens to hundreds or thousands.

It would also be nice to have some Dublin Core like metadata in the footprints to keep track of authors, versions, etc.

[davidperrenoud]

From brendan....@gmail.com on October 30, 2008 08:53:57

Labels: -Priority-High Priority-Medium

[davidperrenoud]

From irasc...@gmail.com on March 25, 2010 14:23:08

It looks to me like Dublin Core and its frequent partner RDF are very abstract metadata
containers which are meant to work with more specific metadata language definitions.
In other words, I believe that to work with Dublin Core/RDF we would have to find an xml namespace for describing parts, or come up with our own.

[davidperrenoud]

From irasc...@gmail.com on September 27, 2010 14:04:53

Labels: Component-Parts

[davidperrenoud]

From irasc...@gmail.com on October 09, 2011 01:23:26

Labels: -Milestone-1.0

[davidperrenoud]

From irasc...@gmail.com on April 19, 2013 04:36:13

Owner: irasc...@gmail.com

[failiz]

I agree that this is needed in the future part editor. Not sure if metadata is the best way. Most CAD programs (f ex. KiCad) use libraries, keyword and number of pins filters.