Building a knowledge graph

What is a Dataset?

About the API

Managing users

Team roles

Creating a Dataset

Simple vocabularies

Concept types

Subclassing and inheritance

Data types

Search facets

What is a Concept?

Importing data

Viewing and modifying a Dataset schema

Identifiers

How to link Concepts

Authentication

Webhooks

Searching a Dataset

Merging Concepts

Query parameter reference

Deleting Concepts

Advanced Search

Custom validation rules

Federated Search

Making a request

If your data has more complex relationships than simple lists or collections, it is useful to design a domain model as it will help your define your Datasets.<h2>Designing a domain model</h2>
	 You can create a domain model on paper or with a drawing tool such as LucidChart, Visio or OmniGraffle. It should define all your Concepts (types/classes) and the relationships between them (their properties).&nbsp;
	 In the following Food domain model, the blue ovals represent your Concept types and the arrows the relationships between them – their properties. The white rectangle signifies a primitive datatype. So a Recipe, for example, has a chef property of type Person, a forDish property (type&nbsp;Dish) and a steps property (text - a primitive datatype).
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6113d8c06ffe270af2a97d9c/file-CXxZylDdx8.png" style="width: 511px;">
	 For more information see <a href="https://support.datagraphs.io/knowledge-base/managing-data/what-is-a-dataset">What is a Dataset?</a> and <a href="https://secure.helpscout.net/knowledge-base/managing-data/what-is-a-concept">What is a Concept?</a>.&nbsp;We have also created a video that walks you through this process <a href="https://datagraphs.com/demos/how-to-setup-your-data-sets" target="_blank">here</a>.<h2>Build your Datasets</h2>
	 With a well defined domain model you are in a position to create your Concept types and their relationships. You can do this in one or more Datasets depending on how you prefer to organise and manage your data. Although the Datasets themselves confer no semantic meaning on your domain model, they allow you to collect concepts (entities) of similar types together making them easier to manage. On the other hand, it is perfectly possible to build your entire knowledge graph in a single Dataset.&nbsp;<h4> 1. Create leaf Concept types</h4>
	 Start by creating&nbsp;the leaf nodes –&nbsp;those types that have no links outward to other types. In the Food domain model above, the leaf types are Occasion, Ingredient, Cuisine and Person.&nbsp;<h4> 2. Creating relationships</h4>
	 Once the leaf types are defined, you can create their related Concept types. In our example, Recipe has a chef property whose type is Person, so creating a complete&nbsp;Recipe type wouldn't be possible without defining Person first. Of course you can still come back and edit a type later to add a property if you did not create the dependant type first (the Person in this example).
	 In Data Graphs the relationship between two types is created&nbsp;automatically&nbsp;when one&nbsp;type is assigned to&nbsp;the property of another, in this case when Person is assigned to the chef property of Recipe.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6113ddc3b37d837a3d0e2c9d/file-vAR7Y8ZcCR.png" style="width: 525px;"><h4> 3. Define non-relational properties (primitive or datatype properties)</h4>
	 These are properties with standard primitive datatypes (text, date, keyword, boolean etc). You can find definitions of these primitives <a href="https://support.datagraphs.io/knowledge-base/managing-data/data-types">here</a>. In this case, the steps property is of type text.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6113de5864a230081ba1e357/file-tda0XHL3th.png" style="width: 508px;"><h4>4. Review the domain</h4>
	 Once you have created all your types and their properties, you can see a visualisation of the domain model in Data Graphs <a href="https://app.datagraphs.io/account/_domain-model">here in the app</a> and check to see if it aligns with your own domain model.<h4> 5. Import your data</h4>
	 You can import your data in 3 ways:<ul>
	
<li>Create Concepts manually from the&nbsp;Add New Concepts&nbsp;page using the Data Graphs UI</li>	
<li>Upload CSVs from the&nbsp;Import Data&nbsp;page in a Dataset</li>	
<li>Create Concepts via the <a href="https://support.datagraphs.io/api-docs">Data Graphs API</a> - either individually or in bulk.</li></ul>
	 For more information see <a href="https://support.datagraphs.io/knowledge-base/managing-data/importing-data">Importing data</a>.

Data Graphs' information management is based around the Dataset. This is where you define your classes, or types, and the relationships between them, and where you import your data, or Concepts.
	 This simplest way to use a Dataset is to create one per type. This approach is suitable for data comprising lists or collections of things.&nbsp;For example, in a geographical domain including lists&nbsp;of countries, flags and governments, your Datasets would be Countries, Flags and Governments, with each defining the relevant type and its properties. In its simplest form, a vocabulary in a Dataset might be just a list of Key–Label pairs.
	 However, if you are working with more complex relationships, eg in well documented a knowledge graph, then you should consider carefully <a href="https://support.datagraphs.io/knowledge-base/get-started/building-a-knowledge-graph">how you define your types among your Datasets</a>.
	 For more information see <a href="https://support.datagraphs.io/knowledge-base/managing-data/what-is-a-dataset">What is a Dataset?</a> and <a href="https://support.datagraphs.io/knowledge-base/managing-data/what-is-a-concept">What is a Concept?</a>.<h2>Building a simple dataset</h2>
	 You can do this in 4 simple steps:<h4>1. Create a Dataset</h4>
	 Click on Create New Dataset&nbsp;on the <a href="https://app.datagraphs.io/_account/_project" target="_blank">datasets page</a>.&nbsp;Give your Dataset a name and decide whether it should be public or private.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60718690f8c0ef2d98df10f0/file-aAshbuVw7b.png" style="width: 587px;"><h4>2. Add a&nbsp;Concept&nbsp;type&nbsp;</h4>
	 Create your own custom concept type or choose one of Data Graphs' pre-created templates.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60718ec34466ce6ddc5f3490/file-ptnhmI8YEs.png" style="width: 583px;"><h4>3.&nbsp;Define Custom Type properties</h4>
	 Every Data Graphs type has an id and a label as a minimum but you can add as many others as required by clicking the + symbol on the right hand side of the last property in the list.
	 Note: if your entities come with their own ids, you should select Manual Identifiers. Alternatively, Data Graphs will create Automatic Identifiers for you.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6113d6f0766e8844fc34f778/file-ATnTHv9KFp.png" style="width: 673px;"><h4> 4. Add your data&nbsp;</h4>
	 You can do this 3 ways:<ul>
	
<li>Create a Concept manually from the&nbsp;Add New Concepts&nbsp;page in the Data Graphs app</li>	
<li>Upload a CSV from the&nbsp;Import Data&nbsp;page for the Dataset</li>	
<li>Load Concepts via the <a href="https://support.datagraphs.io/api-docs">Data Graphs API</a> either individually or in bulk</li></ul>
	 For more information see <a href="https://support.datagraphs.io/knowledge-base/managing-data/importing-data">Importing data</a>.
	 <a href="https://support.datagraphs.io/api-docs#/paths/~1{your-account-key}~1{datasetId}/post" target="_blank"></a>

Get started

A Dataset is a namespace or bucket for collecting or grouping Concepts together.
	 Data Graphs' project homepage shows all the project's Datasets as cards where&nbsp;you can see the number and types of Concepts each Dataset contains.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/606c6fa98996210f18bd0740/file-T1XEAorhC7.png" alt="" style="float: left; width: 349px; margin: 0px 10px 10px 0px;">
	 Datasets provide two main functions:1. Information management - a way to efficiently or conveniently manage data2. Security - a way to make some of your data public or privately accessible to applications at integration time<h2></h2><h2></h2><h2>Information management</h2>
	 A Dataset does not add any semantic value to your knowledge graph, but does provide a nice way for you to group data together to improve its manageability.
	 For example, you may wish to put all Concepts of one type into its own Dataset, such that a Dataset of Organizations would all be collected together. Alternatively you may have defined a Person&nbsp;type and create one Dataset to hold all politicians and another Dataset to hold all sports people.
	 * Remember - you can still federate across all your Datasets. Putting the same type of Concepts into multiple datasets does not prevent you from searching and navigating data by type across your entire knowledge graph.<h2>Security</h2>
	 A Dataset can be declared as public or private. This defines how the data within the Dataset is accessed by the Data Graphs API.&nbsp;
	 Private - A Dataset declared as private requires the use of OpenID credentials. This means your data in this Dataset is secure and can only be accessed via an authenticated user request. Machine-2-Machine OpenID / OAuth credentials can be setup in the Application section of the project management settings.
	 Public - A Dataset declared as public can be accessed using just your API key. These data requests can be made without authentication.

