Build with Us | Deep Dive: Your first Ontology

preview_player
Показать описание

All data shown in this tutorial is notional data created for teaching purposes.

*About Ontologize*
We build teams of Palantir experts. Ontologize is a team of former Palantir engineers who are passionate about teaching. We are an official Palantir Partner focused on helping Palantir's customers and partners scale their Foundry & AIP deployments.

#aip #foundry #palantir

00:00 Intro
01:11 Setting up your Project and Folder
03:26 Ontology Basics: Building your objects
18:43 Exploring the Ontology
23:42 Conclusion
Рекомендации по теме
Комментарии
Автор

Been working in Foundry for 2 days running through exercises, overall you guys do a great job. I think tutorials like this are great for giving us a glimpse into what's possible, but a longer tutorial that goes end-to-end and has meaningful complexity across data cleaning, ontology creation, and app development would be awesome. I don't care how long the video is, I"m just here to build and understand waht's possible after I grab the basics. Thanks again.

ehhalexx
Автор

Great and detailed as always. In 11:05 I didn't know that one can create or edite ontolgoy objectsets directly in pipelinebuilder. Could you also use time to demonstratte "Allow edits to objects of this type"

madfiskmad
Автор

Great video for understanding relationship building, so what different made in this application that cant done in other applications, and what are the benefit of making this?

PANDURANG
Автор

Thanks for another great walk through. I did this tutorial a few weeks ago. Would have been helpful if I watched this video and walked through it, much better explanations than the written tutorial! I'd like to see a tutorial on restricted views. I've watch the securing PII video on this channel (awesome video) but would like to know how to use restricted views and use cases. thanks!

dkfresh
Автор

What are some reasons you would want to create these inside or outside of pipeline builder? I learned the hard way certain edit permissions need to be explicit defined but figure there must be a reason for both options

ChristopherKnight-nomad