vault backup: 2026-02-26 22:57:07
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
tags:
|
||||
- eventkit
|
||||
---
|
||||
|
||||
# Barcode & QR Scanning
|
||||
|
||||
## Purpose
|
||||
@@ -20,6 +21,17 @@ Enable fast, accurate equipment tracking through QR code scanning. Every [[01 -
|
||||
| **Kit / Set** | QR Code (optional) | URL → `https://{instance}/kit/{id}` | Kit card / bag tag |
|
||||
| **Consumable** | Barcode (EAN/UPC) | Product ID or manufacturer barcode | Existing packaging or custom label |
|
||||
|
||||
### Legacy Barcode Support
|
||||
|
||||
Companies migrating to EventKit may already have existing barcode/label schemes. EventKit supports **dual scanning** — both legacy barcodes and new QR codes are recognised:
|
||||
|
||||
| Feature | Description |
|
||||
| ---------------------- | ---------------------------------------------------------------------------- |
|
||||
| Legacy barcode import | Import existing barcode-to-asset mappings during onboarding |
|
||||
| Dual scanning | Scan either a legacy barcode or an EventKit QR code — both resolve the asset |
|
||||
| Gradual migration | No need to re-label everything at once; legacy barcodes remain valid |
|
||||
| Barcode format support | Code 128, Code 39, EAN-13, UPC-A, QR — any standard 1D/2D format |
|
||||
|
||||
---
|
||||
|
||||
## QR Code Design
|
||||
@@ -34,13 +46,13 @@ https://inventory.company-a.com/asset/550e8400-e29b-41d4-a716-446655440000
|
||||
|
||||
### Why URLs?
|
||||
|
||||
| Benefit | Description |
|
||||
| ----------------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------ |
|
||||
| **Universal** | Any phone camera can scan it and open the asset page in a browser |
|
||||
| **Federation-friendly** | The domain tells any EventKit instance who owns the asset (see [[04 - Federation Architecture#Global Asset Identity | Global Asset Identity]]) |
|
||||
| **App-aware** | A dedicated EventKit app can intercept the URL and handle it natively |
|
||||
| **Offline-capable** | The app can extract the UUID locally and sync the action later |
|
||||
| **Future-proof** | No proprietary encoding — standard URLs work forever |
|
||||
| Benefit | Description |
|
||||
| ----------------------- | --------------------------------------------------------------------- |
|
||||
| **Universal** | Any phone camera can scan it and open the asset page in a browser |
|
||||
| **Federation-friendly** | The domain tells any EventKit instance who owns the asset |
|
||||
| **App-aware** | A dedicated EventKit app can intercept the URL and handle it natively |
|
||||
| **Offline-capable** | The app can extract the UUID locally and sync the action later |
|
||||
| **Future-proof** | No proprietary encoding — standard URLs work forever |
|
||||
|
||||
### Label Design
|
||||
|
||||
@@ -106,13 +118,13 @@ sequenceDiagram
|
||||
participant App as EventKit App
|
||||
participant API as API Server
|
||||
|
||||
User->>App: Open [[02 - Planning Module#Pull Lists / Equipment Planning|Event Pull List]]
|
||||
User->>App: Open Event Pull List
|
||||
App-->>User: Show items to dispatch
|
||||
|
||||
loop For each item/case
|
||||
User->>App: Scan QR code
|
||||
App->>API: POST /scan/checkout {asset_uuid, event_id}
|
||||
API-->>App: ✅ Asset status → "[[01 - Inventory Management#Asset Lifecycle & Statuses|Checked Out]]"
|
||||
API-->>App: ✅ Asset status → "Checked Out"
|
||||
App-->>User: ✅ Item confirmed on list
|
||||
end
|
||||
|
||||
@@ -192,7 +204,7 @@ sequenceDiagram
|
||||
participant A_API as Company A API
|
||||
|
||||
User->>B_App: Scan QR code on received item
|
||||
Note over B_App: URL domain = company-a.com → [[04 - Federation Architecture|federated asset]]
|
||||
Note over B_App: URL domain = company-a.com → federated asset
|
||||
B_App->>B_API: POST /scan/subhire-receive {url, condition}
|
||||
B_API->>A_API: GET /federation/asset/{uuid}
|
||||
A_API-->>B_API: Asset details (Shure SM58, SN: 00142)
|
||||
|
||||
Reference in New Issue
Block a user