This is really helpful context, thank you! The ability to un-archive and keep tags as keywords I can see be very useful. I'm going to move this to Future Consideration for now, and the next time we tackle Tags API related work, this will be considered. Thank you again!
A deleted tag would no longer appear anywhere. It wouldn't appear in Global Settings or any lists. If it was added to a story before it was deleted, it would just be a keyword in the ANS, it wouldn't be attached to anything.
An archived tag would be hidden or set off to the side in the Tag List in Global Settings. It would not pop up as an option to be selected in Composer or elsewhere. If someone manually types in the exact tag as it existed before it was archived, it would be added as a keyword in the ANS but would not add that story to the topic page. The topic page would continue to exist but not accept new updates. If you want to make updates to the tag or the topic page, you would have to un-archive the tag to return it to active use.
I guess more what I'm wondering is what is the desired difference in behavior between Deleting a Tag and Archiving a Tag. How would an archived Super Bowl Tag behave differently from a deleted one? I want to make sure we don't just implement a second Delete endpoint, and that the desired difference between the two is captured. Thank you!
Hi Jessica! The Tags API provides a delete functionality as is. Is there a specific use case where you'd want to archive instead of delete, and can you provide more detail around why that is? Thanks!
Jessica Parks
This is really helpful context, thank you! The ability to un-archive and keep tags as keywords I can see be very useful. I'm going to move this to Future Consideration for now, and the next time we tackle Tags API related work, this will be considered. Thank you again!
A deleted tag would no longer appear anywhere. It wouldn't appear in Global Settings or any lists. If it was added to a story before it was deleted, it would just be a keyword in the ANS, it wouldn't be attached to anything.
An archived tag would be hidden or set off to the side in the Tag List in Global Settings. It would not pop up as an option to be selected in Composer or elsewhere. If someone manually types in the exact tag as it existed before it was archived, it would be added as a keyword in the ANS but would not add that story to the topic page. The topic page would continue to exist but not accept new updates. If you want to make updates to the tag or the topic page, you would have to un-archive the tag to return it to active use.
I guess more what I'm wondering is what is the desired difference in behavior between Deleting a Tag and Archiving a Tag. How would an archived Super Bowl Tag behave differently from a deleted one? I want to make sure we don't just implement a second Delete endpoint, and that the desired difference between the two is captured. Thank you!
My answer above lists multiple examples where we would want to archive instead of delete.
Hi Jessica! The Tags API provides a delete functionality as is. Is there a specific use case where you'd want to archive instead of delete, and can you provide more detail around why that is? Thanks!
Answering from question here: https://ideas.arcpublishing.com/ideas/ACS-I-73?utm_source=idea_comment_mailer&utm_medium=email&utm_campaign=subscribers
Old, inactive tags might include
- temporary topics that have ended (i.e. Super Bowl XLI)
- tags that were carried over as part of Arc onboarding/content migration and are not needed anymore
- tags that were experimental or analytics