Overall Architecture Sample Clauses

Overall Architecture. The overall architecture of the gCube Infrastructure Enabling Services is depicted in Figure 6. It consists of six cooperating subsystems whose role, functions and relations are briefly described in the rest of this section.

Overall Architecture. The Architecture of the Information Organization services is articulated over three fundamental layers, as illustrated in Figure 27, Base Layer, Storage Management Layer, Content Management Layer, Metadata and Annotation Management. Additional information about these layers and their functionality is provided below, while the technical details related to how to interact with the services at each layer are provided in the next sections.

Overall Architecture. Due to the nature of the ▇▇▇ and its integration within the many different CMS and aggregator systems throughout the Europeana Inside project there can be no one overall ‘system architecture’ in the traditional sense. Rather the ▇▇▇ will be made up of a set of modular components that may or may not be implemented as standalone services in the Europeana Inside ecosystem rather than as a single monolithic whole. Some of these modules will actually come from existing functionality within CMS systems, others will be developed as part of this project and can be incorporated directly into or interfaced with the CMS or aggregation systems themselves and others might be existing third party components which can be used ‘as is’ or wrapped in a service later with appropriate API calls. The high level architecture was designed to meet the following principles: • The overall architectural style complies with established principles for service oriented architectures1 • The ▇▇▇ comprises a set of modular components • The components may be implemented locally or externally • Functionality which is closely related to exist functionality within a CMS should be embedded within the CMS • Components should expose (machine) interfaces to other components in a consistent fashion • User interfaces, where necessary, will be embedded within the CMS and will be consistent with the look and feel of the individual CMS • As well as the CMS, ▇▇▇ components will interact with, and may be embedded in, aggregators • Some ▇▇▇ components will interact with aggregators or directly with Europeana Figure 1is a representation of the overall architecture and environment in which the ▇▇▇ will operate. Some of the functional requirements listed in D2.4 are to be provided by the CMS itself, while other parts are provided by external, shared modules. The connections between the components are of course as important as the individual modules themselves as they represent the interfaces presented by the different modules and the communications that are sent via these interfaces. The figure depicts the overall architecture as consisting of a number of modules. These modules are summarised in Table 1. As can be seen from Figure 1, some ▇▇▇ modules have been incorporated into the aggregators used within the project. ▇▇▇ functionality has also been implemented in other components of the ecosystem, such as middleware, but these variants have been left out of the diagram for simplification purposes. 1 ▇▇▇▇:/...

Overall Architecture. ‌ Figure 13: Integration design diagram for the DURAARK framework 1. On the frontend side, so-called User Interface (UI) Modules are responsible for displaying data and interacting with the user. On the backend side Web Services are processing data and deliver the data in a consumable form for the UI modules. The web service layer of the DURAARK framework provides a RESTful API to communicate between service and UI module. The actual implementation of the web service has to be provided by the developer. This decoupled approach makes it easy to exchange the implementation of a web service with another or updated one, without having to change a) the code in the consuming UI module and b) the API code of the web service.

Overall Architecture. The high-level Go-Lab architecture, illustrated in Fig. 1, consists of two main components with a graphical user interface (GUI), namely the lab repository and the ILS platform. Both are supported by components for user management and tracking user activities for learning analytics and recommendation. By splitting up the portal functionality in this way, each component serves a very different purpose and we aim to satisfy the requirements and design principles stated above. The components have well-specified interfaces and protocols, which allow interchangeability (e.g., the ILS platform could use another repository that implements the same specification of the Publisher & Instantiator interface) and other third-party platforms can make use of each component separately enabling wider adoption of Go-Lab technology. The next section elaborates on the components of the architecture.‌

Overall Architecture. Due to the nature of the ▇▇▇ and its integration within the many different CMS and aggregator systems throughout the Europeana Inside project there can be no one overall ‘system architecture’ in the traditional sense. Rather the ▇▇▇ will be made up of a set of modular components that may or may not be implemented as standalone services in the Europeana Inside ecosystem rather than as a single monolithic whole. Some of these modules will actually come from existing functionality within CMS systems, others will be developed as part of this project and can be incorporated directly into or interfaced with the CMS or aggregation systems themselves and others might be existing third party components which can be used ‘as is’ or wrapped in a service later with appropriate API calls. This lack of an overall architecture means that the ▇▇▇ must be specified by the set of high level, functional and non-functional requirements that have been determined by previous stages of the project. In addition the interfaces and interactions between the ▇▇▇ components and with external tools such as existing CMS components, vocabulary management systems, Europeana itself, etc. will make up a key part of the overall architecture. Figure 1 is a representation of the overall architecture and environment in which the ▇▇▇ will operate. Some of the functional requirements listed in D2.4 are to be provided by the CMS itself, while other parts are provided by external, shared modules. The connections between the components are of course as important as the individual modules themselves as they represent the interfaces presented by the different modules and the communications that are sent via these interfaces. The figure depicts the overall architecture as consisting of an ▇▇▇ ‘Core’ with additional modules as external to the ▇▇▇ core. However, it is expected that many of the modules may actually be implemented within the core itself. They are simply presented this way in order to make the figure more easily understood. Equally it is expected that the aggregator and possibly even Europeana itself will also incorporate the ▇▇▇ but again this duplication has been left out of the figure for simplification purposes.

Overall Architecture