--- title: "Component libraries with DRCY" slug: "component-libraries-with-drcy" updated: 2026-10-23T20:12:12Z published: 2026-10-23T20:12:12Z canonical: "learn.allspice.io/component-libraries-with-drcy" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.allspice.io/llms.txt > Use this file to discover all available pages before exploring further. # Component libraries with DRCY DRCY analyzes schematics using constraints extracted from component datasheets. Because of this, resolving the **correct datasheet for each component** is critical for accurate review results. Most teams do not need to configure anything to get started. The following examples show the common patterns teams use when working with datasheets in DRCY. ![](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/component%20library.png) --- ## Example 1: Alice uses manufacturer part numbers Alice’s schematics already use **manufacturer part numbers (MPNs)** such as: ``` STM32F103C8T6 LM7805 TPS62172 ``` When DRCY sees a manufacturer part number, it automatically attempts to retrieve a datasheet using fallback libraries such as DigiKey. Alice can run DRCY without any additional configuration. However, Alice sometimes needs to override the default behavior. --- ### Alice uploads a preferred datasheet Sometimes distributor datasheets are not the best reference. Alice may want to: - lock a specific revision of a datasheet - use a clearer vendor document - reference an internal or NDA-restricted document She can upload a datasheet directly into the repository. #### Repository structure Datasheets must be stored in: ``` .allspice/datasheets/.pdf ``` or ``` .allspice/datasheets//.pdf ``` Example: ``` .allspice/ datasheets/ STM32F103C8T6.pdf ``` When a matching file exists, **DRCY will use it before any other source**. --- ### Alice maps a component to a datasheet stored in another repository Alice may maintain a central repository that stores approved datasheets. She can reference those documents using a CSV mapping file. Example: ``` mpn,datasheet_url TPS62172,https://example.com/datasheets/TPS62172.pdf ``` Saved as: ``` .allspice/library.csv ``` When DRCY encounters `TPS62172`, it will use the provided datasheet URL. --- ### Alice maps a component directly to a DigiKey datasheet Alice can also map a component directly to a specific datasheet URL from DigiKey. Example: ``` mpn,datasheet_url LM7805,https://www.digikey.com/en/products/detail/stmicroelectronics/L7805CV/585964 ``` This ensures a consistent datasheet is used during review. --- ## Example 2: Bob's team uses internal part numbers Bob’s team uses an **internal part numbering system (IPN)** in their schematics. Example components: ``` ACME-PWR-001 ACME-MCU-004 ACME-ESD-002 ``` Because these identifiers are not globally recognized, Bob needs to map them to manufacturer part numbers or datasheets. He does this using a CSV file. --- ### Bob maps IPNs to manufacturer part numbers Example CSV: ``` ipn,mpn ACME-PWR-001,LM7805 ACME-MCU-004,STM32F103C8T6 ACME-ESD-002,PESD5V0L1BA ``` Saved as: ``` .allspice/library.csv ``` When DRCY reviews the schematic: ``` IPN → MPN → DigiKey datasheet ``` This allows Bob’s team to keep internal part numbers in schematics while still resolving datasheets automatically. --- ### Bob uploads a preferred datasheet Bob can also override datasheets the same way Alice does. Example: ``` .allspice/ datasheets/ LM7805/ ACME-PWR-001.pdf ``` or ``` .allspice/ datasheets/ LM7805.pdf ``` Repository datasheets always take precedence over CSV mappings and fallback libraries. --- ### Bob maps an IPN directly to a datasheet URL If a component has no public manufacturer part number, Bob can map it directly to a datasheet. Example: ``` ipn,datasheet_url ACME-ESD-002,https://internal.example.com/datasheets/acme-esd.pdf ``` --- ## Datasheet resolution order When reviewing a design, DRCY resolves datasheets using the following order: 1. **Datasheets uploaded into the repository** ``` .allspice/datasheets/ ``` 2. **CSV mappings** ``` .allspice/library.csv ``` 3. **Fallback libraries** Typically DigiKey, when an MPN is available. Once a valid datasheet is found, DRCY stops searching. --- ## Datasheet repository requirements DRCY currently supports: - **PDF files only** - **One datasheet per component** If multiple PDFs exist for the same component, **only the first discovered file will be used**. Valid locations include: ``` .allspice/datasheets/.pdf ``` or ``` .allspice/datasheets//.pdf ``` --- ## Datasheet accuracy DRCY extracts electrical constraints from datasheets, including: - voltage limits - pin functions - regulator behavior - interface requirements If the wrong datasheet is used, analysis results may be incorrect. DRCY may attempt to detect when a datasheet appears to describe a different component, but this detection is **best effort only** and should not be relied on as a guarantee. Engineers should verify that the correct datasheet is associated with each component. --- ## Quick decision guide | Situation | Recommended approach | | --- | --- | | Schematics use manufacturer part numbers | No configuration required | | Schematics use internal part numbers | CSV mapping | | Preferred datasheet required | Upload to repository | | Internal or NDA components | CSV + repository datasheet | | Air-gapped environments | CSV with internal datasheets |