Creation of new labels to classify the issues

[andre-hohmann]

Problem

I had a look on several issues to think about helpful improvements with regard on the development fund 2022. This is very time consuming, because nearly every issue has to be assessed on its own regarding the concerned subject areas and thus its relevance for an improvement.

Solution

From my point of view, the Labels should be extended to some more broad subject-categories as for example:

• performance
• search/filter
• newspaper
• import
• ruleset
• ...

On the first glance, it might seem unnecessary, but with 470 open issues, it is from my point of view an opportunity to assess quickly the issues and to bundle them. Especially regarding the development fund but also for other development-initiatives, it would be helpful to enable a quick overview of related issues.

It would be OK, if these labels have always be to combined with the improvement-label or with the feature-label. It just would be helpful not to assess each of the 470 issues by content.

[matthias-ronge]

For the same reason, I once started keeping a list in the wiki to organize the issues better. I made up the following categories, in order of decreasing priority:

• Dangerous
  A risk of life or limb, property damage, security issue or the risk of loss of work.
  This is basically equal to the security label that we already have.
• Unusable
  An essential functionality of the application is not given. There is no work-around.
  This is basically equal to the blocking label that we already have.
• Faulty
  A target functionality is not given or behaves wrong.
  This is what a bug describes best.
• Fragile
  An error is badly intercepted. A tiny incorrect operation leads to incredibly bad things.
• Unsightly
  Slipped layout, typographical errors, …
• Inconvenient
  A target functionality is not available, but there is a work-around. Likewise: A target functionality can only be achieved with an unnecessarily high operating effort.
• At a loss
  Poor operator guidance, the meaning of input elements is not revealed, nothing seems to happen when a function is triggered (if the function actually works). Likewise: No error message in the event of an error, it gives the impression that the function has worked where it did not.
• Opaque program code
  Confusing program code, cleaning up necessary.
• Non-interoperable software solution
  An in-house solution is used where a standard solution could be used.
• New feature
  A completely new type of functionality is desired.
  This exists as feature label
• Conception
  Discussion with an open outcome, no clear goal yet.
  These should be moved to discussions

Aside from that, I came up with the following subject keywords:

• administrability
• business objects
• calendar hierarchies
• documentation
• export
• hierarchical processes
• import
• layout
• list view
• metadata editor
• migration
• multitenancy
• performance
• process creation
• search
• security
• statistics
• tasks
• text
• workflow editor
• workflow engine

[andre-hohmann]

@matthias-ronge : Thanks, that is very close to what i expected. The creation of your list was certainly quite time consuming. From my point of view, that should be solved with the labels.

The priority labels i had not in mind, but maybe the existing ones could be complemented. Regarding the subject labels, i prefer the following ones:

• calendar hierarchies
• export
• import
• layout
• metadata editor
• migration
• performance
• search

Could we create and apply them to have a look how it works? Is there someone who organizes the labels and decides about new ones?
I suggest to use the same color for all subject labels to indicate the subject-reference. Maybe a neutral color as a white background would be good to show that the subject label is a supplement to the colorful "priority" labels.

[matthias-ronge]

I don't have permission to do this

[matthias-ronge]

@Kathrin-Huber @Erikmitk @henning-gerhardt What do you think about this? Could one of you perhaps create a few more meaningful labels?

[henning-gerhardt]

I'm not the right person for this @matthias-ronge as I'm not an administrator nor release manager.

[andre-hohmann]

Here a part of the list from: Bugs by severity with the current state. The aim to copy it here is to see, which issues are still open - especially the important ones,

10 Dangerous

• Update Java (and maybe Tomcat) version  #4106 security
• Replace current mechanism to store encrypted passwords #456 security

9 Unusable

• Migrating hierarchical processes uses wrong template #3190 migration
• Process link cannot be deleted #3275 metadata editor hierarchical processes
• CopyData has stopped working #3368 import export
• For process with workflow created by migration, all tasks are closed #3569 migration
• Indexing is pausing on long index run #3713 search
• Calendar cannot be saved #3722 calendar hierarchies
• Double setting for beginning of the year #3741 calendar hierarchies
• Structure tree is not sorted correctly #3751 metadata editor
• Metadata editor crashes with metadata group not defined in the ruleset #3762 metadata editor
• On Export: Duplication of smLink entries #4064 export
• Always showing multi-select metadata is not saved  #4068 metadata editor
• Multi-line single-select metadata is not saved #4069 metadata editor

8 Faulty

A target functionality is not given or behaves wrong.

• Edit metadata in the task being performed #3156 tasks
• Allow configuration of acquisition stage per workflow step #3155 tasks
• Show existence of images in process list #3292 list view
• Advanced search’s task status filter not working #3341 search
• Incomplete validation by creation of new processes #3403 process creation
• Generation of “TSL/ATS” for volumes of multivolume works without title #3408 process creation
• Add new InsertionPosition for structural elements in metadata editor #3486 metadata editor
• Metadata should be searchable via advanced search #3512 search
• Extended Search: "does not contain" option for project-search does not work #3523 search
• Missing notification function to all users #3586 administrability
• Import breaks user interface when person has multiple roles #3640 import
• "Assign to next element" not available in the Erweiterter Strukturbaum #3646 metadata editor
• Error deleting 'project' #3649 business objects
• Don't forget metadata when changing DocType #3664 process creation
• Script task as first task is not started #3672 workflow engine
• Faulty script task is completed #3673 workflow engine
• Setting task to 'in process' via administrative action should also set processing user #3692 business objects
• VariableReplacer does not work properly in the script step #3718 workflow engine
• pica2kitodo_default.xsl not working with all catalogs #3800 import
• Configuration of metadata for year-elements #3812 calendar hierarchies
• Automatic Taks in strange state: (somehow finished, but process is not propagated to next state) #3818 workflow engine
• OPAC import replcesShelfmarksource with CatalogIDDigital #3880 process creation
• Wildcard search does not work properly #3938 search
• There is no possibility to choose a teaser image #4017 metadata editor
• Limitation of processes in the excel file (statistics)  #4099 statistics
• Difficult to tell if someone is active #4129 session management
• When saving a copied project, additional production templates are linked #4150business objects
• Production templates deleted from a project cannot be added again #4152 business objects
• The same page can only be linked to two chapters #4155 metadata editor

[andre-hohmann]

I moved this issue to the discussion-area, as it is not really an issue.

With the new labels added on 2023-02-24, the question is answered.