nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bulk taxonomy/tag updates within archived content

vishal

Invesco requested this

No ability to bulk-edit taxonomy or custom fields on archived records — must unarchive, edit in the live library, then re-archive. Painful at ~30k archived records, especially as org strategy/team names change frequently

Find more posts tagged with

Future consideration

Organization Settings

Content Library

Status: Future consideration

Comments

sathish s

@vishal I understand that the customer request is to update metadata of Q&A pairs in archive queue. Right now they have to unarchive, update and then archive again. But I would like to know the business need for updating metadata of archived content. Can you give more insights on this?

sally

Hello Sathish, from my experience of interviewing customers with heavy DDQ use cases (like Invesco), they refer frequently to their archive to base their new answers off of. The reason is that they want to make sure to stay consistent in their answer and use approved language only. My educated guess of their use case of updating meta data in bulk in archive collections is to better enable search for new DDQ completion especially when their volumes are high, which makes it a critical step of their workflow and not just for maintenance purpose.

@sathish s How big of a lift that we think this improvement could be?

@vishal How does this resonate with your observations?

CC @Natalie Berigan

vishal

@sathish s @Natalie Berigan @Sally Xia

Here's why Invesco needs the ability to update tagging/metadata on archived content

Their taxonomy changes frequently. Team groupings and strategy names shift regularly because of the regulatory environment they operate in ("why is it changing so much... we need to be compliant with that... need to go in lockstep with those changes").
Org settings won't let them delete or rename a field if it's still linked to archived content. When they try to remove or rename something in organization settings (e.g., an old strategy name), they can't, because legacy content in Archive is still tied to that field.
Archive itself has no bulk-edit capability. Unlike the live content library, where they can select content and apply bulk changes to tags/fields, Archive only allows adding a tag. There's no way to remove or update fields directly within Archive.
Archive is meant to function as a reference/backup layer, not appear in active AI responses. They want older content preserved and accessible when specifically needed (e.g., pulling an old RFP response), but kept separate from the main library so it doesn't surface in general AI-driven answers.

sathish s

@vishal Is the expectation is to update any field from archive queue or they have specific field(s) to be updated from archive queue?

vishal

@sathish s , Per the client" we would like to have access to all fields for this option. However, if prioritizing is helpful for faster development, Investment Team, Strategy, Main Topic, Subtopic and Tags would be our preferences"

sathish s

@vishal Okay. @Logapriya Shanmugasundaram How big is the effort to provide edit and save option for a Q&A pair when it is in archive queue?

sathish s

https://rfpioinc.atlassian.net/browse/RES-185184

sathish s

@vishal It is not possible to provide edit option for all the fields mentioned as those are custom fields. Can we prioritize tags as of now? Kindly confirm.