Currently, when users save Q&A content from a Project to the Content Library using the "Save in Library" function, mandatory Content Library fields are not enforced at the time of saving. Validation only occurs later during the Moderation process. For organizations that do not use Moderation, or for those that prefer content owners and SMEs to classify content during the Project phase, this results in incomplete metadata being saved to the library and creates additional manual work.
This enhancement would introduce validation of mandatory Content Library fields during the "Save in Library" workflow, ensuring that all required metadata is captured before content is added to the library.
Business Impact
- Improves data quality and consistency within the Content Library.
- Reduces manual effort required to update metadata after content has been saved.
- Supports organizations that do not use Moderation workflows.
- Encourages content owners and SMEs to classify content at the source rather than relying on moderators.
- Increases efficiency and adoption of the "Save in Library" workflow.
Use Cases
Use Case 1: Organizations Without Moderation
A customer has Moderation disabled and uses "Save in Library" directly from Projects. When content is saved, mandatory fields such as Language, Owner, Collection, and custom metadata fields remain blank. The enhancement would require users to complete these fields before the content is saved.
Use Case 2: Reducing Moderator Workload
A customer uses Moderation but wants content owners to classify and tag content during proposal creation. By enforcing mandatory fields during "Save in Library," moderators no longer need to manually populate missing metadata before approving content.
Use Case 3: Ensuring Metadata Compliance
Organizations with strict content governance requirements need all library content to be categorized consistently. Enforcing mandatory fields at the time of saving ensures that no content enters the library without required metadata.
Use Case 4: Custom Mandatory Fields
Customers frequently create custom fields (e.g., Business Unit, Region, Product Line, Section Classification) and mark them as mandatory. The system should honor these requirements during the "Save in Library" process and prevent saving until all required fields are completed.
Expected Behavior
When a user selects "Save in Library" from a Project:
- The system identifies all mandatory Content Library fields.
- A prompt or form is displayed requesting values for any required fields that are not populated.
- The content cannot be saved until all mandatory fields are completed.
- Once validated, the content is successfully added to the Content Library with complete metadata.
