Synchronise with IMS for Participant Nodes information (existing Nodes, Nodes contacts)

10767
Reporter: ahahn
Type: Task
Summary: Synchronise with IMS for Participant Nodes information (existing Nodes, Nodes contacts)
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-02-03 16:26:21.687
Updated: 2013-12-16 17:50:49.73
Resolved: 2013-12-10 15:57:57.768
        
Description: Information on Participant Nodes is maintained outside of the registry, in the GBIF Information Management System (IMS). The registry requires some of this information to support functionality:
- list of existing Nodes (e.g. to offer selection list for endorsement requests)
- contact information (name, email) of Node Managers (e.g. to handle and automate endorsement requests).

This information should we synchronised in a one-directional process (IMS -> registry). No manual updates should be made on the registry side (no console editing UI), but regular updates out of the IMS are required.

As some Participant Nodes have more than one Node Manager, we need to review possible needs for determining a "Primary Node Manager" (IMS interaction / communication task), to avoid e.g. having to handle conflicting responses to endorsement requests from different endorsement request receipients within a Node.]]>
    

Author: kbraak@gbif.org
Created: 2013-12-10 15:57:57.798
Updated: 2013-12-10 15:57:57.798
        
Participant Nodes information is copied from the IMS into Drupal. The Portal views integrate this information with Nodes information in the Registry.

Ideally in the future, the Nodes information will only be stored in the Registry.

Closing issue.