Project

General

Profile

Actions

task #7935

closed

Discuss new solution to establish the communication between submitter and curator

Added by Andreas Kohlbecker about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Highest
Category:
cdm-vaadin
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Tags:

Description

As stated in #7785 the checking for messaged in the Redmine instance serving as communication hub slows down the display of registration working sets a lot (43%)

--> decide for another solution to establish the communication between submitter and curator

The concept of using redmine as communication and messaging hub has been discussed during the last playday session. Result of this discussion was that this concept is not fulfilling the requirements. We should expect a lot of direct communication between submitter and curation which will often pass by any messaging system/hub. Therefor it might not make much sense to have such hub for controlled communication.


Related issues

Related to EDIT - bug #7936: Consider complete removal of redmine communication hub code ClosedAndreas Kohlbecker

Actions
Related to EDIT - bug #8069: RegistrationUI: remove all messaging related code and message indicators from all viewsClosedAndreas Kohlbecker

Actions
Related to EDIT - task #7269: Use redmine as message hub for submitter curator communicationClosedAndreas Kohlbecker

Actions
Copied from EDIT - bug #7908: Redmine communication hub slows down RegistrationWorkingSetsClosedAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Kohlbecker about 4 years ago

  • Copied from bug #7908: Redmine communication hub slows down RegistrationWorkingSets added
Actions #2

Updated by Andreas Kohlbecker about 4 years ago

  • Description updated (diff)
Actions #3

Updated by Andreas Kohlbecker about 4 years ago

  • Related to bug #7936: Consider complete removal of redmine communication hub code added
Actions #4

Updated by Andreas Kohlbecker about 4 years ago

[Henning]

Normaler Weise würde man auf normalen E-Mail-Kontakt ausweichen und eine Funktions-Email einrichten, z.B. phycobankcuration@bgbm.org, allerdings werden zurzeit von der Zedat Funktionsmails auf den Prüfstand gestellt, um den Bestand drastisch zu senken...

Actions #5

Updated by Andreas Kohlbecker about 4 years ago

curation@phycobank.org wäre noch besser

Actions #6

Updated by Andreas Kohlbecker about 4 years ago

  • Priority changed from New to Highest
  • Target version set to Release 5.5
  • % Done changed from 0 to 10

We agreed on a pure email solution without any messaging system:

curation@phycobank.org sollte auf eine bgbm interne Adresse verweisen: curation.phycobank@bgbm.org

Actions #7

Updated by Andreas Kohlbecker about 4 years ago

  • Status changed from New to In Progress
Actions #8

Updated by Andreas Kohlbecker about 4 years ago

  • Target version changed from Release 5.5 to Release 5.6
Actions #9

Updated by Andreas Kohlbecker almost 4 years ago

  • Related to bug #8069: RegistrationUI: remove all messaging related code and message indicators from all views added
Actions #10

Updated by Andreas Kohlbecker almost 4 years ago

  • Subject changed from Discussion new solution to establish the communication between submitter and curator to Discuss new solution to establish the communication between submitter and curator
Actions #11

Updated by Andreas Kohlbecker almost 4 years ago

  • Related to task #7269: Use redmine as message hub for submitter curator communication added
Actions #12

Updated by Andreas Kohlbecker almost 4 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber

Hi Henning,

is there anything left to discuss regarding this issue?

Andreas

Actions #13

Updated by Wolf-Henning Kusber almost 4 years ago

  • Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
  • % Done changed from 10 to 100

As plan B: E-Mail curation@phycobank.org is working now,

Currently most phycologists contact the curator by the personal bgbm mail.
April 2019: There is c. one message in/out per day concerning PhycoBank issues. This can be handled.

Plan A task #7269 will not be continued.
Plan B task (this ticket) is as a practicalbe and simple solution solved.

Actions #14

Updated by Andreas Kohlbecker almost 4 years ago

  • Status changed from Feedback to Closed
  • Target version deleted (Release 5.6)

noting to add to this issue. The email based communication is a proper solution for the time being.

Actions

Also available in: Atom PDF