To create a Dataset click on the Create New Dataset tile on your current project's <a href="https://app-datagraphs.io/_account/_project">datasets page</a>. You will be guided through a set of steps in which you define the types of Concepts you want your Dataset to contain.<h2>Step 1: Dataset settings</h2>
	 Choose an appropriate name for the Dataset, an example would be to name it after the collection of&nbsp;Concepts&nbsp;that it will contain. You need to name it unambiguously. The namespace for the&nbsp;Dataset&nbsp;is a URN and is set automatically – urn:test:countries in the example below. The namespace is also important as this will be used as part of the API endpoint URL if you want to access this Dataset via the API.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60718690f8c0ef2d98df10f0/file-aAshbuVw7b.png">
	 Choose whether the Dataset is public or private with respect to API access. A public Dataset can be accessed using the API from any client on the internet using an API key. A private Dataset can only be accessed using the API with OAuth / OpenID authentication.&nbsp;
	 When you are happy with the main settings, click Add Types to configure the Concept types you want the Dataset to contain.<h2>Step 2: Add a Concept type</h2>
	 Next you must add one or more types of&nbsp;Concepts&nbsp;that you want to include in the&nbsp;Dataset. We call this the Dataset Schema. You don't have to be exhaustive at this point as you can edit your schema at any stage before you add your data.
	 Choose the first type you want to add, either selecting a type you have already defined or one of Data Graphs' own types, or create a brand new type. In the example below we are naming a new type Country as we want to include Country&nbsp;Concepts&nbsp;in the Dataset. When happy, click the Add Type button.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60718ec34466ce6ddc5f3490/file-ptnhmI8YEs.png"><h2>Step 3: Customise the type</h2><h3>Subclassing</h3>
	 Now you need to choose if this&nbsp;Concept&nbsp;type is a sub-class of some existing type or not. If it is a sub-class, you can select the Parent Type from the list of existing types. If you do choose a parent type, you can then choose to include the properties from the parent&nbsp;Concept&nbsp;type in this new (child) type&nbsp;–&nbsp;typically you should choose to inherit the parent&nbsp;Concept&nbsp;properties.<h3>Automatic or manual identifiers</h3>
	 You must choose whether to use manual or automatic identifiers. If you choose manual, for every&nbsp;Concept&nbsp;of this type you create you will need to supply an identifier that&nbsp;unique with respect to the class / type of Concept. If you choose automatic you will&nbsp;not need to supply identifiers for each&nbsp;Concept, and Data Graphs will generate a globally unique identifier for you.<h3>Defining the Concept properties</h3>
	 Now add the properties to your Concepts schema. By default each&nbsp;Concept&nbsp;has an id and a label. The id property name cannot be changed but you can change the label property name to something else (eg&nbsp;name&nbsp;is a good alternative).
	 Now you can define the custom properties that will describe each instance of your Concept. In our&nbsp;example&nbsp; Country has capitalCity, isoCode, flagImage, lat, longitude and borders properties.
	 For each property you must choose its data type. Property data types can be primitive types like text, decimal, integer and&nbsp;boolean, or specialised data types like latitude / longitude. Alternatively&nbsp;you can make a relationship property that references a different Concept type defined in this or another&nbsp;Dataset.
	 For each property, you can choose modifiers that&nbsp;describe whether the property:<ul>
	
<li>is optional – you do not need to supply a value for an optional field when editing data</li>	
<li>is identifier&nbsp;–&nbsp;if you have selected manual identifiers, you may select one custom property as the field that will uniquely identify Concepts of this type. You do not need to choose a field to be the identifier, and instead you can just use the default id field if this is preferable. If you do define an identifier property, the property datatype must be a keyword or an integer.</li>	
<li>allow multiple – indicates if the property allows multiple values (an array).</li>	
<li>preview image – if you have selected an imageURL datatype, you can choose if this property holds a canonical preview image of the Concept.</li>	
<li>is nested –&nbsp;if you have defined a relationship property that references another Concept, you can optionally choose this to be nested inside the Concept itself. This allows you to create complex data structures within the concept. A more typical scenario is simply to link to Concepts elsewhere in your Datasets (the knowledge graph and linked-data pattern). In this case leave this option unchecked.</li></ul>
	 Our Country example uses manual identifiers, which means a Concept should either use the standard&nbsp;id property as its identifier or use a newly defined property. In this case we have defined an isoCode field and marked it as the identifier. You can see the other custom properties we have chosen for our Country type below:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/607198a68af76a714bfd5e50/file-ocgLyD0nLs.png">
	 When you are happy with this Concept schema definition, click Review Types.&nbsp;<h2>Step 4: Review types and save the Dataset</h2>
	 Finally you get to review the&nbsp;Concept&nbsp;types you have defined for this Dataset, you can edit, remove, or add more types from this final screen. If you choose to add another type, you will repeat Step 2 and 3 for the additional&nbsp;Concept&nbsp;type.
	 When you have defined all your types, click the Save Dataset button and Data Graphs will create an empty Dataset ready for you to add Concepts.

Every&nbsp;Concept&nbsp;in your Data Graphs account is assigned a type or class by you. The type describes the semantics of the class of&nbsp;Concept&nbsp;(such as Person, Animal, Organisation, Football Team etc).&nbsp;
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/607444244466ce6ddc5f397b/file-XWmWcDtME9.png" style="width: 329px; float: left; margin: 0px 10px 10px 0px;" alt="">The&nbsp;Concept&nbsp;type confers characteristics upon your data. It also enables you to query, navigate and facet data by type. For example, in the federated search screen there is a type facet presented by default – as shown in the screenshot.
	 This type facet shows how many&nbsp;Concepts&nbsp;of each type exist in your Datasets, entire knowledge graph or reference data.
	 By selecting one of the types you can restrict the search results to only&nbsp;Concepts of that type, regardless of which Dataset the&nbsp;Concepts might be present in.<h2></h2><h2>Concept relationships</h2>
	 Concept types are used when creating a property that references or links to another&nbsp;Concept&nbsp;in your domain model. If you specify a specific type in this relationship, Data Graphs understands the range semantics of the relationship and is able to validate and constrain the Concept editor to only allow&nbsp;Concepts of the type you selected.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60745c91f8c0ef2d98df1693/file-rVOKHCiv9r.png" style="width: 565px;"><h2>Managing Concept types</h2>
	 While you can view and manage&nbsp;Concept&nbsp;types within each Dataset schema, there is a dedicated screen for viewing and managing all&nbsp;Concept&nbsp;types accessible from the main account menu in the navbar called Manage Types. This screen lists the types across all your Datasets and lets you view the class hierarchy you have created through subclassing.
	 You can delete an unused Concept&nbsp;type from right hand side bar of the Manage Types screen:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60745b618996210f18bd25f6/file-Dk9XGAnvLR.png">

Sometimes the Concept type you want to give your data shares a common pattern with other types. In Data Graphs it is possible to make types that share some common parent type. This is sometimes referred to as classes being a subclass of another class.
	 This allows you to share common properties from the parent class and to facet on the child and parent class simultaneously.
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608134c68af76a714bfd9c82/file-OXyBuqMoUc.png" style="width: 254px; float: left; margin: 0px 10px 10px 0px;" alt="">For example, you might have a Vehicle Concept type that has properties for name and manufacturer. You could then define more specific&nbsp;Concept&nbsp;types for planes and motor vehicles. These might have their own set of specific properties – wing length for planes or transmission type for motor vehicles – but they will inherit the properties of the Vehicle&nbsp;Concept&nbsp;type as well.
	 In addition, when you search for anything made by a manufacturer, your results will show any type of vehicle – plane or motor vehicle.
	 
	
	 
	<h2> Planning your Concept type hierarchy</h2>
	 If you have already designed your model, it is useful to define Concept types related by subclassing and inheritance in Data Graphs from the top down. Start with the parent type and work down to define more specific&nbsp;Concept&nbsp;types. When it comes to creating a new type it is as simple as selecting from the existing parent types in the drop down list. By defining your parent types first they will be available to select when it comes to defining more specific&nbsp;Concept&nbsp;types.<h2>Creating subclasses</h2>
	 You create a subclass or a sub-type when creating a&nbsp;Concept&nbsp;type schema in a Dataset. After naming your&nbsp;Concept, you have the option of choosing a 
	Parent Type for the&nbsp;Concept&nbsp;you are defining.
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608675bef8c0ef2d98df609a/file-AL51K2sLxl.png">
	 By selecting the 
	Include {Type} properties option, your new subclass will inherit (re-use) the properties from the parent type. This is most likely what you will need to.<h2>Managing types</h2>
	 The 
	<a href="https://app.datagraphs.io/account/_manage-types">Manage Types</a> screen allows you to see a visual representation of your current type hierarchy. This view is accessible by selecting&nbsp;Manage Types&nbsp;in the main account menu in the navbar. Within this screen you can remove a type that you no longer require or have created incorrectly in your type hierarchy.
	<img src="https://lh6.googleusercontent.com/AqGXF5eT55DyiGM8rAvynSRwGGUCbhxm4YScCESUXUXS7__56-YULmFBSwm2OOW8BwmRyhNZm8NWGS0Wi926G3XcZo3Irfgm-JPSF_UjmgIJfs3ZVHiBvSqaofO9HZqrmAS1y70U" style="margin-top: 0px; margin-left: 0px;" width="624" height="289"><h2>Transitive class inference</h2>
	 When you create a subclass type, Concept relationships become class-structure aware, with transitive inference. When a&nbsp;Concept&nbsp;property defines a relationship to another&nbsp;Concept&nbsp;type/class, Data Graphs allows you to select&nbsp;Concept&nbsp;instances of that type and all its subclasses.&nbsp;
	For example, if you create a class FootballTeam that is a sub-class of Organization, and you then create a property on another Concept&nbsp;of type&nbsp;Organization,&nbsp;transitive inference means that football teams can be assigned to that property as well as organizations. Search facets and&nbsp;API queries also obey the semantics of transitive inference across a class hierarchy.
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608678378af76a714bfdad60/file-x7YinLI0un.png">

