Curating Knowledge Sources and Governance Overlap

Curating What's in Scope

Good knowledge management is an active, ongoing task, not a one-time upload event:

• Add the sources that actually matter to the work at hand
• Keep them organized so it's clear what's current
• Remove or update stale material rather than letting it accumulate alongside newer versions

This curation discipline applies equally to uploads and to connected sources -- a connector doesn't need curation in the same mechanical sense (it points at a live source), but the decision to connect it in the first place, and to which folders/scopes, is still a curation choice.

The Governance Overlap

Because uploaded and connected content may include sensitive data, knowledge management overlaps directly with governance: only add data that policy permits. A business user adding a file or turning on a connector is making a data-handling decision, not just a convenience decision -- and that decision should be checked against organizational policy before the content becomes part of a Project's grounding material.

This is the same underlying discipline covered more fully under governance, but it surfaces here as a practical, day-to-day configuration step: before you upload or connect, check whether the data is allowed to be there.

Common exam traps

• Uploading or connecting regulated or sensitive data without checking policy first -- treating knowledge configuration as a purely technical/convenience decision misses that it is also a governance decision.
• Assuming curation is a one-time cleanup rather than an ongoing habit; sources that were appropriate when added can become stale or, in the case of policy changes, become inappropriate to keep.