How gs1/gs1_digitallink_resolver_ce works
GS1 Resolver CE maps GS1 Digital Link identifiers to contextually appropriate web resources. Consumers request a product link or linkset; the web service interprets the identifier, retrieves stored link data, negotiates link type, language, context and media type, then redirects or returns linkset data. Operators use a separate data-entry API to create, merge, delete and batch-manage those records. The README documents the proxy and single document database; source excerpts are partial, so some internal service wiring is represented only where supported.
Main entry points: web_namespace.py Resolver routes · web_logic.py Resolution logic · nginx.conf Frontend proxy · data_entry_namespace.py Entry routes
Components 17
Data entry
- Entry API app
data_entry_server/src/__init__.py - Entry routes
data_entry_server/src/data_entry_namespace.py - Entry operations
data_entry_server/src/data_entry_logic.py - Request models
data_entry_server/src/models/request_models.py - Entry database access
data_entry_server/src/data_entry_db.py - GS1 link toolkit
data_entry_server/src/gs1-digitallink-toolkit/GS1DigitalLinkToolkit.js
Resolution
- Resolver app
web_server/src/__init__.py - Resolver routes
web_server/src/web_namespace.py - Resolution logic
web_server/src/web_logic.py - GS1 link toolkit
web_server/src/gs1-digitallink-toolkit/GS1DigitalLinkToolkit.js - GS1 syntax encoder
web_server/src/gs1-digitallink-toolkit/gs1encoder.mjs - Resolver description
web_server/src/public/gs1resolver.json
Document storage
- Resolver database access
web_server/src/web_db.py - Document database
Edge routing
- Frontend proxy
frontend_proxy_server/nginx.conf
Other components
- Consumer
- Data operator
Connections 20
- Data operator → Frontend proxy: submits records
- Frontend proxy → Entry API app: routes entry requests
- Data operator → Entry API app: manages records
- Entry API app → Entry routes: serves API
- Entry routes → Request models: validates payloads
- Entry routes → Entry operations: dispatches operations
- Entry operations → Entry database access: reads and writes
- Entry database access → Document database: accesses documents
- Consumer → Frontend proxy: requests identifier
- Frontend proxy → Resolver app: routes resolver requests
- Consumer → Resolver app: requests resource
- Resolver app → Resolver routes: serves routes
- Resolver routes → Resolution logic: processes resolution
- Resolver routes → Resolver description: serves description
- Resolution logic → Resolver database access: looks up links
- Resolver database access → Document database: reads documents
- Resolution logic → GS1 link toolkit: handles link syntax
- Resolution logic → GS1 syntax encoder: compresses identifiers
- GS1 syntax encoder → GS1 link toolkit: uses toolkit
- Resolver routes → Consumer: redirects or returns linkset