Sick or drunk ? either way, get better.
fulltextsearch does not get access to your files.
files_fulltextsearch is defined as a content provider and feed the
fulltextsearch with the content of your files that will be sent to
fulltextsearch_elasticsearch for indexing.
Which means that yes:
files_fulltextsearch will get any content from unencrypted files, so any app that generate file(s) available to the Nextcloud Files will see their content indexed (based on the mimetype/format).
Which also means that yes: apps that store content in database won’t have their content indexed by
Which finally means that if your app generate contents that are not stored in files, you will need to provide a content provider within your app if you want the content to be indexed by
If by metadata, we’re talking name of file, sharing rights, …, when available they are indexed and used during the search.
If your talking about the metadata app, this should be doable by making a small extension of
files_fulltextsearch. I know someone started working on this but fulltextsearch was still alpha by the time and the tools were missing. But, with today’s API, you should be able to do something within few hours.
files_fulltextsearch provide some hooks when indexing files/search for content that allow any 3rd party app to ‘complete’ the indexing process with its own data (ie. the
files_fulltextsearch_tesseract app that will OCR your files and help fill the content to be indexed during the process)
If an app can get the content, it can index it.