Replies: 3 comments 1 reply
-
Hi, currently there is no API endpoint for this. Could you please explain your exact use case? I'd welcome the implementation of such an endpoint for a single volume if this would also work for you. It could be used to improve the suggestions for the "filter files by annotations of a user" filter in the volume overview. Some hints:
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply. The use case is a system that imports annotations from a video annotation CSV report into another database. Prior to the actual import, the operator uses a Web application to (among other things) map the users associated with annotations to users already in the database. The actual mapping happens (mostly) automatically, but since it occurs prior to generation of the report, it must consume a user list from the projects endpoint, which in my case does not have a complete list of the users associated with annotations in the report. I don't want to generate a report as part of this process because it would disrupt a clean(ish), linear workflow. As far as I can tell, there isn't presently a way to get a user list for all of the annotations under a project without publishing the report. So I guess a prior question should be, should I even expect to be able to get a complete listing of users represented in the annotation report from a project or volume user list? If it's possible for a user to be removed from a project without deleting their annotations under that project, there would need to be another way to get a complete list. |
Beta Was this translation helpful? Give feedback.
-
Is there a way to get a list (via the ReST API) of the users who have applied annotations under a project. In my specific example, if I generate a video annotation report (CSV), there are users in the report that are not listed under the project itself. (This could be a permissions restriction on my end, etc.)
If possible, I would like to do this without exporting the annotations, scraping the user IDs and getting the information user-by-user.
If this isn't currently possible, I'd be happy to investigate an implementation.
Beta Was this translation helpful? Give feedback.
All reactions