'Blocklist' of IDs which should not appear in Result Lists

[silvanheller]

For some of the datasets commonly used with vitrivr, there might be items which should not appear in results when the general public can interact with demos. Instead of having the effort of separate deployments, a very simple solution would be as follows:

• There is a new config field blocked_object_ids which could for example be populated as follows: [v_0007, v_01240, is_2016_04_20]`
• In the ContinuousRetrievalLogic, simply remove all SegmentScoreElements which contain a blocked id. This might result in config values not being exactly followed, but that is an acceptable tradeoff for public demos.

For new Contributors

Feel free to set up the stack: https://vitrivr.org/getting_started.html. Afterwards, have a look at the implementation suggestion above and feel free to get started.

[lucaro]

I get your point, although I'm not a fan of having a simple black list. If such a mechanism is introduced, why not turn it into a proper access management mechanism, which could then also be extended to take into account where a query is coming from?