New WebAnno remote API
See original GitHub issueImplement a new remote API for WebAnno with a more systematic API design and a more maintainable backend implementation.
Project
- project list - list projects
- project create - create a new project
- project read - get project information
- project delete - delete a project
- project export - export a project as a ZIP file
- project import - import a project as a ZIP file
Document
- document list - list documents in a project
- document create - import a document in a specified format
- document create parameter
state
- allow document to be created in a specified state (Allowed: NEW, ANNOTATION-IN-PROGRESS) - document read - export a document in a specified format
- document delete - delete a document from a project
Annotations
- annotations list - list which users have annotations
- annotations create - create/overwrite a users annotations by importing from a specified format
- annotations create parameter
state
- allow annotations to be created in a specified state - annotations read - export a users annotations in a specified format
- annotations delete - delete the annotation document record from the DB and the latest file. It will seem to WebAnno as if the annotation document was never created. If WebAnno is configured to maintain a backup history, this history will be retained (minus the latest file of course).
Curation
- curation create - create/overwrite a curation by importing from a specified format
- curation create parameter
state
- allow curation to be created in a specified state (actually is the document state. Allowed: CURATION-IN-PROGRESS, CURATION_FINISHED) - curation read - export a curated document in a specified format
- curation delete - delete the latest curation file. It will seem to WebAnno as if the annotation document was never created. If WebAnno is configured to maintain a backup history, this history will be retained (minus the latest file of course).
curations list- this is not necessary since a) there is only a single curation per document and b) the curation status of a document is provided in the document list call.
Misc
- allow messages in response (https://github.com/webanno/webanno/issues/455#issuecomment-283011969)
Undecided
- conflate curation with annotation API using a special username <-> having a dedicated curation API parallel to the annotation API -> decision: separate set of calls for curation
Issue Analytics
- State:
- Created 7 years ago
- Comments:39 (37 by maintainers)
Top Results From Across the Web
WebAnno Administrator Guide
Once the remote API is enabled, it becomes possible to assign the role ROLE_REMOTE to a user. Create a new user, e.g. remote-api...
Read more >WebAnno Administrator Guide
Create a new user, e.g. remote-api via the user management page and assign at least the roles ROLE_USER and ROLE_REMOTE . Most of...
Read more >Export the annotations from WebAnno via REST API
to webanno-user. This method only how's a status. /api/aero/v1/projects/{projectId}/documents/{documentId}/annotations. like following.
Read more >webanno/webanno - Gitter
@ramx you need to set the system property webanno.remote-api.enable=true when starting WebAnno. That enables a new user role "ROLE_REMOTE".
Read more >de.tudarmstadt.ukp.clarin.webanno » webanno ... - Maven Repository
Home » de.tudarmstadt.ukp.clarin.webanno » webanno-remote. WebAnno Core Remote API. WebAnno Core Remote API. License, Apache 2.0. Tags, remote.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you so much for the response. it’s working! 👍
You get access to the Swagger UI if you log in as admin (ROLE_ADMIN). But then a second login popup comes up. The user that you use there to log in must have ROLE_REMOTE. Check if your admin user does indeed have the
ROLE_REMOTE
.