You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by sh...@apache.org on 2022/05/25 11:43:53 UTC
[unomi] branch master updated: [UNOMI-564] - Misinformation in some descriptions in online site docs (#409)
This is an automated email from the ASF dual-hosted git repository.
shuber pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/unomi.git
The following commit(s) were added to refs/heads/master by this push:
new f2972a186 [UNOMI-564] - Misinformation in some descriptions in online site docs (#409)
f2972a186 is described below
commit f2972a18629223c283e3df8b017a549a741e0da7
Author: Woonsan Ko <wo...@users.noreply.github.com>
AuthorDate: Wed May 25 20:43:48 2022 +0900
[UNOMI-564] - Misinformation in some descriptions in online site docs (#409)
* trivial fixes in manual
* UNOMI-564 : fixing community links
* UNOMI-564 : periods to re-run integ-tests
---
manual/src/archives/1.5/asciidoc/connectors/connectors.adoc | 2 +-
manual/src/archives/1.5/asciidoc/datamodel.adoc | 6 +++---
manual/src/archives/1.6/asciidoc/connectors/connectors.adoc | 2 +-
manual/src/archives/1.6/asciidoc/datamodel.adoc | 6 +++---
manual/src/main/asciidoc/connectors/connectors.adoc | 2 +-
manual/src/main/asciidoc/datamodel.adoc | 6 +++---
wab/src/main/webapp/index.html | 2 +-
7 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc b/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc
index b15e5ca08..4d9ac8200 100644
--- a/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc
+++ b/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc
@@ -22,4 +22,4 @@ Apache Unomi provides the following connectors:
==== Call for contributors
We are looking for help with the development of additional connectors. Any contribution (large or small) is more than
-welcome. Feel free to discuss this in our link:http://unomi.apache.org/community.html[mailing list, window="_blank"].
\ No newline at end of file
+welcome. Feel free to discuss this in our link:http://unomi.apache.org/community/[mailing list, window="_blank"].
\ No newline at end of file
diff --git a/manual/src/archives/1.5/asciidoc/datamodel.adoc b/manual/src/archives/1.5/asciidoc/datamodel.adoc
index 0d97d4306..8f0485735 100755
--- a/manual/src/archives/1.5/asciidoc/datamodel.adoc
+++ b/manual/src/archives/1.5/asciidoc/datamodel.adoc
@@ -194,7 +194,7 @@ Inherits all the fields from: <<Item>>
|===
| *Field* | *Type* | *Description*
-| eventType | String | Contains an identifier for the field type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
+| eventType | String | Contains an identifier for the event type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
| sessionId | String | The unique identifier of a Session object
@@ -415,7 +415,7 @@ Inherits all the fields from: n/a
| typeIdentifier | String | This is a unique consent type identifier, basically a unique name for the consent. Example of such types might include: “newsletter”, “personalization”, “tracking”.
-| status | GRANTED / DENIED / REVOKED | A copy of the profile associated with the session
+| status | GRANTED / DENIED / REVOKED | The type of status for this consent
| statusDate | Date | The date (in ISO 8601 format) at which the current status was set
@@ -1066,7 +1066,7 @@ Inherits all the fields from: <<MetadataItem>>
|===
| *Field name* | *Type* | *Description*
-| elements | ScoringElement array | A ScoringElement is composed of:* A Condition* A Score increment valueEach element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score
+| elements | ScoringElement array | A ScoringElement is composed of: a Condition and a score value to increment. Each element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score.
|===
diff --git a/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc b/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc
index b15e5ca08..4d9ac8200 100644
--- a/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc
+++ b/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc
@@ -22,4 +22,4 @@ Apache Unomi provides the following connectors:
==== Call for contributors
We are looking for help with the development of additional connectors. Any contribution (large or small) is more than
-welcome. Feel free to discuss this in our link:http://unomi.apache.org/community.html[mailing list, window="_blank"].
\ No newline at end of file
+welcome. Feel free to discuss this in our link:http://unomi.apache.org/community/[mailing list, window="_blank"].
\ No newline at end of file
diff --git a/manual/src/archives/1.6/asciidoc/datamodel.adoc b/manual/src/archives/1.6/asciidoc/datamodel.adoc
index 0d97d4306..8f0485735 100755
--- a/manual/src/archives/1.6/asciidoc/datamodel.adoc
+++ b/manual/src/archives/1.6/asciidoc/datamodel.adoc
@@ -194,7 +194,7 @@ Inherits all the fields from: <<Item>>
|===
| *Field* | *Type* | *Description*
-| eventType | String | Contains an identifier for the field type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
+| eventType | String | Contains an identifier for the event type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
| sessionId | String | The unique identifier of a Session object
@@ -415,7 +415,7 @@ Inherits all the fields from: n/a
| typeIdentifier | String | This is a unique consent type identifier, basically a unique name for the consent. Example of such types might include: “newsletter”, “personalization”, “tracking”.
-| status | GRANTED / DENIED / REVOKED | A copy of the profile associated with the session
+| status | GRANTED / DENIED / REVOKED | The type of status for this consent
| statusDate | Date | The date (in ISO 8601 format) at which the current status was set
@@ -1066,7 +1066,7 @@ Inherits all the fields from: <<MetadataItem>>
|===
| *Field name* | *Type* | *Description*
-| elements | ScoringElement array | A ScoringElement is composed of:* A Condition* A Score increment valueEach element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score
+| elements | ScoringElement array | A ScoringElement is composed of: a Condition and a score value to increment. Each element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score.
|===
diff --git a/manual/src/main/asciidoc/connectors/connectors.adoc b/manual/src/main/asciidoc/connectors/connectors.adoc
index b15e5ca08..4d9ac8200 100644
--- a/manual/src/main/asciidoc/connectors/connectors.adoc
+++ b/manual/src/main/asciidoc/connectors/connectors.adoc
@@ -22,4 +22,4 @@ Apache Unomi provides the following connectors:
==== Call for contributors
We are looking for help with the development of additional connectors. Any contribution (large or small) is more than
-welcome. Feel free to discuss this in our link:http://unomi.apache.org/community.html[mailing list, window="_blank"].
\ No newline at end of file
+welcome. Feel free to discuss this in our link:http://unomi.apache.org/community/[mailing list, window="_blank"].
\ No newline at end of file
diff --git a/manual/src/main/asciidoc/datamodel.adoc b/manual/src/main/asciidoc/datamodel.adoc
index 0d97d4306..8f0485735 100755
--- a/manual/src/main/asciidoc/datamodel.adoc
+++ b/manual/src/main/asciidoc/datamodel.adoc
@@ -194,7 +194,7 @@ Inherits all the fields from: <<Item>>
|===
| *Field* | *Type* | *Description*
-| eventType | String | Contains an identifier for the field type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
+| eventType | String | Contains an identifier for the event type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
| sessionId | String | The unique identifier of a Session object
@@ -415,7 +415,7 @@ Inherits all the fields from: n/a
| typeIdentifier | String | This is a unique consent type identifier, basically a unique name for the consent. Example of such types might include: “newsletter”, “personalization”, “tracking”.
-| status | GRANTED / DENIED / REVOKED | A copy of the profile associated with the session
+| status | GRANTED / DENIED / REVOKED | The type of status for this consent
| statusDate | Date | The date (in ISO 8601 format) at which the current status was set
@@ -1066,7 +1066,7 @@ Inherits all the fields from: <<MetadataItem>>
|===
| *Field name* | *Type* | *Description*
-| elements | ScoringElement array | A ScoringElement is composed of:* A Condition* A Score increment valueEach element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score
+| elements | ScoringElement array | A ScoringElement is composed of: a Condition and a score value to increment. Each element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score.
|===
diff --git a/wab/src/main/webapp/index.html b/wab/src/main/webapp/index.html
index 56363a767..93a0f25a6 100644
--- a/wab/src/main/webapp/index.html
+++ b/wab/src/main/webapp/index.html
@@ -79,7 +79,7 @@
</li>
<li>Try out some <a href="http://unomi.apache.org/manual/latest/index.html#_integration_samples"
target="_blank">samples</a></li>
- <li>Join <a href="http://unomi.apache.org/community.html" target="_blank">Apache Unomi's mailing lists</a></li>
+ <li>Join <a href="http://unomi.apache.org/community/" target="_blank">Apache Unomi's mailing lists</a></li>
<li>Star the project on Github <!-- Place this tag where you want the button to render. -->
<a class="github-button" href="https://github.com/apache/incubator-unomi" data-icon="octicon-star"
data-show-count="true" aria-label="Star apache/incubator-unomi on GitHub">Star</a>