Skip to content

Library ID ​

The Library ID (Global Unique Identifier, or GUID) is the core logical identifier used by Sharp Stock to precisely distinguish and track different asset libraries.

1. Definition & Generation Mechanism ​

When you create a brand new asset library or load an external directory as a library for the first time, the system automatically generates a unique code consisting of random characters (e.g., f8a1...).

This identifier is persistently stored in the underlying configuration table of the library database (assetlib.db). You can think of it as the "digital ID card" of the asset library.

2. Core Purposes ​

  • Multi-Terminal Sync Verification: In team collaboration scenarios where multiple members share the same resource library via SVN, the ID ensures that all software clients accurately identify it as the same logical repository, enabling seamless synchronization of settings and metadata.
  • Physical Path Decoupling: The logical identification of the library is completely separate from its physical storage location on the local hard drive. Even if you move the library folder on the disk, the system can still retrieve all historical configurations for that library upon reloading, as long as the ID remains unchanged.
  • Secure Link Navigation: When performing resource jumps via Asset Links, the system prioritizes verifying the ID. A jump is only executed if the ID pointed to by the link matches the currently opened library, preventing resource pointer errors across similar projects.

3. How to View & Extract ​

Go to the [Settings] → [Library Status] panel. Below the current library path, the system will display the full ID code of the asset library. Click the "Copy" icon to the right to save it to your clipboard.


IMPORTANT

Prohibited Operations: Please do not attempt to manually modify the lib_guid field in the database via external tools. Illegal ID tampering will cause the asset library to go unrecognized on other team members' computers and may even trigger serious metadata synchronization failures.