Library and Revisions¶
Goal¶
Help you turn loose source files into library documents that can be reopened, extended with new revisions, and shared.
Supported Platforms¶
iOSmacOS
Intended Audience¶
- Users organizing imported boards into a reusable library
- Testers validating document, revision, and share behavior
Prerequisites¶
- The app is already open on the library home page
- At least one document is available, or source files are ready to import
Steps¶
- Review the document list in grid or list mode and open the action menu for a target document.
- Use the document-level actions to inspect metadata, append revisions, duplicate, pin, or share as needed.
- Reopen the document after changes and confirm that revision and metadata updates are reflected in the library.
Result¶
- Documents remain organized as reusable project entries, and revisions can be maintained without creating unnecessary top-level duplicates.
What the Library Home Page Can Do¶
- switch between grid and list layouts
- import new design or manufacturing documents
- enter batch selection and batch deletion
- view each document’s thumbnail, format, last-opened time, and revision count
- rename, duplicate, pin, delete, share, or inspect a single document
Relationship Between Documents and Revisions¶
- Document: one project entry in the library
- Revision: a historical version under that document
- Current revision: the revision currently opened, displayed, and exported
When you append a revision, the app does not create a separate top-level card. Instead, the card’s revisionCount increases, and you can switch the current revision within the document.
Key Actions in the Document Menu¶
From each document card menu, you can:
- append a design revision
- append a manufacturing revision
- import SES
- rename
- duplicate
- view information
- share
- pin / unpin
- delete
Special Rules for SES¶
SES is not a general-purpose new-document import path. The current implementation requires you to:
- open the target document’s action menu
- choose
Import SES - choose a usable base revision from the list
If that document has no eligible base revision, the app shows a status message instead of failing silently.
What the Information Sheet Shows¶
When you click Information, you can inspect:
- document name
- file type
- import time
- last-opened time
- current revision ID
- total revision count
- full revision list
All of this is copyable for testing notes and issue reproduction.
Recommendations¶
- For ongoing evolution of the same project, prefer append revision.
- If you want to preserve an experimental branch, use duplicate to create a separate document.
- Pin important documents to reduce the risk of accidental deletion or mis-selection.
- After import completes, open the current revision once to confirm the content, thumbnail, and last-opened time were updated correctly.
Common Questions¶
Why does one document contain multiple revisions?¶
Because the current library model is designed around continuous project evolution. Multiple revisions let you track change history within a single project context.
If I open another document while import is still running, will the newly imported document steal focus later?¶
No. Import continues and completes, but it does not force the UI back to the newly imported document.
Does sharing send the whole document package?¶
The library share action prepares a share item from the current document’s shareable root path. For grouped or directory-based sources, the shared result is based on that source root rather than a text summary alone.
Last Verified¶
2026-04-17