ynput
Renaming folders after creation, e.g. when typo is found
Stories - what are the use cases for different personas?
Sometimes a folder gets created but gets the wrong name but user still saved - e.g. a typo.
Problems - what problems does this story create?
Suddenly now we have a few folders that are 'labeled' differently than their name (just fixing a typo) but e.g. workfiles will still include the name with the typo.
Proposal - how do we solve these problems?
Preferably there is some flexibility for any folders without any workfiles or publishes to still rename them - even after having been saved. I believe the OpenPype Ftrack integration allowed that - to rename an asset on Ftrack and sync the update to OpenPype in some cases
It's hard to define whether that should truly be allowed - since it may be hard to detect whether any work had started on a folder or not and if it has, it may be dangerous to rename the folder.
It's a problem that was sometimes tricky in OpenPype as well.
The biggest issue we had now was that artists "thought" they had fixed it (changed the right hand side name on the folder but were actually only correcting the 'label'). This may just be user training needed to avoid that in the future - or is just a side effect of human error you can't avoid?
TODO - Actionable steps to solve this
- [ ] Discuss: What can we do?
Is it acceptable human error? Can we do something to make it easier to capture such errors or correct them?
Attachments
Correct me if I'm wrong but I think we have a similar strategy for delete: front end only shows the option if there's no version inside.
The same would be acceptable for renaming/moving folders.
Dedicated ACL and confirm dialog (force flag on API route) could help too.
Correct me if I'm wrong but I think we have a similar strategy for delete: front end only shows the option if there's no version inside.
The same would be acceptable for renaming/moving folders.
Dedicated ACL and confirm dialog (force flag on API route) could help too.
As long there are no published versions, renaming is possible via API without a force flag. It is just a frontend thing (when a folder exists, it changes the label instead of name), but i like the idea of having a rename dialog.
Once there's something published, the backend blocks any attempts of renaming the folder as it would break things and i don't think there should be a way to do that.
It is just a frontend thing
I like the idea of allowing the named to be edited if there are no published versions and if there are then the field would be disabled with a tooltip of why.
FE will just need to figure out if the folder has versions or not when querying the data.
What's the deal with task names, can they be changed at anytime?
What's the deal with task names, can they be changed at anytime?
I'd treat them the same as folder. Once there is a workfile created or a publish linked to it.
However, that being said, we should probably still allow force rename even through the UI with a very obvious big red message, that if you continue you might be breaking relationships and file links in the pipeline.
