Understanding object storage and organisation

Ask the Community
,
1

Hi,

I was playing around with a new object I defined in the Ontology manager. I didn’t have any pre-existing data for it so I started with an empty datasource, but I created new instances of this object through my workshop app.

I was suprised to find that although these new instances persist in my list section (and also in object explorer), my original backing datasource is still empty. I expected these instances to be written to my datasource.

I also found that my list section in workshop locally groups my new objects in an Object Set. In object explorer this structure is lost, I can’t see which Object Set each instance belongs to.

I know that data and objects are different concepts in Foundry, and that objects are stored in the Object Layer of the Ontology, but I’m still confused about how object storage and organisation works in practice. How can I keep track of object instances users create?

Thanks!

2

Hi!

What you are seeing is correct behaviour. Your backing dataset is used as a starting point, and then you are editing what is stored in the ontology through object edits.

If you want a dataset that contains your object edits you can set up a materialization, which is essentially a dataset that is exported from the ontology and contains your objects with any edits made.

Regarding the object sets; Any object sets you create in Workshop are local to Workshop only, and you wont be able to see these anywhere else. Object sets are generally used in only one place (i.e. not shared across applications).

I hope that made sense! Feel free to ask if you have further questions :slight_smile:

  • Eirik