[FEATURE] add config option for MetaDataExtractor #222
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dkd-kaehm
force-pushed
the
metadata-option
branch
2 times, most recently
from
94a752d
to
82848ab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a separate checkbox to the extension configuration options, which toggles the registration of MetaDataExtractor and LanguageDetector within TYPO3.
Background: We have a use-case for ext-tika, where we only want to make use of content extraction. The meta data extraction is not required for our use case of ext-tika. On the contrary, it bothers us that fields within sys_files_metadata get overwritten whenever a file change is detected by TYPO3 (e.g. when renaming a file).
Maybe others have similar use cases, where they only want the "content extraction"-part of this extension and such a toggle in the options is useful.