Successfully exported 0 annotations of annotator [email protected] to ./output/.

[SAIVENKATARAJU]

Hi
I was trying to export the annotations which are so far completed using the below command. here is my file structure is attaching can you please help me with this. I have used [email protected]_annotations.json, [email protected] both the file names in place of markn. but no luck.
pawls export <labeling_folder> <labeling_config> <output_path> <format> -u markn

[codeviking]

It looks like this might be because of a typo? The command in your screenshot is trying to export annotations for [email protected], the t on development is missing.

[SAIVENKATARAJU]

Hi
Thanks for your quick response. I will check that. But my doubt is what should we use here in the command instead of markn. Is it [email protected] or [email protected]_anotations.json file

[codeviking]

It's the name of the user. So you shouldn't include the .json suffix, that's the filename.

So I'd try [email protected]. The code (I think) adds the .json suffix for you. If that doesn't work, you could try development_user too (by omitting the email host).

I'm not familiar with the specifics of that code, but can take a look if none of these alternatives do the trick.

[SAIVENKATARAJU]

HI @codeviking ,
Unfortunately, None of the ways are worked. I use [email protected] and with out email host. I evan copy the files like _annotation.json, status/development_user.json to ./cli/skiff_files/apps/pawls/papers/( when we are annotating actual values are appending to /skiff_files/apps/pawls/papers/ outside of CLI like above and even user_annotation.json also creating here)

[SAIVENKATARAJU]

I am attaching [email protected]. json content here.I think its hsowing I have done 89 annotations.
{"e4e006fa27de79ff20b31011c3a57e8397a99bb06fdb518a3320a7096cc52bb8": {"sha": "e4e006fa27de79ff20b31011c3a57e8397a99bb06fdb518a3320a7096cc52bb8", "name": "e4e006fa27de79ff20b31011c3a57e8397a99bb06fdb518a3320a7096cc52bb8", "annotations": 89, "relations": 0, "finished": false, "junk": false, "comments": "", "completedAt": null}}

[codeviking]

I wouldn't suggest manipulating the filesystem manually. It's possible the manual manipulations somehow caused the filesystem structure to differ from what the command expects, and that's the issue.

Could you try omitting the user entirely (just remove the -u argument)? That'll export annotations for all users, and confirm whether the issue has to do with the username or not.

Also, it looks like your annotations aren't finished. Maybe you need to add the --include-unfinished flag. Can you try that too?

[SAIVENKATARAJU]

it worked with out user and including **--include-unfinished ** flag. but strange it detect only one annotations.

[codeviking]

I suspect that might have to do with the local modifications you've made to the file tree. I'm not sure if we'll be able to provide much more help, sorry!