When you create a Dataset and define a new Concept you define the properties for the&nbsp;Concept. Each of these properties has a data type. The data types fall into 3 main categories:<h2>1. Primitive data types</h2>
	 These are fundamental data types for value-based properties. The different primitive data types are:<ul>
	
<li>text&nbsp;– a string of characters or words. Used for labels and descriptions etc. All text properties are indexed for full text search. The primary label of a Concept is boosted for full text searching.</li>	
<li>keyword – a contiguous character string with no whitespace. A keyword is not indexed for full text search, but instead is used for identifiers or terms that can be queried as an exact match. You may use these, for example, for representing an alternative identifier, an ISO code, or a passport number.</li>	
<li>integer&nbsp;– decimal integers only, no whitespace, e.g. &nbsp;65432</li>	
<li>decimal – a decimal value, no whitespace, e.g. 12.34567</li>	
<li>boolean – a boolean value, true or false</li>	
<li>date – an ISO-8601 date, YYYY-MM-DD, &nbsp;e.g. &nbsp;2021-04-17</li>	
<li>dateTime – an ISO-8601 dateTime, YYYY-MM-DDThh:mm:ssZ &nbsp;e.g. 2021-04-17T13:14:32Z. A timezone component can be included.</li></ul><h2>2. Specialised primitives</h2>
	 These are also primitive data types for value type properties, but can be interpreted for specific use-cases in Data Graphs :<ul>
	
<li>latitude – a decimal field for capturing geospatial latitude coordinate values. When combined with a longitude Data Graphs indexes these properties for geospatial search, and also allows your Concepts to be plotted on a map.</li>	
<li>longitude&nbsp;– a decimal field for capturing geospatial latitude coordinate values. When combined with a latitude Data Graphs indexes these properties for geospatial search, and also allows your Concepts to be plotted on a map.</li>	
<li>URL – interpreted and validated as a URL</li>	
<li>imageURL –&nbsp;interpreted and validated as an image URL, and can be set as a canonical preview image of the Concept. Properties defined as imageURLs are rendered as images in Data Graphs.</li></ul><h2>3. Relationship properties</h2>
	 You can select any other previously defined Concept type as a value of some property. This allows you to define semantic relationships between things in Data Graphs, and lends itself to the knowledge graph or linked data pattern.&nbsp;
	 When you select a specific&nbsp;Concept&nbsp;type as the data type of some property, Data Graphs is able to validate and constrain the allowed&nbsp;Concept&nbsp;value to be only of this type.&nbsp;
	 If you have utilised sub-classing, and the property range is some parent class&nbsp;Concept&nbsp;type, then Data Graphs will constrain the range of the relationship to include all&nbsp;Concepts of the parent class selected and the set of all sub-classes of this&nbsp;Concept&nbsp;type.

In addition to free text search Data Graphs provides search (filter) by facets – properties that have been defined for a&nbsp;Concept&nbsp;type. For example, an aircraft might be associated with a manufacturer or a football players might be associated with a team. Faceted search allows you to combine a free text search with filtering based on a Concept's properties.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60813fe18af76a714bfd9cb6/file-byAZMOWnBq.png" style="width: 212px; float: left; margin: 0px 10px 10px 0px;" alt="">
	 Facets can be found on the left hand side of the search results screen. The default list of facets is always the&nbsp;Concept&nbsp;types. You can filter on any property you have defined as part of your schema. The additional facets can be found in the more facets dropdown.
	 When a facet is selected, the current set of&nbsp;Concepts are filtered to show only those that match that facet and any other existing search criteria. Counts of matching&nbsp;Concepts are provided based on the what is currently returned with facets and search terms applied.&nbsp;
	 Faceting by&nbsp;Concept&nbsp;label is included for data quality purposes as it is useful to see where there is more than one&nbsp;Concept&nbsp;with the same label.Faceting on a property that is inherited from a parent type will work across all the&nbsp;Concept&nbsp;types that it inherit from it. For more information see <a href="https://support.datagraphs.io/knowledge-base/managing-data/subclassing-and-inheritance">Subclassing and inheritance</a>.

A Concept is an instance of some thing in your domain. Concepts are the instance data that you populate your knowledge graph or reference data set with. People, places, organisations, tangibles and intangibles that are of relevance to you, your business, or your projects are all&nbsp;Concepts.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/607168f28996210f18bd201c/file-13qZsU4TsY.png" style="width: 401px; display: block; margin: auto;" alt="Concepts are the instances of things in your domain">
	 In Data Graphs, a Concept has a schema that defines its type (class), its properties and relationships to other&nbsp;Concepts.
	 When you create a Dataset you define the types of&nbsp;Concepts&nbsp;you want to populate it with. At this point you are able to:<ul>
	
<li>select or re-use Concept types you have already defined</li>	
<li>define new Concept types</li>	
<li>update the properties of an existing Concept type</li></ul>
	 All&nbsp;Concepts&nbsp;have an id and a label&nbsp;as fundamental properties. As a user you define whether you want to supply your own the ids (Manual&nbsp;Identifiers) or allow Data Graphs to generate them (Automatic Identifiers).&nbsp;
	 All other properties of a&nbsp;Concept&nbsp;are defined by you.
	 There are several ways of ingesting and maintaining&nbsp;Concepts&nbsp;in Data Graphs :<ul>
	
<li>Import Concepts in bulk into a Dataset using the CSV import wizard&nbsp;</li>	
<li>Import Concepts via the Data Graphs API</li>	
<li>Manually create and update Concepts using the Data Graphs user interface</li></ul>

Data Graphs lets you import data in tabular form using CSV files with a user interface where you can map CSV columns to your Dataset and&nbsp;Concept&nbsp;schemas.
	 The key steps in importing data are:<ol>
	
<li>Prepare a CSV file with the data you want to import, with each row representing one Concept or entity in your Data Graphs Dataset</li>	
<li>Create a Concept schema in a Dataset where Concept properties can be mapped to the data in your CSV column</li>	
<li>Use the Import Data wizard in a Dataset to guide you though mapping different CSV columns to the correct Concept properties</li></ol>
	 Key points:<ul>
	
<li>Your CSV does not need column headers, but this can help</li>	
<li>Column headers do not need to match the property names in the Concept schema, but if they do, Data Graphs will match them automatically. If they do not, you can match them yourself</li>	
<li>Each row in the CSV represents one Concept in Data Graphs, but you can import rows from one CSV file into multiple Concept types if you have a column in the CSV that identifies the Concept type of the row (eg Person, Organization etc)</li>	
<li>If the Concepts being imported are configured in Data Graphs&nbsp;to have manual identifiers, one of the columns in the CSV must hold the identifiers. With automatic identifiers, no identifier column is required</li>	
<li>You can match columns to relationship properties if the column contains identifiers of Concepts that you have either already imported or are planning to import.</li>	
<li>Data Graphs allows for "eventual consistency"&nbsp;– you can import links to other Concepts either before or after the linked Concepts are imported.</li>	
<li>Importing handles subclassing. If you import linked data where the target (linked) Concepts are of subclasses of the relationship you can either choose the type of linked Concept when you map your columns, or use a different column in the CSV as a type discriminator.</li><li>Maximum file size is 10MB. Larger files should be split and imported separately.</li></ul><h2>Importing a simple CSV</h2>
	 The following example demonstrates how to import a simple CSV where all the rows are mapped to a single&nbsp;Concept&nbsp;type. In this example we import a CSV of countries, where each row represents one Country, and the identifiers are the 2-character ISO codes.<h3>Step 1: Prepare the CSV and schema, and upload the file</h3>
	 Our CSV is structured as follows:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608eb124f8c0ef2d98df874f/file-tNCQli5DQ3.png">
	We have a Countries&nbsp;Dataset&nbsp;containing a&nbsp;Country&nbsp;type:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608ec6333149d33a19c72c58/file-ErQ9B33iJI.png">
	 Now upload your CSV using the file uploader, select your CSV file and click the import/upload button:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608ec65ae0324b5fdfd10f0f/file-V5ux0nkp0e.png"><h3>Step 2: Check the CSV headers</h3>
	 Data Graphs asks you if the CSV has a header row – choose 
	Yes or No:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608ec6b08996210f18bd9698/file-ZImjW4Bfdh.png"><h3>Step 3: Map the columns to Concept properties</h3>
	 For each property of our Country&nbsp;Concept, choose the CSV column that matches it. Data Graphs will attempt to match those columns that have the same names, but if not you can choose the correct column. Data Graphs will tell you how many rows have value data and flag up any potential data issues. When you have selected the column, choose the 
	Confirm option. You can also ignore a column in the CSV if you wish.
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608ec8413149d33a19c72c5a/file-J5X5P5QWi4.png"><h3>Step 4: Review your data and import</h3>
	 When you have mapped all your columns to properties, you can review the data you are importing. If you have made a mistake, you can go back to the previous steps and adjust. If you think you need to start again and adjust your CSV for data quality, you can still cancel, as nothing has been stored yet.&nbsp;
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608ee2ba8af76a714bfdd3bd/file-QXyjhaD5JG.png">
	 When you've finished reviewing the data, click the Import button. The data will be uploaded to Data Graphs, processed and loaded into your&nbsp;Dataset. This ingest is done asynchronously, so if it is a very large import, you can safely close your browser and come back later. Progress will be reported.
	 Once imported you can view your data, for example:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608ee29d3149d33a19c72c70/file-P2m5NUv8qA.png">

