Being able to delete a subcategory
**I open this feature request following ticket 8189 and conversation with Dave Arsene**
I would like to be able to delete a subcategory.
Reason why? "My" library was created in mid 2015, when the AODocs possibilities were different from today and also our needs have changed since then (workflow implemented, new metadata, etc.) and I want to improve the end user experience with searches, so improve the quality of the metadata.
Today, some of the subcategories shouldn't be used anymore (I have remove them from all documents, versions ongoing), but as I can't delete the subcategories in the admin console as they are used in previous version (that I can't edit) and then, as I can't delete them, users can still choose them whereas they are not applicable anymore.
I understand that if there are used in previous versions, it can be a shame to "loose" the information of "the past" (in some cases, not in mine).
Few ideas to improve (I don't know what is technically possible):
- As we can't do searches on previous versions, why the (meta)data used in a version (which is going to be replaced by a new version) become "text" at that moment and not considered as a subcategory anymore. It's like for example, for the field "person", we today encode email of people who are working for the company, but if they leave, the data is still there even if the email is not active anymore.
- Why there is a button "delete" on subcategory, if not possible to delete?
- Have an option in the bulk updater to also update/clean metadata of the previous versions in order to unblock the deletion of a subcategory, if "cleaned", we could maybe delete it.
- Or to keep all subcategories as they are, but to have an option to do not display them anymore in the library itself (except in the admin console), in order that nobody can choose them and that from an end user point of view, this subcategory doesn't exist anymore.
If you have any questions, please don't hesitate to contact me, or see with Dave, as I explained him already the issue.