How to set up multiple object types in a schema

[Sandra Lawrence]

I have set up a basic schema with object types.  Some are sub-object types to others.  I do not know when I should establish a reference directly into an object type to access data in another .  Here is a simple example.

Organization

-- Program  (programs are assigned to an Organization)

----- Project  (projects are assigned to a program)

Employees  (are assigned to a project)

Contract   (are associated with a project); there can be more than one contract to a project

-- Vendor    (each contract has one vendor)

----- Contacts (there are many contacts to a vendor) 

How do I set up object types and relationships if I want to see:

1. For one program, show me all the projects, their associated contracts with each ?

[Kris Dewachter · Accepted solution]

Hi @Sandra Lawrence ,

I think your sub-object types setup is incorrect in this case. "Program" and "Project" don't seem to be sub-object types.

You use Sub-object types when they share attributes from the main object. For example:

- Vehicle

-- Car

---- City Car

---- 4x4 Car

-- Bike

-- Bicycle

In your case, i don't think "Program" shares any information with an "Organisation". So i would setup all your object types as main object types (all on the main level).

And you can link the objects via the attributes (Type onject).

For example:

In "Program", you can have an attribute "Organization", which links to the "Organization" object type. 

Best regards,

Kris

[Sandra Lawrence]

Kris!  So thankful for this reply!  I am just trying to learn all this via youtube videos - LOL.

Just to clarify and make sure I am understanding - wanted to explain a bit more on my Program to Project relationship, because in my mind (LOL) they do have a relationship.  But, maybe that relationship doesn't have to be shown in a tree structure of object to sub-objects.

Each program can have one or more projects.   So like your car example, we will have software projects, system projects, etc.

Am I looking at this the wrong way?

[Kris Dewachter]

@Sandra Lawrence ,

"Object relations" and "parent-child object types" are something completely different. 

In your case, a "Program" can contain multiple "Projects". Since a "Program" is something different than a "Project", they can not be setup as a parent-child object schema. This needs to be defined as a relation and can be configured with attributes. 

In your example, there can be multiple types of "projects". That could be defined in a parent-child object type setup. Ex.

- Project

-- Software Project

-- System Project

-- ...

A "Project" will have a number of attributes (ex. Project Name, Budget, ...). A "Software" or "System" project will inherit these attributes from the parent project type. 

Best regards,

Kris

[Sandra Lawrence]

Again - a wealth of knowledge!  Thank you so very much.  Let me ask you one more question:  When adding attributes that have a Type = Object, what is the impact of selecting the right "additional Value" (for e.g., belongs to, or dependency)?

And if you know of any particular resources that could explain in more detail the concept of Object relations vs. Parent-chhild object types....I'd be in geek heaven!

Thank you!

Sandy

[Kris Dewachter]

Hi @Sandra Lawrence 

From a functionality point of view, there is no specific impact on setting the "Additional value". For relationships, it just indicates the kind of relation for visualisation. 

Ex.

• User X "is owner of" laptop Y
• Project X "belongs to" Program Y 

I can recommend these 2 articles from @Derek Fields _RightStar_ in the Atlassian Community:

• Using Insight as an Object-Oriented Database (Part 1)
• Using Insight as an Object-Oriented Database (Part 2)

Hope this helps.

Best regards,

Kris

[Sandra Lawrence]

Wonderful - thank you very much!