Once you have created a Dataset you may need to modify its schema, either to add new&nbsp;Concept&nbsp;types to it, or to modify the properties of a&nbsp;Concept&nbsp;within.
	 To view a&nbsp;Dataset's schema, click the menu icon in the top right of its tile on the relevant project's homepage, and select&nbsp;Manage.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/607427b34466ce6ddc5f38cf/file-13fMnlmRGa.png" style="width: 631px;">
	 This will take you to the Dataset's Schema screen – a read-only view of the its Concepts and their property definitions:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60742573e0324b5fdfd09eaa/file-DgTbuHkiYO.png" style="width: 692px;"><h2>Editing Concept properties</h2>
	 To edit a Concept's properties click the Edit Schema button in the bottom corner of the&nbsp;Concept&nbsp;details pane. Note, you will not be able to modify the property of a&nbsp;Concept&nbsp;schema if&nbsp;Concept&nbsp;instances already exist for the type you are editing. You can always add more properties to a Concept definition by clicking the + icon to the right of the last property:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/607432b38996210f18bd24bb/file-557ZuRpJqc.png" style="width: 689px;"><h2>Adding a new Concept type to a Dataset</h2>
	 To add a new Concept class/type to a&nbsp;Dataset&nbsp;schema, select a new Concept type from the Add a new type drop list at the top right of the Edit Schema screen. Choose a predefined&nbsp;Concept&nbsp;type, or choose Custom to create one of your own:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60743407f8c0ef2d98df1562/file-SVw4OrK76X.png" style="width: 695px;">
	 You will then be presented with a form to edit the properties of your new&nbsp;Concept.

Understanding how Data Graphs utilises identifiers is critical to understanding how to best setup your Datasets and maintain your data.<h2>Key points</h2><ul>
	
<li>Every Concept (entity) in Data Graphs has an identifier</li>	
<li>The identifier is unique to the type of Concept, for example all Concepts of type Person must have a unique identifier within the scope of all Person Concepts in your Data Graphs project.</li>	
<li>For a given type, identifiers can be configured to be manual&nbsp;(provided by you, the user) or automatic&nbsp;(generated by Data Graphs).</li>	
<li>When you create a Concept schema in a Dataset you choose whether the IDs are manual or automatic.</li>	
<li>For manually provided identifiers, you can choose to use the generic "id" property (that is present for all Concepts) or use a custom property of the Concept that you choose to be the identifier.</li></ul><h2>URNs</h2>
	 Internally Data Graphs uses URNs to namespace identifiers by&nbsp;Concept&nbsp;type. A URN is like a URI but is not web resolvable. The URN pattern used in Data Graphs is <code>urn:{project}:{type}:{id}</code> for example <code>urn:test:Person:1a2b3c4d</code>. You will see these URNs when viewing&nbsp;Concept&nbsp;data.&nbsp;
	 In most circumstances you need not worry about using URNs, especially in the Data Graphs app or when importing data – you can just use the identifier on the end part of the URN. But if you are using the API to query data, the URNs are important as they provide the true identity of each concept.<h2>Manual identifiers</h2>
	 If you choose manual identifiers when configuring a&nbsp;Concept&nbsp;type,&nbsp;you will need to provide a unique ID for every&nbsp;Concept&nbsp;of that type you create, either within the user interface or when using the API.
	 Why might you choose manual IDs? &nbsp;A good example is when you might be importing some external data that already has unique IDs. Or there might be a particular ID pattern you need to use, e.g., the 2 or 3 character ISO-3166 codes for identifying countries:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608f00328af76a714bfdd3e5/file-1w4ijrFwpN.png">

Linking data through semantic relationships is a critical part of building a useful knowledge graph. To do this there are a number of important principles to understand:<ol>
	
<li>How graphs join data entities using linked-data principles</li>	
<li>Creating relationships in your domain or ontology model</li>	
<li>How to load related Concepts into that model using the Data Graphs app</li>	
<li>How to load related Concepts into Data Graphs in bulk using a CSV file</li>	
<li>How to load related Concepts&nbsp;into Data Graphs in bulk via the API</li></ol><h2>Linked Data Principles</h2>
	 Linked-data patterns use the identity of entities to connect them; this ID usually takes the form of a URI or a URN.&nbsp;
	 In Data Graphs, each entity – known as a Concept – is identified by a URN, which is globally unique in your knowledge graph and takes the form <code>urn:{project}:{type}:{id}</code>. For example, <code>urn:demo:Person:12345</code>.<h2></h2>
	 Thus two Concepts, a Person and an Organization, can be linked together via their IDs as follows:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618e59abefc78d0553e59a61/file-jeYdFkmBy7.png" style="width: 701px;"><h2>Creating Relationships in the Domain Model</h2>
	 Creating relationships in your Data Graphs domain model is easy. It just requires some sequencing.&nbsp;
	 Relationships are defined between Concepts: a Concept owns a relationship when one of its properties is assigned another Concept as its datatype.&nbsp;In the above example – where a Person&nbsp;<code>worksFor</code> an Organization – the relationship is defined by adding the property <code>worksFor</code> to Person with the datatype&nbsp;Organization. (With this in mind, it is important to define Organization&nbsp;before creating this property on&nbsp;Person.)
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618e89549ccf62287e5f5f29/file-rFV1oN9PGH.png">
	 Once you have added your property, Data Graphs knows that this property belongs to Person and can only have&nbsp;Organization&nbsp;Concepts – or concepts that are sub-classes of Organization – assigned to this relationship.&nbsp;
	 In the RDF world, this principle is like assigning domains and ranges to properties in an ontology. The domain of property <code>worksFor</code> is class Person and the range is class Organization.<h2>Loading Linked Data via the Data Graphs app</h2>
	Once a relationship is defined in your&nbsp;Data Graphs&nbsp;domain model, the Add New Concept (or Edit Concept) screen knows which types (classes) of Concept can be used for which property. In essense, Data Graphs is range aware - it understands the semantics of the properties in your model.
	 For example, when creating a new Person instance,&nbsp;Data Graphs will only allow you select an Organization to populate the&nbsp;<code>worksFor</code>&nbsp;field. Of course, if you have not already loaded any Organization instances, there will be none available.
	 Data Graphs is also aware of class inheritance, so if you have created subclasses of an Organization, such as Political Party, the editor will let you choose concepts that are instances of those subclasses as well.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618eaa992b380503dfe047b8/file-MYeTg868LW.png">
	 Saving the above example creates a Person&nbsp;(Jane Doe) connected to an Organization (Apple) by the&nbsp;<code>worksFor</code>&nbsp;property, illustrated below in the Graph Explorer:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618eab6e64e42a671b636857/file-qE7pOlanbd.png"><h2>Loading Linked Data via CSV</h2>
	 Loading data in bulk with Data Graphs' <a href="https://support.datagraphs.io/knowledge-base/managing-data/importing-data">CSV importer</a> also uses the Concept identifiers to make the relationship joins. To illustrate this process, let's assume that we have three Organization&nbsp;Concepts as follows:
<table>
<thead>
<tr>
	<td>
		 Organization name
	</td>
	<td>
		 Organization ID
	</td>
</tr>
</thead>
<tbody>
<tr>
	<td>
		 Apple
	</td>
	<td>
		 59k0AZ8rcripmaLcL2BisK 
	</td>
</tr>
<tr>
	<td>
		 Amazon
	</td>
	<td>
		 5ir3poyfNQLjjsra50BDRI
	</td>
</tr>
<tr>
	<td>
		 Microsoft
	</td>
	<td>
		 5qnrcsngabk85QSrrT4M1E
	</td>
</tr>
</tbody>
</table>
	 Our CSV lists people that work for these organizations. It has two columns, which contain the person's name and the identifier of the company they work for:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618ec4e964e42a671b636904/file-bFx9TF55ov.png">
	 When loading this CSV into our Dataset with the CSV Importer, we need to identify the data as Person&nbsp;Concepts and to map the&nbsp;<code>worksFor</code>&nbsp;column of the CSV to the&nbsp;<code>worksFor</code>&nbsp;property of the Person type:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618ec5489ccf62287e5f60ba/file-Kvr6QzYx3v.png">
	 This way Data Graphs will be able to establish the relationships between each person and the organization(s) they work for&nbsp;automatically. (Note that Carol James and Billy Crane both work for two organizations so their&nbsp;<code>worksFor</code>&nbsp;column has the identifiers of both companies in a quoted array.)
	 One the import completes, our People graph is as follows:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/618ec5a82b380503dfe0486a/file-foE48clVK3.png"><h2>Loading linked concepts using the API</h2>
	 When loading Concepts using the Data Graphs API, you need to send a POST request to the <a href="https://support.datagraphs.io/api-docs/[docs]#create-concept-s">Create Concept(s) endpoint</a> specifying the key of Dataset where the Concept type is defined.&nbsp;
	 The Concepts themselves should be defined as fully formed JSON in the request body. Relationship properties must identify the Concept being connected with its entire URN.&nbsp;Creating Person Concepts in our&nbsp;<code>worksFor</code>&nbsp;example, the JSON would be as follows (assuming the Person Concept is defined with automatically assigned identifiers):
