Unble to edit Attribute name

[phjae]

My actions before raising this issue

• Read/searched the docs
• Searched past issues

Steps to Reproduce (for bugs)

1. Create Project
2. Make label that has couple attributes
3. Annotate
4. Edit attribute on project page

Expected Behaviour

It should be possible to change attribute name

Current Behaviour

Unable to change attirubte name after i created

Possible Solution

can add new attribute however, it's not possible to delete attribute either

Context

when doing project, customers want to change attribute name on the middle of or at the end of the project.
it's pain to annotate all again just for the change of attribute name

Is there any reason why cvat disabled attribute edit box?

thanks so much for your help!

[zhiltsov-max]

Hi, there is no such option yet. As a workaround, you can export a backup, rename the attribute in the downloaded files, then recreate the project from the backup.

[ritikraj26]

Hello @bsekachev
I would like to take up this issue

[ScriptShah]

hi , i would like to contribute please assign me .

[ritikraj26]

So currently we don't have the endpoint for deleting an attribute?

[zhiltsov-max]

Hi, I think, currently the attribute changes require all the attributes to be sent in the request. You can find tests here. Skeleton labels can also only be sent as a full list, specific sublabels cannot be changed separately. There are 2 ways to update labels now, one it changing a specific label via /api/labels, and another one is by sending the new list of labels in /api/{projects|tasks}/<id> endpoints. The implementation for these endpoints is located here.

[ritikraj26]

Yes, currently all the attributes are sent in the request. Currently updating an attribute name is creating a new one and not updating the previous one. That might have something to do with the serialization. Thanks for providing the reference.

[ritikraj26]

Currently, the attribute name is being used as the primary key, so when I am trying to send the updated list of attributes with the new names, a new attribute is being created instead of updating.
Possible fix:
1)Adding a primary key field in the AttributeSpec table
2)Sending both the old name and the new name of the attribute in the request

[nmanovic]

@ritikraj26 ,

the attribute name is being used as the primary key

Could you please explain why you think so? Please post a link on the code in the GitHub repo.

[ritikraj26]

@nmanovic ,
Let's say an attribute's name is updated in the front-end and the updated list of attributes is being passed in the request. Now to locate the same attribute in the database we will require the previous name as it is the primary key. However, we will receive the updated name which is not present in the database, and hence a new attribute will be created instead of updating the previous one.
Please find the reference here

[nmanovic]

@ritikraj26 , an attribute's name isn't a primary key. You reference a correct piece of code, but it doesn't support the "updating an attribute" case. It should be fixed. Try to propose the best way to fix the issue. Just prepare a PR and we will review it.

[ritikraj26]

@nmanovic
Raised the PR here