You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
POST /projects/{project_id}/tags
GET /projects/{project_id}/tags/{tag_id}
PUT /projects/{project_id}/tags/{tag_id}
PATCH /projects/{project_id}/tags/{tag_id}
DELETE /projects/{project_id}/tags/{tag_id}
Usecases & Scenarios:
We want to integrate doccano with our interval jobs/services. As providing an automated platform, we want annotators explicitly mark a project as 'completed', so that certain downstream jobs can be triggered.
As we serving doccano for multiple internal teams, we also want to attach business-related information to the project, like model names, stakeholder teams, etc.
The text was updated successfully, but these errors were encountered:
Hi,
As title described. I think this feature will be helpful when:
Here are my thoughts:
UI:
DB Models:
add one more table
api_tag
, with following columns:APIs:
GET /projects/{project_id}/tags
response body may look like:
POST /projects/{project_id}/tags
GET /projects/{project_id}/tags/{tag_id}
PUT /projects/{project_id}/tags/{tag_id}
PATCH /projects/{project_id}/tags/{tag_id}
DELETE /projects/{project_id}/tags/{tag_id}
Usecases & Scenarios:
We want to integrate doccano with our interval jobs/services. As providing an automated platform, we want annotators explicitly mark a project as 'completed', so that certain downstream jobs can be triggered.
As we serving doccano for multiple internal teams, we also want to attach business-related information to the project, like model names, stakeholder teams, etc.
The text was updated successfully, but these errors were encountered: