Extractors are KBC components used for importing data from external sources into KBC.
Typically, they connect to external services APIs, like Facebook, Youtube, etc. They can also connect directly to an arbitrary database, or, for instance, process incoming e-mails.
For a definitive list of usable extractors, see your project Extractors section. Since each extractor connects to a different data source, their configurations might differ greatly.
Extractors are generally designed for automated and repeated data collection, though they can be triggered manually at any time.
- For manual import of ad-hoc data, see Data Import in Storage, or our tutorial on manual data loading.
- Configure a sample extractor.
- Configure a database extractor.
As bringing data into KBC is the main purpose of an extractor, go the path of least resistance:
- Get your data in first, and
- Then convert it to what you want it to look like.
To give an example, when you are connecting to existing information systems, do not modify the data in them. Such data conversion can prove to be difficult and expensive. Extract what you need and shape it in KBC.
Some extractors have limits inherent to their sources. Unfortunately, there is not much we can do about it. For example, the Twitter extractor will not let you access the history of a particular tweet account beyond a certain point because of the limitations of Twitter API.