ARCHITECTURE DESCRIPTION Sample Clauses

ARCHITECTURE DESCRIPTION. From the requirement analysis in the previous chapter it becomes clear that the EUMSSI system should fulfil three main functions:  Collect and store (meta-)data of multimedia resources from several sources in a unified format.  Enrich the existing data with the (combined) outcomes of audio, video and text analysis.  Provide end-users (journalist and second-screen users) with useful and/or entertaining suggestions, background information and recommendations. Along with discussions on the system’s functionality, several iterations of architecture sketches have been created with the intention to communicate the envisaged functionality to the consortium partner, and to facilitate the selection of components. In the next section, we summarize the different iterations, to provide a historical background on the design decisions, as reflected in the current architecture. The current software architecture design is discussed in Section 4.2. We will first provide an overview of the four main components, followed by a more detailed description of the main functionality and – where applicable – the framework or tools that will be used for implementing the component. The second part of the architecture design involves the process flows, which are illustrated in section 4.2.2. 4.1. Initial sketches and selection of components

ARCHITECTURE DESCRIPTION. The architecture as shown in figure 23 is made up of three principal components: the neuGRID Single Sign-On (SSO) system, the neuGRID dashboard (menu – in orange) and the neuGRID JSR286/WSRP 2.0 compliant portal.

ARCHITECTURE DESCRIPTION. There are three main technical components of the anonymization service: • The neuGRID pseudonymization library • The Pseudonymization Web Service • The Pseudonymization applet/stand alone application The neuGRID pseudonymization library is a Java library providing the necessary methods required to pseudonymize DICOM images in a reusable form. In order to leverage the work and reuse what has already been done the library is using an already existing DICOM manipulation library, the dcm4che2 toolkit. dcm4che2 is a high performance, open source implementation of the DICOM standard. The neuGRID pseudonymization library allows sharing of the pseudonymization code between both the Pseudonymization Web Service and the pseudonymization applet/standalone application ensuring that the same coherent level of pseudonymization is used throughout the neuGRID infrastructure. The Pseudonymization Web Service is the point of entry in the neuGRID infrastructure to pseudonymize and upload the images. It allows users to send images for pseudonymization and once done, these images can be uploaded on the GRID, registered into LORIS and used by neuGRID users. The Pseudonymization applet/stand alone application is a tool that will be provided to neuGRID's users to help them pseudonymize images without having to send the images outside the walls of the hospital. The pseudonymization applet will make full usage of the latest Java features allowing the creation of an applet that can be dragged out of a browser and that can be used outside of the browser's context without having to be connected to the Internet. To provide a web- friendly access, the following two steps have been planned initially: • The development of an applet for the pseudonymization of images. • The adaptation of the applet to allow it to be fully functional outside of the browser. The data anonymization process is described through the steps shown in figure 30 whereas in figure 31 an overview of the Service deployment is shown.

ARCHITECTURE DESCRIPTION. When talking about RP requirements we say that the RIP will act as a "Front End (FE)", so in this section we will use this term instead of the usual RIP one. In the Remote Proofing (RP, in short) service, the Front Ends (FE) can act as two different actors: o Front End as a consumer of Remote Proofs: in this role, the Front End prints proofs. o Front End as a producer of Remote Proofs: in this role, the Front End generates the proof file that is going to be proofed. o The proof file must follow the Remote Proof Data Exchange Format Specification. The FE (SW RIP) described in this specification will work ONLY as a consumer of proof jobs. The FE communicates with a local application that it's installed at the same time (so, it's always available). We call this application the HP Remote Proofing (RP) engine. In the picture below you can see the different components in the system, and the interfaces among them. The FE can receive files through the input hot folder from the PS driver (regular path) or from the remote proofing service (remote proofing path). -------------------------------------------------------------------------------- HP InkJet Commercial Division Monday, December 10, 2001 HP SW RIP External Reference Specification [hp logo] -------------------------------------------------------------------------------- -------------- Graphic design -------- application \ Internet -------------- \ TIFF, JPEG,... -------- \ | App file | \ | --------- \ ---------------------------- PS driver \ HP RP engine --------- \ (with UI) \ \ ---------------------------- PS \ \ / | \ \ / | \ \ / JDF file with a | \ \ / reference to a | \ \ / PDF job file | ----------------------------------------- | Input Hot | Folder | ----------------------------------------- | | ----------------------------------------- FE engine ----------------- (no RP UI) -------------- Output Hot folder ----------------------------------------- XML ----------------- | notifications | (job status) | | ----------------------------------------- Printer/Proofer ----------------------------------------- The interfaces between the HP RP engine and the FE server are: o The RP-to-FE Input Hot Folder for reception of JDF job files. The format of these files is defined in the document: "HP Remote Proofing Data Exchange Format Specification". o The FE-to-RP Output Hot Folder for notifications from the FE engine to the HP RP engine. This Hot Folder will consist of a queue of events (Remote Proofing Events fro...