<pre>[
 {
 "type": "Person",
 "name": "Jane Doe",
 "worksFor": [
 "urn:test:Organization:5ir3poyfNQLjjsra50BDRI"
 ]
 },
 {
 "type": "Person",
 "name": "Jim Smith",
 "worksFor": [
 "urn:test:Organization:59k0AZ8rcripmaLcL2BisK"
 ]
 },
 {
 "type": "Person",
 "name": "John Jones",
 "worksFor": [
 "urn:test:Organization:59k0AZ8rcripmaLcL2BisK"
 ]
 },
 {
 "type": "Person",
 "name": "Carol James",
 "worksFor": [
 "urn:test:Organization:5qnrcsngabk85QSrrT4M1E",
 "urn:test:Organization:5ir3poyfNQLjjsra50BDRI"
 ]
 }
]
</pre>

Data Graphs allows you to search within a specific Dataset or across all the Datasets in a given account, known as a&nbsp;"federated search".
	 The search box on a project home screen allows you to carry out a federated search. You do not have to specify a search term – you can perform an empty query that will return all data and allow you to navigate by facets. A free-text search can be added, as well as a filter by facet, at any stage and in any combination.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60813b37e0324b5fdfd0d85c/file-KFJq94QJUH.png" alt="Search across all datasets" style="display: block; margin: auto;">
	 To search within a specific Dataset and use&nbsp;its associated facets, select the Dataset from the project home screen and search from the sidebar on the subsequent Concepts screen. You can return to a federated search at any time by navigating to the home screen.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60813b833149d33a19c6f53e/file-acQALz2QAI.png" alt="Searching within a dataset" style="display: block; margin: auto;">
	 
	 See <a href="https://support.datagraphs.io/knowledge-base/managing-data/search-facets">searching by facets</a> for more information.

Sometimes you will want to take one or more Concepts and merge them into a single existing Concept. This might be because of data errors that created duplicate Concepts or because you now consider the Concepts to be the same.
	 To merge Concepts, select two concepts from any Concepts list or search results screen:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608146a13149d33a19c6f58b/file-wkvA2EcUnG.png" style="width: 648px;">
	 And then choose Merge Selected&nbsp;from the menu in the bottom right corner of the screen.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6102806d64a230081ba1a1b2/file-uGW04E8hq3.png" style="width: 193px;">
	 The next screen allows you to decide which is the target concept, which you will retain, and which is the source concept, which will be merged into the target. &nbsp;You can swap&nbsp;between the two of them using the button at the top. Note that the id of the target concept will be retained and used as the canonical ID for the merged concept.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/60814743f8c0ef2d98df5059/file-cr6cmfiNMZ.png">
	 You can copy fields from the source to the target concept by clicking the arrows. The lock icon indicates that the field is not editable at the merge stage but you can still copy and the value to the target concept.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/608147a18996210f18bd5f02/file-0fUJNyeVlf.png" style="width: 345px;">
	 When you have decided what data is to be retained, you can confirm the merge of concepts.

A Concept can be deleted individually or as a group.
	 To delete an individual Concept, select it and enter the "Concept view" screen. Then in the left-hand menu, select Remove Concept.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6081445af8c0ef2d98df5049/file-VXmkNcM0AX.png" style="width: 302px; float: left; margin: 0px 10px 10px 0px; clear: both;" alt="">
	 To delete groups of Concepts from any list view or search results screen, you can select multiple Concepts via the check box on each Concept.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6081447f3149d33a19c6f576/file-Xf6o3MQ80U.png" style="width: 252px;" alt="">
	 Then in the bottom right of the screen, you can open the menu to choose to Delete Selected.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61027f0eb37d837a3d0dea2e/file-gbc6UwiRAw.png" style="width: 251px;">

This feature allows you to build complex queries to search for Concepts within a given Dataset by chaining and grouping boolean expressions.&nbsp;You will find it on the Concepts screen and can access it by clicking the three dots icon at the top of the sidebar and selecting Advanced Search:<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/62e3c0b7a3bd51396505487f/file-fET4UcQYVC.png">Building a Query
	 Datagraphs' Advanced Search allows you build a series of boolean clauses (Items), each of which consists of a property type, a value and in some cases an operator or operator expression. Items can be chained&nbsp;together with boolean operators (AND, OR). It is also possible to describe a Group of items which can in turn be combined with other Items or Groups.<h2></h2>
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61b87313a5e184696a17a8a1/file-Qqts3byvFZ.png" style="width: 305px;"><h2>Searching with an Item</h2>
	 To create an Item, select a property and then choose or enter the value you wish to search for. In the example below the property is <code>Type</code> and the value is <code>Ingredient</code>, and clicking Search will find all Concepts whose Type is Ingredient.
<div style="display: flex;">
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61b873c0a5e184696a17a8a4/file-en47KHrEtm.png" style="width: 307px;">
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61b874d9e5e5185a647d47bd/file-Jpg6HsXl7B.png" style="width: 307px; margin-left: 40px;">
</div><h2>Searching with multiple Items</h2>
	 Clicking Add Item allows you to create another item. By default it is combined with the existing item with a boolean AND operator; in this case the query will return concepts that match&nbsp;all&nbsp;items in the group. Toggling the&nbsp;button on the left-hand bracket from&nbsp;ALL&nbsp;to ANY produces a boolean OR operator, meaning the query will return concepts that match&nbsp;any item in the group.
<div style="display: flex;">
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61b87844e5e5185a647d47c1/file-cTu8rGTiuX.png" style="width: 307px;">
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61b878daa5e184696a17a8b6/file-DS2k2F00js.png" style="width: 307px; margin-left: 40px;">
</div><h2> Searching with Groups and Items </h2>
	 With more complex queries, you can group Items by boolean operator. To create a Group, click Add Group and create its items as usual. The following example combines a Group with an item. But Groups can also be combined with other Groups, and can themselves contain a Group or several Groups.&nbsp;
<div style="display: flex;">
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61b87a9ba5e184696a17a8bf/file-5DbWo50ue6.png" style="width: 307px;">
	 
</div>

The custom validation rules are a configurable set of rules which can be applied to the majority of available property data types, providing an additional layer to ensure the logical integrity of your data. Validation rules can be a critical tool when using Data Graphs for master-data management or reference-data management.<h2>1. Custom Validation Rules</h2>
	 Basic Rules<ul>
	
<li>Custom RegEx&nbsp;- validates strings agains any valid&nbsp;regular expression. Can be applied to both keyword&nbsp;and text&nbsp;property data types.</li>	
<li>Min Characters - validates total number of characters, incl. whitespace,&nbsp;in a string against a specified number. The number of characters has to be greather than or equal to the specified number. Can be applied to both keyword&nbsp;and text&nbsp;property data types.</li>	
<li>Max Characters - validates total number of characters, incl. whitespace,&nbsp;in a string against a specified number. The number of characters has to be less than&nbsp;or equal to&nbsp;the specified number. Can be applied to both keyword&nbsp;and text&nbsp;property data types.</li>	
<li>Min Words - validates the total number of words in a string against a specified number. The number of words has to be greather than&nbsp;or equal to&nbsp;the specified number.&nbsp;Can be applied to text&nbsp;property data type.</li>	
<li>Max Words - validates the total number of words&nbsp;in a string against a specified number. The number of words has to be less than&nbsp;or equal to the specified number. Can be applied to text&nbsp;property data type.</li>	
<li>Min Value - validates numeric input against a specified value. The input number has to be greather than&nbsp;or equal to&nbsp;the specified value. Can be applied to integer, decimal, latitude&nbsp;and longitude&nbsp;property data types.</li>	
<li>Max Value&nbsp;- validates numeric&nbsp;input against a specified value. The input number has to be less than&nbsp;or equal to&nbsp;the specified value. Can be applied to integer, decimal, latitude&nbsp;and longitude property data types.</li>	
<li>After Date&nbsp;- validates input date against a specified date. The input date has to be&nbsp;AFTER&nbsp;the specified date. Can be applied to&nbsp;date&nbsp;and&nbsp;dateTime&nbsp;property data types.</li>	
<li>Before Date - validates input date against a specified date. The input date has to be BEFORE&nbsp;the specified date. Can be applied to date&nbsp;and dateTime&nbsp;property data types.</li></ul><h3>Special Rules</h3><ul>
	
