Libraries
Why Versioned Symbol and Component Libraries Matter in Electrical Design
Shared libraries need to improve over time, but an approved correction for tomorrow's work should not silently redraw projects that were created yesterday.
A reusable symbol or component can appear in hundreds of project pages. That scale is the value of a shared library—and the reason an uncontrolled edit can have consequences far beyond the library record being changed.
01 · The hidden reach of an edit
A small library correction can become a large project change.
A symbol may need a corrected pin label, revised geometry or improved search classification. A component may need a new manufacturer reference, rating or mapped physical representation. These are reasonable updates, but replacing the existing definition in place can change what an older drawing displays or how its connections resolve.
The risk is especially serious when graphical pins are also electrical connection points. Moving, renaming or removing a pin can alter wires, reports and terminal relationships even when the page still appears visually similar.
02 · Identity is not a revision number
Separate what the resource is from which version was published.
A stable resource identity lets the system recognize that several publications belong to the same symbol or component. A version identifies one exact published definition. Together they answer two different questions: “Which reusable resource is this?” and “Which approved state of that resource does this project use?”
The resource remains recognizable across revisions and references.
A published version does not silently change after projects depend on it.
A placed project object records the exact library version it requires.
A new version can improve the resource without rewriting earlier drawings.
Human-readable names and categories remain important for discovery, but they should not be the only reference. Names can be corrected, and a resource can move between categories without becoming a different engineering definition.
03 · Reproducible drawings
Projects should retain the exact library version they placed.
When a designer places a published symbol, the project should store both the stable library identity and the selected version. Loading the drawing can then resolve that exact definition rather than whatever happens to be newest at the time.
Library edits can unexpectedly alter old drawings, connections and generated reports.
New projects can use improvements while existing drawings remain reproducible.
Moving an existing project to a newer version should be an explicit migration with a visible comparison and validation step. Automatic replacement is only safe when compatibility rules are well defined and the organization has accepted the change.
04 · More than one library
Components connect commercial data with graphical resources.
A component record can describe a real product and reference the symbol used in a schematic, the geometry used in a panel layout and other reusable definitions. Those relationships should point to explicit published resources rather than duplicating their geometry or relying on a name that may later change.
- Symbols: graphical and electrical definitions, including pins and default engineering behavior.
- Components: manufacturer, part number, ratings, descriptive properties and mapped resources.
- Geometry: reusable physical representation for layout or enclosure work.
- Macros: assemblies that depend on exact symbol versions and project placement rules.
Versioning each dependency makes the assembly understandable. If a macro refers to an exact symbol publication, the platform can load what the macro was reviewed with instead of substituting a later incompatible definition.
05 · Publishing discipline
A versioning model still needs ownership and review.
Draft changes should be tested before publication. Reviewers need to inspect geometry, pin behavior, metadata, search fields and dependent resources. Once published, a version should remain immutable; another correction creates another version.
- Document why the new version is required and what changed.
- Test placement, connections, rendering and report behavior.
- Identify whether the change is compatible with prior project data.
- Keep old versions available while active projects still reference them.
- Retire a version from new selection without deleting its historical definition.
A resource that should no longer be selected for new work may still be essential for opening, reviewing and exporting existing projects.
06 · The ElecDraw model
How ElecDraw keeps reusable resources and drawings connected.
ElecDraw publishes reusable library definitions with stable identities and versions. Project symbols retain the version they require, while the editor loads referenced definitions when they are needed instead of replacing every project reference with the newest library state.
Component records can map product information to published symbols and geometry. Reusable macros retain their exact symbol dependencies so placement can create fresh project objects from known library content. Search and menu organization help users discover resources, while the published definition remains the engineering source used by the drawing.
Versioning protects traceability; it does not prove that a library item is correct for a particular application. Organizations must review symbols, component ratings, manufacturer data, safety implications and applicable standards before approving or using reusable content.
