{"action":"created","issue":{"url":"https://api.github.com/repos/KiCad/kicad-library/issues/808","repository_url":"https://api.github.com/repos/KiCad/kicad-library","labels_url":"https://api.github.com/repos/KiCad/kicad-library/issues/808/labels{/name}","comments_url":"https://api.github.com/repos/KiCad/kicad-library/issues/808/comments","events_url":"https://api.github.com/repos/KiCad/kicad-library/issues/808/events","html_url":"https://github.com/KiCad/kicad-library/issues/808","id":192232652,"number":808,"title":"Add metadata to libraries","user":{"login":"kuro68k","id":2674466,"avatar_url":"https://avatars.githubusercontent.com/u/2674466?v=3","gravatar_id":"","url":"https://api.github.com/users/kuro68k","html_url":"https://github.com/kuro68k","followers_url":"https://api.github.com/users/kuro68k/followers","following_url":"https://api.github.com/users/kuro68k/following{/other_user}","gists_url":"https://api.github.com/users/kuro68k/gists{/gist_id}","starred_url":"https://api.github.com/users/kuro68k/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kuro68k/subscriptions","organizations_url":"https://api.github.com/users/kuro68k/orgs","repos_url":"https://api.github.com/users/kuro68k/repos","events_url":"https://api.github.com/users/kuro68k/events{/privacy}","received_events_url":"https://api.github.com/users/kuro68k/received_events","type":"User","site_admin":false},"labels":[{"id":68603981,"url":"https://api.github.com/repos/KiCad/kicad-library/labels/enhancement","name":"enhancement","color":"84b6eb","default":true},{"id":68603983,"url":"https://api.github.com/repos/KiCad/kicad-library/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2016-11-29T09:42:20Z","updated_at":"2016-11-30T16:48:23Z","closed_at":null,"body":"Libraries should have consistent metadata added to each component, to make BOM generate easier and more consistent.\r\n\r\nApologies for not submitting a pull request, but it seems that you can't for wiki entries.\r\n\r\nThere is some discussion here: https://forum.kicad.info/t/default-manufacturers-part-number-field-in-kicad-libraries\r\n\r\nI propose adding the following to the wiki page on library conventions. This will allow BOM generation plug-ins to be much more compatible and uniform, and save users time editing metadata manually. The goal would be to have the BOM generated directly from the schematic with minimal editing afterwards, and to facilitate tools like automatic order generation at suppliers.\r\n\r\nTo this end, metadata must be consistent and predictable. Normalization is key.\r\n\r\n### 5. Symbol metadata\r\n\r\n1. Value should be ~blank~ R/C/D/etc. for passives like resistors and capacitors, or the primary differentiating factor for ICs (e.g. 32k for a 32k variant of a microcontroller).\r\n1. Add an ~\"MFP\"~ \"ManufacturerPart\" hidden field with the manufacturer's part number.\r\n1. Add an ~\"MFN\"~ \"ManufacturerName\" hidden field with the manufacturer's name.\r\n1. Add a \"fit\" hidden field, set to \"true\" for things that require parts and \"false\" for things like jumpers, solder pads, markings, edge connectors etc. that don't generate any items on the BOM.\r\n1. Add an optional \"data\" hidden field with relevant data on precision, voltages/current limits etc. Should be omitted for generic parts.\r\n1. Add an optional \"notes\" hidden field with any relevant textual notes, e.g. why pins were swapped.\r\n1. Empty fields should have a single underscore ( _ ) to prevent them being stripped out."},"comment":{"url":"https://api.github.com/repos/KiCad/kicad-library/issues/comments/263926527","html_url":"https://github.com/KiCad/kicad-library/issues/808#issuecomment-263926527","issue_url":"https://api.github.com/repos/KiCad/kicad-library/issues/808","id":263926527,"user":{"login":"jkriege2","id":11967523,"avatar_url":"https://avatars.githubusercontent.com/u/11967523?v=3","gravatar_id":"","url":"https://api.github.com/users/jkriege2","html_url":"https://github.com/jkriege2","followers_url":"https://api.github.com/users/jkriege2/followers","following_url":"https://api.github.com/users/jkriege2/following{/other_user}","gists_url":"https://api.github.com/users/jkriege2/gists{/gist_id}","starred_url":"https://api.github.com/users/jkriege2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jkriege2/subscriptions","organizations_url":"https://api.github.com/users/jkriege2/orgs","repos_url":"https://api.github.com/users/jkriege2/repos","events_url":"https://api.github.com/users/jkriege2/events{/privacy}","received_events_url":"https://api.github.com/users/jkriege2/received_events","type":"User","site_admin":false},"created_at":"2016-11-30T16:48:23Z","updated_at":"2016-11-30T16:48:23Z","body":"Hi!\r\n\r\nI'm really confused by now ... Could you please - very simply with a few easy examples, say on typical discrete like R and one more IC like 741/555/7400/... - write down what you proposal would mean! Also e.g. consider a microcontroller family such as ATmega88P and varaints (see http://www.atmel.com/images/Atmel-8271-8-bit-AVR-Microcontroller-ATmega48A-48PA-88A-88PA-168A-168PA-328-328P_datasheet_Complete.pdf).\r\n\r\nIf you say there is no need for empty fields pre-generated by KiCAD, but also say that mostly the fields should be empty in the lib, I don't see what you really want! \r\n\r\nThe KLC-page defines Standards that symbols for this lib have to (mostly) follow, in order to be accepted. So if you set up these rules, you require people to stick to them and generate those fields (as otherwise symbols without the fields won't be accepted anymore), unless you say they are strictly optional (then that should be in your proposal). Still, even if they are optional, the questions of checking and formatting (also of the different ManufacturerNames) remains, if somebody supplies the data!\r\n\r\n> For libraries, the main change would be the way the \"value\" field works, \r\nOK, I think here some examples would really help (see above)\r\n\r\n> and the way that some parts have many aliases for what are essentially different values.\r\nWhat would you propose here? A change in KiCAD, or a change how we use the current structure (no ALIASES anymore, as currently they only have the one provided functionality)?\r\n\r\nBest,\r\nJAN"}}
{"actor":{"display_login":"jkriege2"}}