add named metadata event

[ArtificialOwl]

This adds:

• a new event MetadataNamedEvent,
• an optional parameter to the existing occ files:scan --generate-metadata [name] command.

The idea is to provide a last param to the IFilesMetadataManager::refreshMetadata() that assign a name to the event.
Any app listening to the MetadataNameEvent will use getName() to confirm the event is related to itself and manage the refresh of metadata the same way it would manage the Live and/or Background Event.

This way, we can ask a refresh of the metadata from all files' from the cloud without loosing time refreshing all metadata provided by all apps.

[artonge]

So existing providers need to all listen to this new event?

[come-nc]

So named event is always live, or always backgrounded?
Why the name is not an optional parameter for both MetadataLiveEvent and MetadataBackgroundEvent?

[ArtificialOwl]

Because it would require a check condition on every Live/Background listeners

[ArtificialOwl]

So existing providers need to all listen to this new event?

no, this is purely optionnal; only if they want to called via a specific occ command.
It should only be implemented if they want to provide a faster way to only add their own metadata on a scan

[come-nc]

So the passed name does not need to match a metadata name, it’s like a tag used by some providers?

[ArtificialOwl]

So the passed name does not need to match a metadata name, it’s like a tag used by some providers?

yes, as we don't communicate via provider we cannot enforce provider_id

[ArtificialOwl]

The idea behind this is mostly to remove the custom files scan from files_fulltextsearch and use metadata to store the status of the index of a document there.

However, starting a full index of your current document will also trigger some heavy process from the extraction of metadata from photos.

Using NamedEvent, I can trigger a scan of files to only update metadata related to fulltextsearch

[come-nc]

I get the idea, I’m not entirely sure this won’t be cause for trouble.
Especially there is nothing to prevent name clash between applications.

[artonge]

Feels highly specific, but I do not see any other solution.