<li>Must be in the past - validates input date against the a relative date. When creating a concept the input value has to be BEFORE&nbsp;the current time. When editing a concept the input value hast to be BEFORE&nbsp;the creation date of the concept.&nbsp;</li>	
<li>Must be in the future&nbsp;-&nbsp;validates input date against the a relative date. When creating a concept the input value has to be&nbsp;AFTER&nbsp;the current time. When editing a concept the input value hast to be&nbsp;AFTER the creation date of the concept.&nbsp;</li>	
<li>Min Items - validates the number of items in an array property against a specified number. The number of items must be greather than&nbsp;or equal to&nbsp;the specified number. Can be applied to ANY array property of&nbsp;ANY&nbsp;property data type.</li>	
<li>Max Items&nbsp;- validates the number of items in an array property against a specified number. The number of items must be less than&nbsp;or equal to&nbsp;the specified number. Can be applied to ANY&nbsp;array property of ANY&nbsp;property data type.</li></ul><h3> Unsupported Data Types</h3>
	 Boolean - a boolean is inherently only true or false, and thus no additional custom&nbsp;validation is necessary.
	 URL and ImageUrl&nbsp;- these can only be validated as a URL string,&nbsp;&nbsp;and thus no additional validation is necessary.<h5></h5><h2>2. Working with the validation rules</h2>
	 Custom validation rules can be added through the dataset creation wizzard, at the point when properties are being customised. You can also add or remove rules at any point after creating the Concept Type through the type schema editor.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/616d938d9ccf62287e5ece1e/file-g3cR8StJVR.png" style="background-color: initial;">
	 Your rules will be applied immediately and will be visible in the Concept form.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/616d95b99ccf62287e5ece31/file-ImOnxc7V8S.png"><h5></h5>

If you have multiple Datasets you can search across all your data and all your Concepts using a federated search.&nbsp;
	 You can start a federated search from the project homepage, where all its Datasets are listed, by typing into the search bar at the top of the page. This will let you select a Concept, or if you hit return it will invoke a detailed full text search.&nbsp;
	 &nbsp;Alternatively you can click the arrow button highlighted below without typing in the search bar:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61a0a1d8efc78d0553e5de20/file-xn1WxkuzCr.png">
	 In this case you will be presented with a search page that lets you facet across all your data and build a search from scratch:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/61a0a2a6efc78d0553e5de23/file-leJHJXgqAa.png">

Managing data

The Data Graphs API is a REST API that allows you to interact with your data, letting you query, retrieve, filter, facet, and sort Concepts from your Datasets. You can also access individual Datasets and search within them, or federate across all your data.
	 The API provides the following core capabilities:<ul>
	
<li>Authentication</li>	
<li>Full text search</li>	
<li>Querying and filtering data</li>	
<li>Faceting</li>	
<li>Sorting and paging</li>	
<li>Creating Concepts</li></ul>
	 Although you can develop directly against the API, if you are coding in Javascript we recommend using the <a href="https://support.datagraphs.io/client-sdk/set-up/get-started">Data Graphs Javascript Client SDK</a>.<h2>Using the API</h2>
	 The API's Base URL is:
	 <code>https://api.datagraphs.io</code>
	 All requests require an&nbsp;API key&nbsp;and those to private Datasets must also include&nbsp;an&nbsp;OAuth 2.0 access token. For more information see <a href="https://support.datagraphs.io/knowledge-base/using-data-graphs-api/making-a-request">Making a Request</a>.<h2>Testing the API</h2>
	 If you have a&nbsp;Developer,&nbsp;Owner, or Administrator role on a given account, you can test each endpoint against your own data in the <a href="https://support.datagraphs.io/api-docs/overview">Support Portal API documentation</a>. Once logged in, just select the relevant application from the account menu in the nav bar.

Access to the API is granted via an API key and, for private&nbsp;Datasets,&nbsp;an optional set of OAuth credentials. These are unique to each application and bound to the project in which they are created.&nbsp;<h2>Generating application credentials</h2>
	 To create application credentials, navigate to the <a href="https://app.datagraphs.io/_account/_project/_manage/project-applications">Applications screen</a> of your current project. Note this is only accessible by users with one of the roles&nbsp;Owner,&nbsp;Administrator&nbsp;or&nbsp;Developer.
	 Click Create New Application&nbsp;to create a new set of API credentials. You must name your application and choose whether it has&nbsp;read&nbsp;access or&nbsp;read/write&nbsp;access to your data:<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/630738dac1ba4b3dfdae2f33/file-fMMa9kHfpz.png"><h2>Generate an OAuth 2.0 token</h2>
	 Once you have your application credentials, you can use them to generate the access token you'll need for calls to private Datasets. 
	 
	 Use the <code>clientId</code> and <code>clientSecret</code> in the body of a request to <code>POST /oauth/token</code>&nbsp;as follows:
<pre>	{
 	 "clientId": "{clientId}", 
 	 "clientSecret": "{clientSecret}"
	}
</pre>
	 The response will be in the form:
<pre>	{ 
 	 "access_token": "eyJhbGciOiJSUzI1N.....", 
 	 "expires_in": 86400, "token_type": "Bearer"
	}
</pre>

Webhooks are an integration mechanism that allow you to trigger actions in a downstream business system or application in response to certain Data Graphs&nbsp;events, such as creating or updating a&nbsp;Concept.&nbsp;This lets you react to changes in Data Graphs without having to poll the API. They are essentially a&nbsp;push&nbsp;integration.
	 Data Graphs webhooks to respond to the following 
	event types:<ul>
	
<li>Concept Created</li>	
<li>Concept Updated</li>	
<li>Concept Merged</li>	
<li>Concept Migrated</li>	
<li>Concept Deleted</li>	
<li>Candidate Concept Accepted</li>	
<li>CSV Imported</li>	
<li>Dataset Deleted</li>	
<li>All Concepts in Dataset Deleted</li>	
<li>All Concepts for Type Deleted</li>	
<li>Multiple Concepts Deleted</li></ul>
	 Each can listen for changes in all Datasets or can be constrained to a specific Dataset.
	 When one of these&nbsp;events occurs, Data Graphs sends a POST request to your external environment with the event's details in the payload; examples of each type of payload are listed below. In fact, you can set up a webhook to make multiple POST requests by configuring multiple endpoints;<h2>Creating a webhook</h2>
	 To create a webhook you must have the role 
	Owner, Administrator&nbsp;or Developer.&nbsp;
	 1) Navigate to the 
	<a href="https://app.datagraphs.io/_account/_project/_manage/account-webhooks">Webhooks</a> screen in project management:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/63073995c1ba4b3dfdae2f3c/file-CLJLXfX40K.png">
	 2) Click on the 
	Add Webhook button and select an&nbsp;Event Type and&nbsp;Target Dataset, and add the Endpoint&nbsp;of the webhook that will be invoked.
	 In the following example, any Concept added to the 
	Organizations&nbsp;Dataset will send details of that event to <a href="https://www.webhook-domain.com/endpoint:">https://www.webhook-domain.com/endpoint</a>:
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/63073c4e86ac2a0f0724a3a8/file-CVJX7Iij1z.png" style="background-color: initial; width: 520px;">
	 You can add additional endpoints to each event and&nbsp;pass authentication credentials or an API key&nbsp;to each endpoint.&nbsp;
	 3) When you have configured your hook, click 
	Save and the hook will be ready.4) Clicking the&nbsp;
	Test button on your new hook will enable you to trigger it&nbsp;manually&nbsp;using a sample payload and check that it is received correctly at the endpoints(s) you have provided.
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/63073d5f549d66420b99a9ee/file-V6g4gXGy1T.png" style="width: 752px;"><h2>Pre-Commit Endpoint</h2>
	 If you choose to target&nbsp;
	All Datasets&nbsp;there is an additional option to create a single&nbsp;Pre-Commit endpoint for a create, update, merge, migrate or delete&nbsp;Concept event.
	<img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/63073f9cc1ba4b3dfdae2f77/file-X34N1eqyK3.png" style="width: 544px;">This allows a consumer of the pre-commit hook to carry out an impact assessment on your data or the event before carrying out the action. It allows a downstream system to either cancel the change entirely, approve the change, or respond with an assessment or warning that the Data Graphs user can interpret.
	Pre-Commit webhooks will handle three cases:<ul><li>No impact – the action is completed with no notification in the UI.</li><li>Reject – a modal informs the user that the action cannot be completed.</li><li>Warning – a modal informs the user that the action can be completed with details of the impact with a prompt to continue.</li></ul><h2>Webhook request sample payloads</h2><h4>ConceptCreated</h4>
