This document applies to FastGPT v4.17.0
What data for this category looks like
Image annotation project data primarily comes from image samples produced by annotation platforms, annotated bounding box and category label data, category dictionaries supporting the project, and result records for sampling inspections and rework. Daily synced documents include annotation specification documents, bounding box reference examples, batch quality inspection reports, and rework task lists. Data updates follow a cycle of daily or single-batch annotation tasks. Each task includes fields such as image path, bounding box coordinates, annotator ID, and quality inspection status. There are no unified fixed units, and values adjust based on annotation categories and project requirements.
What constraints these characteristics impose on the "sharing and embedding" workflow
Image annotation project data includes visual elements such as image samples and bounding box coordinates. When sharing and embedding into an on-call operations or ticket system, it is necessary to adapt to resource loading rules for different scenarios, and prevent visual elements from failing to display due to cross-domain restrictions. Data updates follow a daily or single-batch cycle. Knowledge base content referenced by shared links is processed and updated by the corresponding knowledge base system. Associated knowledge bases must have on-demand synchronization rules configured to avoid operations personnel using outdated reference materials. Fields involved in the project include non-text coordinate information. Embedded internal system pages must support rendering logic for multiple data types, and adapt to permission control rules of internal systems to ensure only authorized personnel can access sensitive annotation-related data.
How to set configurations
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
Sharing entry shareId | Copy the complete sharing link generated by the system; do not manually replace the identifier | Identifies the sharing entry; business records and data permissions for image annotation projects must still be handled by external systems |
| Sharing link validity period | Test starting point: 7 days; adjust based on actual testing of the collaboration cycle and revocation requirements for image annotation projects | Verify availability within the validity period and access behavior after expiration; this value is not an official default or industry statistic |
| QPM | Test starting point: 20 requests per user per minute; adjust based on actual load | Limits the access frequency of a single user; verification is required combined with request logs and actual load |
| Identity verification | When identity permission requirements exist, first verify commercial edition capabilities and the uid returned by the third-party identity service | Holding a sharing link does not equate to having business data permissions; third-party identity and data scope must be verified separately |
| Referenced content display | Select display configurations for referenced fragments, full text, and original text based on the sensitivity of image annotation project materials | Check displayed content within authorized data ranges; do not use hidden interfaces as a substitute for data permission control |
| Conversation record verification | Test example: Prepare 10 Q&A samples for image annotation projects, and check them in the same browser and another device respectively | Anonymous records rely on browser local identity; retention cannot be guaranteed across devices or after cache clearance |
Three common mistakes
- Sharing entries related to image annotation projects fail to open. First verify the complete system-generated link and its validity period, then check browser request statuses; do not manually replace
shareId. - The visible scope of image annotation project data does not match expectations. Verify third-party identity verification results, workflow request parameters, and data permissions of external systems separately; the sharing entry identifier itself does not provide business authorization.
- The same image annotation project Q&A is not visible on another device. For anonymous scenarios, first check device, browser, and local identity status; record retention cannot be guaranteed across devices or after cache clearance, and service abnormalities cannot be judged solely based on this phenomenon.
How to confirm the configuration is complete
- Access the generated sharing link, confirm that the Q&A interface can be entered without logging in, and verify that the no-login configuration takes effect.
- Embed the sharing page into an internal operations system, test loading documents such as annotation specifications and bounding box reference examples, confirm that resources display normally, and verify that cross-domain configurations are correct.
- Initiate a Q&A about the annotation rework process, close the browser, and revisit the sharing link to confirm that session records can still be queried; repeat this operation on the same device and same browser, close the browser, and revisit the link to confirm that previous Q&A records can be retrieved, and verify that the anonymous local session storage logic takes effect.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.