Skip to content

Commit dcb6ca5

Browse files
authored
Merge pull request #316 from ipbabble/add-emerging-disease-detection
fixed date and edited the google help
2 parents 896abef + 85dead2 commit dcb6ca5

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

content/patterns/emerging-disease-detection/_index.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Emerging Disease Detection
3-
date: 2023-10-01
3+
date: 2023-09-23
44
validated: false
55
summary: This pattern is based on a demo implementation of an automated data pipeline for sepsis analysis previously developed by Red Hat.
66
products:
@@ -9,11 +9,11 @@ products:
99
industries:
1010
- medical
1111
aliases: /emerging-disease-detection/
12-
pattern_logo: emerging-disease-detection.png
12+
// pattern_logo: emerging-disease-detection.png
1313
links:
1414
install: getting-started
1515
arch: https://www.redhat.com/architect/portfolio/architecturedetail?ppid=6
16-
help: https://groups.google.com/g/validatedpatterns
16+
help: https://groups.google.com/g/hybrid-cloud-patterns
1717
bugs: https://github.com/validatedpatterns/emerging-disease-detection/issues
1818
ci: edd
1919
---

content/patterns/emerging-disease-detection/getting-started.adoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,15 @@ aliases: /emerging-disease-detection/getting-started/
1010

1111
== Prerequisites
1212

13-
. An OpenShift cluster (Go to https://console.redhat.com/openshift/create[the OpenShift console]). Cluster must have a dynamic StorageClass to provision PersistentVolumes. See also link:../../emerging-disease-detection/cluster-sizing[sizing your cluster].
13+
. An OpenShift cluster (Go to https://console.redhat.com/openshift/create[the OpenShift console]). Cluster must have a dynamic StorageClass to provision PersistentVolumes.
14+
// See also link:../../emerging-disease-detection/cluster-sizing[sizing your cluster].
1415
. A GitHub account (and a token for it with repositories permissions, to read from and write to your forks)
1516

1617
For installation tooling dependencies, see link:https://validatedpatterns.io/learn/quickstart/[Patterns quick start].
1718

1819
The use of this pattern depends on having a Red Hat OpenShift cluster. In this version of the validated pattern
19-
there is no dedicated Hub / Edge cluster for the *Emerging Disease Detection* pattern. This single node pattern can be extend as a managed cluster(s) to a central hub. See link:../../emerging-disease-detection/ideas-for-customization[ideas for customization.]
20+
there is no dedicated Hub / Edge cluster for the *Emerging Disease Detection* pattern. This single node pattern can be extend as a managed cluster(s) to a central hub.
21+
// See link:../../emerging-disease-detection/ideas-for-customization[ideas for customization.]
2022

2123
If you do not have a running Red Hat OpenShift cluster you can start one on a
2224
public or private cloud by using link:https://console.redhat.com/openshift/create[Red Hat's cloud service].

0 commit comments

Comments
 (0)