Architecture
The main functionality of PTCRISync is to synchronized user profiles of interested services with the respective ORCID profiles, acting as a proxy between the two services. Thus, the parties involved in the process are:
- The ORCID service (see an overview of relevant concepts)
- A CRIS service using PTCRISync (see the imposed requirements
- The PTCRISync library (see a description of the synchronization procedures)
- A CRIS interface implementing PTCRISync (see a recommended interface)
- The user, which acts directly on both the CRIS and ORCID profiles, and grants privileges to PTCRISync
To encapsulate the communication with ORCID, PTCRISync relies on an third-party ORCID client.
PTCRISync is a stateless library of synchronization procedures that connects with both the ORCID and the CRIS services. To facilitate integration, communication with PTCRISync is always performed according to the ORCID data model. The user manages the behavior of the PTCRISync library through the CRIS interface, that should support certain functionalities in order to be compatible with PTCRISync. In particular, it should manage a notion of persistently synchronized production, that is always kept up-to-date between the profiles. Moreover, the CRIS backend itself should be able to support the notification paradigm over which PTCRISync is build.