The OMRS Cohort Registry Store stores information about the repositories registered in the open metadata repository cohort. 

 

Figure 1: Cohort registry stores in an open metadata repository cohort

Each server in the open metadata repository cohort runs an OMRS Cohort Registry to manage its registration with the cohort and maintain the contents of its local cohort registry store. 

 

 

Figure 2: logical structure of the cohort registry store

Each member in the open metadata repository cohort is represented in the cohort registry store with a member registration record.  This has 3 values in it:

  • Metadata Collection Id - this is a unique string that identifies the repository.
  • Registration Timestamp - this is the time that the server registered its repository.
  • Remote Connection - this is the connection information that a remote server can use to create a connector to query values in the repository.

Inside the cohort registry store is a record of the local server's registration and a list of registration record for each remote repository that it knows about.

 

The OMRS Cohort Registry store is implemented as an OCF Connector so the implementation is configurable.  The initial implementation is a file based store that uses JSON.


 

  • No labels

4 Comments

  1. Yao Li

    From Figure 1, it makes me feel like one repository will have its own Cohort Registry Store. So there is no central one. Each server manage its own Cohort Registry Store content. Is this understand correct?

    1. Mandy Chessell

      Yes

  2. Yao Li

    In Figure 2 it makes me feel like there will be one Remote Registration which contains a list of Remote Registration. But it actually only means for a Cohort Registry Store, it contains 1 local Registration and a list of Remote Registrations. Is this understand correct?

    1. Mandy Chessell

      Figure 2 has one RemoteRegistrations (not RemoteRegistration) which is a list of RemoteRegistrations.