Modifying Content with Handlers, Metadata Filters and Metadata WriteFilters

There are several ways to modify, limit or process content during or after the parse.  In the following, we describe the three main categories.  Each of these has been developed for specific purposes and may not be appropriate for all needs.

ContentHandlers

These are applied during the parse.  A small handful may cache all the contents in memory.

Metadata Filters

These are applied at the end of the parse.  These are intended to modify the contents of a metadata object for different purposes:

1. Enrich the data (similar to a ContentHandler) -- these metadata filters might run language detection on the cached contents at the end of the parse.
2. Modify the metadata contents – one might want to run a regex over a specific field and extract only the information matching a regex, for example.
3. Modify the metadata keys – If you need to rename metadata keys before emitting the object to, say, OpenSearch, you can use the FieldNameMappingFilter
4. Limit the metadata fields -- let's say you only want dc:title and text, you can use these: ExcludeFieldMetadataFilter or IncludeFieldMetadataFilter NOTE: these were created before we had MetadataWriteFilters; those are probably a better option for this behavior.

Metadata Write Filters

These filters are applied during the parse.

The primary goal of the metadata write filters is to limit the the amount of data written to a metadata object for two purposes:

1. Limit the total number of bytes written to a metadata objects (prevent DoS from files with large amounts of metadata)
2. Limit the fields written to a metadata object (decrease bytes held in memory during the parse and decrease the bytes sent over the wire/written to a file after the parse)