Categories for software: visible per default

[cmeessen]

Relates to #984 #741

Current implementation

The user can add categories by clicking on the drop down menu:

Selected categories appear below <h2>Categories</h2>

Change request

Administrators can define top level categories that will always appear in the software edit view (default categories).

The goal is to nudge users towards using the default categories.

Example

The defined default category is Some simple research fruits:

[fembau]

Some thoughts for further refinement:

1. Only top-level categories could be a default category
2. How default categories and Categories appear and co-exist in the edit-software-UI.
   • cases: no default categories, one default category, several default categories
   • Default categories do not appear in the list/dropdown of Categories
   • ordering of category headlines/blocks
   • Currently all headlines have a sub-title. How default categories should appear?
3. How default categories and Categories appear and co-exist in the view-software-UI.
   • Appear default categories separated from other categories?
   • ordering of category headlines
4. UI for admin

[cmeessen]

Here are some notes from our discussion:

Only top-level categories could be a default category

Yes

How default categories and Categories appear and co-exist in the edit-software-UI.

• cases
  • one or more default categories: default categories sorted alphabetically first, then other categories
• ordering of category headlines/blocks: alphabetically
• sub-titles: add column in db, if empty do not render

How default categories and Categories appear and co-exist in the view-software-UI.

• current state of discussion: prefer to move default categories to separate block in the main content because HGF has some really long titles for research programs and topics. We don't know where and how yet.

[fembau]

add column for provenance #1141

[fembau]

should we add a flag for "where to display" a top-level certain category, e.g. right sidebar (default) or main container (as extra block to emphasize)

[cmeessen]

Here is a mockup with our preferred design at the moment. The blocks should be displayed after the Contributors.

We did not yet decide whether to use the upper or lower representation.

@ctwhome what is your opinion?

[fembau]

We further discussed the feature and decided:

1. Categories which are marked as is_highlight are visually brought out. In the software edit view they get an extra dropdown menu and in the software view they have an extra section in the main content area.
2. Categories on different levels in the hierarchy could have different extra properties. These are now aggregated in one database column properties of type JSONB.
3. In the software edit view: A highlighted category should have a subtitle (shown below headline) and a description (shown in the blue help/info sidebar) to support the user adding metadata.

[fembau]

[ewan-escience]

Most work is done now in #1227 and #1219 by using highlights. The only thing that is needed is to add the field tree_level_labels to the interface, right?

[cmeessen]

Yes, as far as I can see the tree_level_labels are the only missing feature in the UI.

Apart from tree_level_labels there is also no UI representation of adding a logo for a top level category.