Remove IMS dependencies from registry

18057
Reporter: trobertson
Assignee: fmendez
Type: Bug
Summary: Remove IMS dependencies from registry 
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2015-12-01 11:44:32.383
Updated: 2018-05-31 16:38:02.741
Resolved: 2018-05-31 16:38:02.695
        
Description: The registry exposes the /node API which is a hybrid of:

1) Content in the registry database
2) Augmented with content served from the Drupal MySQL DB copy of the IMS filemaker database. [1]

When the GBIF Directory is developed, the IMS will no longer exist, and the MySQL copy of the IMS tables will no longer exist.  The GBIF Directory will offer a Node api, but *this is not backwards compatible* as it correctly distinguishes between Nodes and Participants.

Therefore, since we wish to maintain the same /v1/node API, we will need to modify the registry so that the Node is built from the Directory postgresql database.  This does indeed mean the directory-ws and the registry-ws are both surfacing node information, but this is the best (only?) way to ensure we maintain backwards compatibility.

For /v2/ we will of course just use the directory ws natively.


[1] https://github.com/gbif/registry/tree/master/registry-ws/src/main/java/org/gbif/registry/ims]]>
    

Author: mblissett
Comment: Presumably was done.
Created: 2018-05-31 16:38:02.738
Updated: 2018-05-31 16:38:02.738