WEB PUSH GFMS - Revision history

Admin at 12:59, 17 June 2021

2021-06-17T12:59:21Z

Admin at 12:57, 17 June 2021

2021-06-17T12:57:49Z

Admin at 12:53, 17 June 2021

2021-06-17T12:53:22Z

Admin at 12:53, 17 June 2021

2021-06-17T12:53:03Z

Admin at 12:49, 17 June 2021

2021-06-17T12:49:54Z

Admin at 14:13, 4 March 2021

2021-03-04T14:13:36Z

Admin: Created page with " [Home] - [DATA ACCESS] ---- which can be digested by all HTML capable browsers (Mobile or Desktop) by means of a web-socket based approach (see s..."

2020-11-12T14:27:46Z

Created page with " [Home] - [DATA ACCESS] ---- which can be digested by all HTML capable browsers (Mobile or Desktop) by means of a web-socket based approach (see s..."

New page

[[GFMS | [Home]]] - [[DATA ACCESS | [DATA ACCESS]]]
----

which can be digested by all HTML capable browsers (Mobile or Desktop) by means of a web-socket based approach (see section 2.4.3.3 Module - Web Push Notification)

----
[[GFMS | [Home]]] - [[DATA ACCESS | [DATA ACCESS]]]

← Older revision		Revision as of 12:59, 17 June 2021
Line 15:		Line 15:


−	Whenever [[PRODUCTS \| GFM's products]] are delivered from the EO-process chain, the metadata about the products are stored in the meta-data database (A). A periodic notification job, executed every 5 minutes, checks the product catalogue in the meta-data database according to the ordered notifications (B). If a notification must be issued due to the user’s request, the appropriate notification is pushed into a message queue (C).	+	Whenever [[PRODUCTS \| GFM's products]] are delivered from the EO-process chain, the metadata about the products are stored in the meta-data database ('''A'''). <br>
		+	A periodic notification job, executed every 5 minutes, checks the product catalogue in the meta-data database according to the ordered notifications ('''B'''). <br>
		+	If a notification must be issued due to the user’s request, the appropriate notification is pushed into a message queue ('''C''').

@@ Line 3: / Line 3: @@
 ----
-As users need automatic generated updates on their AOI for their products a Web-Push Notification and E-Mail service for registered users will be implemented. <br>
+As users need automatic generated updates on their ''AOI'' for their products a Web-Push Notification and e-mail service for registered users will be implemented. <br>
 The services follow an open paradigm, making it compatible with current web browser technologies. <br>
 After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the [[ REST_API_GFMS | '''REST-APIs''']]) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not.
@@ Line 13: / Line 13: @@
 [[File:webpush.jpg]]
 ----
 [[GFMS | [Home]]] - [[DATA ACCESS | [DATA ACCESS]]]

@@ Line 5: / Line 5: @@
 As users need automatic generated updates on their AOI for their products a Web-Push Notification and E-Mail service for registered users will be implemented. <br>
 The services follow an open paradigm, making it compatible with current web browser technologies. <br>
-After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the [[ REST_API_GFMS | '''<u>REST-APIs</u>''']]) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not.
+After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the [[ REST_API_GFMS | '''REST-APIs''']]) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not.

@@ Line 3: / Line 3: @@
 ----
-As users need automatic generated updates on their AOI for their products a Web-Push Notification and E-Mail service for registered users will be implemented. The services follow an open paradigm, making it compatible with current web browser technologies. After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the RESTful API) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not.
+As users need automatic generated updates on their AOI for their products a Web-Push Notification and E-Mail service for registered users will be implemented. <br>
-Conceptional design
-As highlighted in Figure 71 the user will get a notification about the updated availability of his product at Login at the CEMS GFMS Portal. The notification will inform him/her about the temporal aspect of the ordered product and the access options (e.g. download link, map server access for WMS-T and if ordered some pre-analysis).
+As highlighted in the figure below the user will get a notification about the updated availability of his product at Login at the [[INTRODUCTION | '''GFM''']] Portal. <br>

← Older revision		Revision as of 14:13, 4 March 2021
Line 1:		Line 1:
		+	[[File:example7.jpg\|right\|100px\|caption]]
	[[GFMS \| [Home]]] - [[DATA ACCESS \| [DATA ACCESS]]]		[[GFMS \| [Home]]] - [[DATA ACCESS \| [DATA ACCESS]]]
	----		----