Skip to content

Latest commit

 

History

History
120 lines (69 loc) · 4.3 KB

HL Architecture diagram.md

File metadata and controls

120 lines (69 loc) · 4.3 KB
Raw

OPP-6-WIS-Djibouti

High-level architecture diagram

Presents a bird's eye view of the operations and basic data-flows envisaged for OPP-6. The main actors and actions are identified as well as the main building blocks of the system:

(edit this diagram in draw.io)

Point 0 - General

  1. Q: Implementing security restrictions/checks will not be a target for the PoC. However, should we support some very basic user authentication? Regarding the calls in (P5) and (P6) we could have some basic, token-based authentication in place especially since (P14) will be deployed on public Internet.
    A: Yes. Basic security is required. Discuss with UKMO to re-use part of infrastructure. Security will focus on users like Mouktar and not end-users.

  2. Q: Do we want commercial search engines to also crawl AWC?
    A: Not at this point.

  3. Q: Do we envisage a central, single AWC or multiple ones? e.g. AWC France, AWC UK, etc. A: For the pilot, only one.

Point 1 - Creation of CSVs

  1. Q: Should the local WebApp (P11) provide a functionality to create CSVs online?
    A: No.

  2. Q: Do we care for the format/columns of the CSVs? Is there a standard to be used?
    A: No.

  3. Q: We will need some sample CSVs, who is going to prepare/provide them?
    A: Dom.

Point 2 - Pushing CSVs to the Web Server

  1. Q: Do we intend to provide some tool here or is it up to the user?
    A: No.

Point 3 - Pushing CSVs to a secondary dissemination channel

  1. Q: Do we intend to provide some tool here or is it up to the user?
    A: No.

Point 4 - Registering sitemap with a commercial search engine

  1. Q: Which search engine will we pick for the PoC?
    A: Google.

  2. Q: We need some info/research here regarding the format/content of the sitemap.
    A: Check if someone has extensive experience in the subject.

  3. Q: We need some info/research here regarding the registration process, time to crawl, frequency of updates etc.
    A: Check if someone has extensive experience in the subject.

Point 5 - Registering sitemap with the AWC

  1. Q: Can we use the exact same sitemap as in (P3)? This is largely related to the specs of (P14).
    A: TBD.

Point 6 - Notifying AWC of data updates

  1. Q: Do we envisage anything more complicated than an HTTP/GET call?
    A: Need notification for new data. Optionally, for new metadata.

  2. Q: Alternatively, do we need this call or we rely on the Crawler identifying new data (and proceeding to sending notifications)?
    A: See (6.1)

Point 7 - Local web server

  1. Q: For the PoC we need to define the Web Server to be used/supported.
    A: Go for quick :)

Point 8 - Local secondary dissemination channel

  1. Q: Is the secondary dissemination channel something we consider for the PoC? If it is, we need to define what that should be.
    A: No secondary dissemination channel for PoC.

Point 9 - Generating the sitemap

  1. Q: How is the sitemap going to be generated? If not manually, we should investigate tools/methods.
    A: Manually.

Point 10 - Generating web pages for CSVs

  1. Q: How are the pages going to be generated? If not manually, we should investigate tools/methods.
    A: Use HTML templates privided for the PoC.

Point 11 - The local WebApp

  1. Q: What should be the main functionality of the local WebApp?
    A: Simple CSV visualization using existing tools.

Point 12 - Optimising search queries to the commercial search engine

  1. Q: Once we choose the search engine to use, we need to investigate how to query it according to our needs. Can you provide a few representative queries we would like to run? A: Dom will define a few use/test cases for that.

Point 13 - AWC crawling local dissemination environments

  1. Q: Decide on the crawling mechanism as well as the underlying storage mechanism (this is directly related to the queries to be supported by (P14)).
    A: TBD after P14.

Point 14 - The AWC WebApp

  1. Q: Provide a few indicative queries.
    A: Jeremy will define a few use/test cases for that.

Point 15 - AWC real-time notifications

  1. Q: Is the central approach for real-time notifications the one we want for the PoC?
    A: Yes, central.

  2. Q: Real-time notification are about the existance of data, or they disseminate the data itself as well?
    A: No.