<pre style="margin-left: 20px;">{
 "type": "DataObjectEvent",
 "guid": "event-guid",
 "epoch": 1605781971,
 "targetDataset": {
 "name": "Concepts",
 "id": "urn:demo:concept"
 },
 "operation": "Created",
 "eventDate": "2020-11-19T10:32:33.518Z",
 "eventType": "DataObjectCreated",
 "eventTarget": "urn:demo:Concept:guid",
 "account": "demo",
 "sourceType": "User",
 "eventAgent": {
 "id": "urn:demo:user:guid",
 "name": "Demo User"
 },
 "objectVersion": {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid",
 "type": "Concept"
 }
}
</pre><h4>ConceptUpdated</h4>
<pre style="margin-left: 20px;">{
 "type": "DataObjectEvent",
 "guid": "event-guid",
 "epoch": 1605781971,
 "targetDataset": {
 "name": "Concepts",
 "id": "urn:demo:concept"
 },
 "operation": "Modified",
 "eventDate": "2020-11-19T10:32:33.518Z",
 "eventType": "DataObjectUpdated",
 "eventTarget": "urn:demo:Concept:guid",
 "account": "demo",
 "sourceType": "User",
 "eventAgent": {
 "id": "urn:demo:user:guid",
 "name": "Demo User"
 },
 "objectVersion": {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid",
 "type": "Concept"
 },
 "propertiesModified": [
 {
 "propertyName": "prop1",
 "newValue": "New value of prop1",
 "oldValue": "Old value of prop1"
 }
 ]
}
</pre><h4>ConceptDeleted</h4>
<pre style="margin-left: 20px;">{
 "type": "DataObjectEvent",
 "guid": "event-guid",
 "targetDataset": {
 "name": "Concepts",
 "id": "urn:demo:concept"
 },
 "operation": "Deleted",
 "eventDate": "2020-11-19T10:32:33.518Z",
 "eventType": "DataObjectDeleted",
 "eventTarget": "urn:demo:Concept:guid",
 "account": "demo",
 "sourceType": "User",
 "eventAgent": {
 "id": "urn:demo:user:guid",
 "name": "Demo User"
 },
 "objectVersion": {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid",
 "type": "Concept"
 }
}
</pre><h4>ConceptMerged</h4>
<pre style="margin-left: 20px;">{
 "type": "DataObjectEvent",
 "guid": "event-guid",
 "epoch": 1605781971,
 "targetDataset": {
 "name": "Concepts",
 "id": "urn:demo:concept"
 },
 "operation": "Modified",
 "eventDate": "2020-11-19T10:32:33.518Z",
 "eventType": "DataObjectMerged",
 "eventTarget": "urn:demo:Concept:guid",
 "account": "demo",
 "sourceType": "User",
 "eventAgent": {
 "id": "urn:demo:user:guid",
 "name": "Demo User"
 },
 "objectVersion": {
 "label": "label1",
 "prop1": [
 "value1 updated",
 "value2 updated"
 ],
 "prop2": "value2",
 "id": "urn:demo:Concept:guid",
 "type": "Concept"
 },
 "propertiesModified": [
 {
 "propertyName": "prop1",
 "newValue": [
 "value1 updated",
 "value2 updated"
 ],
 "oldValue": [
 "old value of prop1",
 "old value of prop1"
 ]
 },
 {
 "propertyName": "prop1",
 "newValue": "2020-11-19T10:36:46.869Z",
 "oldValue": "2020-11-19T10:34:27.694Z"
 }
 ],
 "sourceIds": [
 "urn:demo:Concept:merged-concept-guid"
 ]
}
</pre><h4>CandidateAccepted</h4>
<pre style="margin-left: 20px;">{
 "type": "CandidateEvent",
 "guid": "event-guid",
 "epoch": 1605781971,
 "targetDataset": {
 "name": "Concepts",
 "id": "urn:demo:concept"
 },
 "operation": "Modified",
 "eventDate": "2020-11-19T10:32:33.518Z",
 "eventType": "CandidateAccepted",
 "eventTarget": "urn:demo:Concept:guid",
 "account": "demo",
 "sourceType": "User",
 "eventAgent": {
 "id": "urn:demo:user:guid",
 "name": "Demo User"
 },
 "objectVersion": {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid",
 "type": "Concept"
 }
}
</pre><h4>CSVImported</h4>
<pre style="margin-left: 20px;">{
 "type": "CSVImport",
 "guid": "event-guid",
 "epoch": 1605781971,
 "targetDataset": {
 "name": "Concepts",
 "id": "urn:demo:concept"
 },
 "operation": "Created",
 "eventDate": "2020-11-19T10:32:33.518Z",
 "eventType": "CSVImported",
 "account": "demo",
 "sourceType": "User",
 "objectCount": 100,
 "eventAgent": {
 "id": "urn:demo:user:guid",
 "name": "Demo User"
 },
 "objectVersions": [
 {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid",
 "type": "Concept"
 },
 {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid2",
 "type": "Concept"
 },
 {
 "label": "label1",
 "prop1": "value1",
 "prop2": "value2",
 "id": "urn:demo:Concept:guid3",
 "type": "Concept"
 }
 ]
}
</pre>

Datagraphs API makes a range of query parameters available for organizing and refining searches for Datasets and Concepts.&nbsp;<h4>Definitions</h4>
<table>
<tbody>
<tr>
	<td>
		<code>pageSize</code>
	</td>
	<td>
		 The number of results to return in the response, eg 
		<code>pageSize=10</code>
	</td>
</tr>
<tr>
	<td>
		<code>pageNo</code>
	</td>
	<td>
		 The page number indicating which set of results should be returned in the response, eg 
		<code>pageNo=2</code>
	</td>
</tr>
<tr>
	<td>
		<code>sort</code>
	</td>
	<td>
		 Sorts the results in the response using a specified field and direction, eg 
		<code>sort=property1:asc,property2:desc</code>
	</td>
</tr>
<tr>
	<td>
		<code>filter</code>
	</td>
	<td>
		 A expression that filters a request. It is a string that takes the form&nbsp;
		<code>{property}:{operator}{value}</code> or uses a special function
	</td>
</tr>
<tr>
	<td>
		<code>q</code>
	</td>
	<td>
		 Full text search, eg 
		<code>q=name</code>
	</td>
</tr>
<tr>
	<td>
		<code>facets</code>
	</td>
	<td>
		 Facets to be listed, eg, 
		<code>facets=type</code>
	</td>
</tr>
<tr>
	<td>
		<code>facetSize</code>
	</td>
	<td>
		 Number of facets to include in results, eg
		<code>facetSize=10</code>
	</td>
</tr>
<tr>
	<td>
		<code>dateFacets</code>
	</td>
	<td>
		 Date facets, eg 
		<code>dateFacets=publishedDate:1d:1w:1M</code>
	</td>
</tr>
<tr>
	<td>
		<code>fields</code>
	</td>
	<td>
		 List of fields to be included in the response, eg
		<code>fields=id,label,image</code>
	</td>
</tr>
<tr>
	<td>
		<code>embed</code>
	</td>
	<td>
		 List of ids of related properties to be embedded in the response, eg 
		<code>embed=id1,id2,id3</code> or for all properties <code>embed=_all</code>
	</td>
</tr>
<tr>
	<td>
		<code>ids</code>
	</td>
	<td>
		 List of Concept&nbsp;ids to be returned (separated by a comma), eg 
		<code>ids=id1,id2,id3</code>
	</td>
</tr>
</tbody>
</table><h4>Building a filter expression</h4>
	 Filter expressions can be constructed from a property, value and optional operator. More complex queries can use a filter function (see below).
	 In its simplest form a filter expression consists of a 
	property and a value, eg&nbsp;<code>filter=property1:value1</code>, where the separator (:) is equivalent to "=". Adding an operator&nbsp;allows for different types of comparisons.&nbsp;
	 Filter expressions can be combined using&nbsp;
	<code>,</code>&nbsp;(AND) or&nbsp;<code>|</code>&nbsp;(OR). Using parentheses around combinations of expressions – eg&nbsp;<code>({expression1},{expression2})</code>&nbsp;– overrides operator precedence.
	 The following defines the rules for each element in a constructed filter expression:
<table>
<tbody>
<tr>
	<td>
		Property
	</td>
	<td>
		 A path representing the field to filter on.
	</td>
	<td>
		<ul>
			<li>It matches&nbsp;<code>[a-zA-Z_][a-zA-Z0-9_.]</code>.</li>
			<li>It supports&nbsp;<code>.</code>&nbsp;separated paths.</li>
			<li>It can contain only alpha-numeric characters and&nbsp;<code>_</code>.</li>
			<li>It cannot contain whitespace.</li>
			<li>It must start with a letter.</li>
		</ul>
	</td>
</tr>
<tr>
	<td>
		Operator
	</td>
	<td>
		 Used to compare values (on its own is roughly =); optional.
	</td>
	<td>
		<ul>
			<li><code>-</code>&nbsp;not</li>
			<li><code>&gt;</code>&nbsp;greater than</li>
			<li><code>&gt;=</code>&nbsp;greater than or equals</li>
			<li><code>&lt;</code>&nbsp;less than</li>
			<li><code>&lt;=</code>&nbsp;less than or equals</li>
			<li><code>[</code>&nbsp;value, value, ...&nbsp;<code>]</code>&nbsp;in group</li>
		</ul>
	</td>
</tr>
<tr>
	<td>
		Value
	</td>
	<td>
		A string containing the value to match the expression against.
	</td>
	<td>
		<ul>
			<li>It can contain whitespace.</li>
			<li>Dates and datetimes should be in ISO 8601 format.</li>
		</ul>
	</td>
</tr>
</tbody>
</table><h3> Filter functions</h3>
	 Functions for more complex queries follow the format&nbsp;
	<code>filter=_functionName(arg1, arg2, etc)</code>. The&nbsp;following are supported:<h4>_has()</h4>
	 Search for Concepts where a given property is populated.<h4>_lacks()</h4>
	 Search for Concepts where a given property is undefined.
	 Where a property is nested, 
	<code>_has()</code> and <code>_lacks()</code> can accept the path to that property, eg <code>_has(address.postcode)</code>, but will not filter on an object, eg <code>_has(address)</code>.<h4>_within()</h4>
	 Search for Concepts within a given area.&nbsp;
	 Coordinates can be provided either as latitude and longitude in the format&nbsp;
	<code>(lat, long)</code>, or as a geohash.&nbsp;If two coordinates are provided, they define&nbsp;the top left and bottom right corners of the&nbsp;search area as a bounding box. Three or more coordinates define the search as a polygon.
	 NB&nbsp;This function can only be used with&nbsp;Concepts whose properties include either a latitude/longitude pair or a geohash property.<h4>_near()</h4>
	 Search for Concepts within range of a given location.&nbsp;
	 Coordinates can be provided either as&nbsp;latitude&nbsp;and longitude in the format&nbsp;
	<code>(lat, long)</code>&nbsp;or as a geohash.
	 The following units are supported for distance:<ul>
	
