FEATURE: Make it possible to set a default set of configured columns in settings/config

[anderser]

Is your feature request related to a problem? Please describe. When browsing through search results the users often need to add columns from the "configure columns" dropdown. Our experience is that some columns are useful for all users across the newsroom. We use a lot of time teaching all the journalists how to add those columns. And if they use a new browser they have to redo it.

Describe the solution you'd like A way for admins to define a set of default columns that should appear for all users across the Aleph instance. This could be a setting in the aleph.env file.

I.e. DEFAULT_COLUMNS='retrievedAt:modifiedAt:publisher'

We need to make sure that these columns do not re-appear if the users removes them manually, somehow.

Describe alternatives you've considered Predefined columns per investigation/dataset: I think this will be troublesome when searching across datasets, which column should be shown in that case? Would probably also be a bit of a hassle to maintain.

Additional context None

[ozhyrenkov]

I think it makes sense to add not just configuration thing for the columns which are being showed, but also a way to set attributes mandatory. Of course one can make this through the ftm-schema fixes, but it breaks the followthemoney versions compatibility. Let me give a bit context: I am trying to teach people, who use our instance of Aleph to set up a SourceURL and always have a codes for vessels and vehicles. But they constantly forgetting this point :D In case it would be mandatory field to fill - there won't be a place for mistake.

So I propose:

• to extend collection configuration panel with Advanced tab.
• to allow user pick an entity of interest and specify:
  • columns to show;
  • mandatory fields.

[Rosencrantz]

@ozhyrenkov This sounds like a useful feature, but to me it is distinct from Andersers request above. Could you create a seperate feature request for this?

[ozhyrenkov]

@Rosencrantz ok, sure, it just landed here: https://github.com/alephdata/aleph/issues/2330