Need an entity to map with "Known Error"

[sk-cool]

Known Error's are represented in ITOP with following set of attributes. We do not have a corresponding entity in GraphIT.

Attributes :
Name
Customer
Related Problem (Edge with Problem)
Error Code
Domain
Vendor (Edge)
Model
Version
Symptom
Root Cause
Workaround
Solution
Edge with CI's (Mars nodes).
Edge with Attachments.

We need an entity to represent this along with free attributes.

Thanks,
Satish

[conofre]

Proposal:
Creation of new entity "Error".
All needed attributes could be instantiated as free attributes.
In this context, please indicate the needed connections in the following manner:

VerbName1:
(EntityFrom) -> (EntityTo)

VerbName2:
(EntityFrom) -> (EntityTo)

Tks.

[sk-cool]

Hi Catarina,

We need the following type of edges with ogit/Error

`
Incoming edges --
ogit/isRelatedTo <= ogit/ITSM/Ticket
ogit/isRelatedTo <= ogit/ITSM/Problem
ogit/isRelatedTo <= ogit/ITService/Order
ogit/isRelatedTo <= ogit/ITSM/ChangeRequest
ogit/isRelatedTo <= ogit/ITSM/Incident
ogit/belongsTo <= ogit/ITSM/Attachment

Outgoing edges --
ogit/isRelatedTo => arago/MARSNode
`

Please let me know if you need anything else.

Thanks,
Satish

[conofre]

Hi Satish

verb isRelatedTo will be changed to "relates"

Summary of changes:

New entity "Error"

Error -> relates Ticket
Error -> relates Problem
Error -> relates Order
Error -> relates ChangeRequest
Error -> relates Incident
Error -> relates MARSNode

Why the edge to the Attachment?

Does this seem ok?

Tks.

[sk-cool]

Hi Catarina,

With respect to "relates", is this change happening for only ERROR or all across other entities/relationships?

With respect to Attachment, User can attach a log file with the error description. ITOP allows it to do so.

Thanks,
Satish

[conofre]

Hi Satish,
OGIT ontology is currently being reviewed and verb "isRelatedTo" will disappear and an equivalent verb "relates" will be available. All the associated changes should be available in some weeks.
In order for you to use to do less future adaptations to the new reviewed ontology, you could use the new verb. Let me know when you will start testing the Error entity creation so that we could complete the creation of:

New entity "Error"
edges to verb "relates":

Error -> relates Ticket
Error -> relates Problem
Error -> relates Order
Error -> relates ChangeRequest
Error -> relates Incident
Error -> relates MARSNode
Error -> relates Attachment

[sk-cool]

Our code is almost ready. We will start testing once you provide the edge.
On May 6, 2015 6:36 PM, "conofre" [email protected] wrote:

Hi Satish,
OGIT ontology is currently being reviewed and verb "isRelatedTo" will
disappear and an equivalent verb "relates" will be available. All the
associated changes should be available in some weeks.
In order for you to use to do less future adaptations to the new reviewed
ontology, you could use the new verb. Let me know when you will start
testing the Error entity creation so that we could complete the creation of:

New entity "Error"
edges to verb "relates":

Error -> relates Ticket
Error -> relates Problem
Error -> relates Order
Error -> relates ChangeRequest
Error -> relates Incident
Error -> relates MARSNode
Error -> relates Attachment

—
Reply to this email directly or view it on GitHub
#165 (comment).

[conofre]

The changed ontology should be ready in couple days. After it we could advance to the implementations of the Error entity and associated edges.

[sk-cool]

Thanks.
On May 7, 2015 6:52 PM, "conofre" [email protected] wrote:

The changed ontology should be ready in couple days. After it we could
advance to the implementations of the Error entity and associated edges.

—
Reply to this email directly or view it on GitHub
#165 (comment).