<li><code>mi</code>&nbsp;– miles</li>	
<li><code>km</code>&nbsp;– kilometres</li>	
<li><code>m</code>&nbsp;– metres</li>	
<li><code>cm</code>&nbsp;– centimetres</li>	
<li><code>mm</code>&nbsp;– millimetres</li></ul>
	 NB&nbsp;This function can only be used with&nbsp;Concepts whose properties include either a latitude/longitude pair or a geohash property.<h3> 
Filter examples</h3>
	 The following expressions can all be used on a Search Concepts query:<h4>Comparisons</h4><ul>
	
<li>
	

	 Search Concepts where 
		<code>string1</code> equals <code>value1</code>
	
		<code>filter=string1:value1</code>
	</li>	
<li>
	

	Search Concepts where 
		<code>string1</code>&nbsp;equals&nbsp;<code>value1</code>&nbsp;and&nbsp;<code>string2</code>&nbsp;equals&nbsp;<code>value2</code>
	
		<code>filter=string1:value1,string2:value2</code>
	</li>	
<li>
	

	 Search Concepts&nbsp;where&nbsp;
		<code>string1</code>&nbsp;equals&nbsp;<code>value1</code>&nbsp;and&nbsp;<code>string2</code>&nbsp;does not equal&nbsp;<code>value2</code>
	
		<code>filter=string1:value1,string2:-value2</code>
	</li>	
<li>
	

	Search Concepts&nbsp;where&nbsp;
		<code>string1</code>&nbsp;equals&nbsp;<code>value1</code>&nbsp;or&nbsp;<code>value2</code>
	
		<code>filter=string1:[value1,value2]</code>
	</li></ul><h4>Dates</h4><ul>
	
<li>
	

		Search Concepts&nbsp;created between 
		<code>2020-01-01</code>&nbsp;and&nbsp;<code>2020-02-01</code>
	
		<code>filter=createdDate:&gt;=2020-01-01,createdDate:2020-02-01</code>
	</li>	
<li>
	

		Search Concepts&nbsp;created or modified since&nbsp; 
		<code>2020-01-01</code>
	
		<code>filter=createdDate:&gt;=2020-01-01|lastModifiedDate:&gt;=2020-01-01</code>
	</li>	
<li>
	

		Search Concepts&nbsp;where&nbsp;
		<code>string1</code>&nbsp;equals&nbsp;<code>value1</code>&nbsp;and it was created or modified since&nbsp;<code>2020-01-01</code>
	
		<code>filter=string1:value1,(createdDate:&gt;=2020-01-01|lastModifiedDate:&gt;=2020-01-01)</code>
	</li></ul><h4>Geometry</h4><ul>
	
<li>
	

		Search Concepts&nbsp;within 100 miles of coordinates (-40, 70)
	
		<code>filter=_near((-40, 70), 100mi)</code>
	</li>	
<li>
	

		 Search Concepts within a polygon with points (-40, 70), (-30, 60), (-35, 60)
	
		<code>filter=_within((-40, 70) (-30, 60), (-35, 60))</code>
	</li>	
<li>
	

	 Search Concepts within a box with top left corner (-40, 70) and bottom right corner (-30, 60)
	
		<code>filter=_within((-40, 70) (-30, 60))</code>
	</li></ul><h4>Property validation</h4><ul>
	
<li>
	

	 Search Concepts where 
		<code>property1</code> is populated
	
		<code>filter=_has(property1)</code>
	</li>	
<li>
	

	 Search Concepts where 
		<code>property1</code> on <code>object1</code> is populated
	
		<code>filter=_has(object1.property1)</code>
	</li>	
<li>
	

	 Search Concepts where 
		<code>property1</code> is undefined
	
		<code>filter=_lacks(property1)</code>
	</li>	
<li>
	

	 Search Concepts where 
		<code>property1</code> on <code>object1</code> is undefined
	
		<code>filter=_lacks(object1.property1)</code>
	</li></ul>

Although we advise using the Data Graphs Client SDK to access your data, you can query the API directly. In this case, you will need to combine the Base URL –&nbsp; 
	<code>https://api.datagraphs.io/</code>&nbsp;– with the relevant endpoint.
	<code>GET</code>, <code>POST</code>,&nbsp;<code>PUT</code>,&nbsp;<code>PATCH</code>, and <code>DELETE</code>&nbsp;methods are available.&nbsp;<code>GET</code>&nbsp;requests can include <a href="https://support.datagraphs.io/knowledge-base/using-data-graphs-api/query-parameter-reference">query parameters</a> that limit the size, ask for specific page, filter and sort the data in the responses.&nbsp;<code>POST</code>,&nbsp;<code>PUT</code>&nbsp;and&nbsp;<code>PATCH</code>&nbsp;requests require a JSON body.
	 The 
	<a href="https://support.datagraphs.io/api-docs/overview">API documentation</a> has more information, as well as sample requests/responses and a test harness for each endpoint.<h2>Headers</h2>
	 All requests require an&nbsp;API key&nbsp;and those to private Datasets must also include&nbsp;an&nbsp;OAuth 2.0 access token.
	API key –&nbsp;should be used as an&nbsp;&nbsp; <code>x-api-key</code>&nbsp;header
	OAuth 2.0 access token&nbsp;– should be used in the&nbsp;Authorization&nbsp;header as a Bearer token
	 See 
	<a href="https://support.datagraphs.io/knowledge-base/using-data-graphs-api/authentication">Authentication</a> for information on how to access your API key and generate an access token.

Using Data Graphs API

Data Graphs users can be added to an account, assigned roles and removed from an account. They can also be added to individual projects. Team members must have either the&nbsp;Owner&nbsp;or&nbsp;Administrator&nbsp;role to perform these tasks.<h2>Managing users at Account level</h2>
	 Click on the user icon in the top right of the app nav bar and select&nbsp;Manage Account from the dropdown menu and Users from the sidebar.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6307475f66967f4ba394b0aa/file-nOEIDTfpHT.png"><h2>Inviting a user</h2>
	 Click the&nbsp;Invite&nbsp;button and&nbsp;enter the user's email address. Then choose the role they will have in your Data Graphs account.&nbsp;Find out <a href="https://support.datagraphs.io/knowledge-base/managing-your-account/team-roles">here</a> the permissions associated with each role.
	 Selecting&nbsp;Owner&nbsp;or Administrator&nbsp;gives them that role across all projects:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/62e26bf9c35bbc3e190ae4f7/file-2Kx31Bvf1d.png" style="width: 617px;">
	 Other types of role are assigned to specific projects, and users can be assigned different roles on different projects:
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/62e26ce3a3bd513965054136/file-hoLpDxH3iw.png" style="width: 616px;">
	 Invitations will expire after 48 hours but can be renewed by clicking Manage Invitation. You can also delete invitations you no longer need.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/630747f7c1ba4b3dfdae2fa1/file-uvOZI81amI.png" style="width: 615px;"><h2>Updating a user's role</h2>
	 Clicking&nbsp;Manage User&nbsp;allows you to update a user's role(s). It is also possible to remove users with Developer,&nbsp;Editor, Data Editor&nbsp;and Viewer&nbsp;roles.
	 <img src="https://s3.amazonaws.com/helpscout.net/docs/assets/606c25df9b956f5f5cfe4092/images/6071d2a5e0324b5fdfd09a6d/file-WfFMA2dYBP.png" style="width: 667px;"><h2>Managing users for a project</h2>
	 You can also manage users with&nbsp;Developer,&nbsp;Editor,&nbsp;Data Editor&nbsp;and&nbsp;Viewer&nbsp;roles at the project level by selecting Manage Project&nbsp;from the user menu and then&nbsp;Users in the sidebar.<h2></h2>

A Data Graphs user is assigned a team role. These roles are:<ul>
	
<li>Owner&nbsp;– the person who creates the Data Graphs account is assigned the Owner role, and has super-admin rights to manage the subscription, invite users, manage the account and can perform all available actions. Other users can also be assigned the Owner role, with all the same permissions, although they cannot modify the original owner's role.</li>	
<li>Administrator –&nbsp;can manage the account, users and all available actions, but cannot manage or see the subscription and billing screens.</li>	
<li>Developer&nbsp;– can&nbsp;read Datasets and events, write Datasets, export data, manage applications and web hooks to manage API integrations.</li>	
<li>Editor&nbsp;– can read and write Datasets and Concepts and can export data</li>	
<li>Data Editor&nbsp;– can read Datasets and write Concepts</li>	
<li>Viewer&nbsp;– has read only access, can only navigate and view data</li></ul>
	 You can change a user's role across all projects in the <a href="https://app-datagraphs.io/_account/_manage/account-users">account management Users screen</a> and, for a given project, in the <a href="https://app-datagraphs.io/_account/_project/_manage/project-users">project management Users screen</a>.

Welcome to Data Graphs Support

Knowledge Base

Client SDK

API

Most popular Knowledge Base articles

Building a knowledge graph

What is a Dataset?

About the API

Managing users