How can I import relations with Excel import?

Importing relations only works with the update import feature. This is because relations can only be created between concepts that already exist in the taxonomy. This means that in order to import an Excel taxonomy that includes relations between concepts, one has to first import only the concept structure and in a second step add the relations.

See also: How Can I Update Data With Excel Import?

In order to import relations, the concepts that are to be related have to be uniquely identifiable in the file. You can choose between URIs, skos:notations and custom attributes to identify concepts in Excel sheets. The first column of the Excel sheet has to contain the attribute that is used to identify the concepts. The same attribute has to be used to identify the concepts for creating relations.

You can use the importing relations feature to create poly-hierarchies in the Excel sheet by adding "broader" relations to concepts that already exist in the taxonomy hierarchy.

How many columns do I need to add relations, what are their headers and what should they contain?

"id" column - this column has to contain either concept URIs, skos:notations or a custom attribute

the following columns have to reproduce the hierarchical structure of the taxonomy tree already existing in the PoolParty project. If you want to import at project level, the second column has to contain concept schemes. If you only want to update a subtree, the second column can already contain concepts. Take care to import a subtree at the right node in your PoolParty thesaurus.

Columns specifying concept relations. The type of relation has to be specified in the header, the concepts that the relation should be with have to be identified using the same id as in the first column. If you chose to use the skos:notation to identify concepts in the first column, you need to use the skos:notation to identify the related concepts in this column as well.

You can add several relation columns if required.

URI / notation / custom attribute URI

scheme / concept

concept (optional)

concept (optional)

exactMatch / closeMatch / relatedMatch / broaderMatch / broader / related / custom relation URI

exactMatch / closeMatch / relatedMatch / broaderMatch / broader / related / custom relation URI (optional)

Example thesaurus structure that exists in PoolParty which we will add relations to

uri

scheme

concept

concept

notation

http://vocabulary.semantic-web.at/PoolParty/schema/Spongebob/id

http://vocabulary.semantic-web.at/spongebob/0

Character

http://vocabulary.semantic-web.at/spongebob/1

Gary

24

34

http://vocabulary.semantic-web.at/spongebob/2

Mr. Crabs

25

35

http://vocabulary.semantic-web.at/spongebob/3

Sandy

26

36

http://vocabulary.semantic-web.at/spongebob/4

Spongebob

27

37

Example of an Excel sheet using URIs to identify concepts

Contains a concept scheme and has therefore to be imported at the project node level. The basic thesuarus structure with all the concepts already has to exist in the taxonomy. Not all concepts contained in the taxonomy have to be present in the Excel sheet: only for those that are in the Excel sheet, data will be added, the other concepts will not be affected by the import. For those concepts that are present in the Excel sheet, the taxonomy tree structure has to be correct. The URIs specified in the Excel sheet need to be the URIs of the concepts in PoolParty.

Defines skos:related relations between concepts.

uri

scheme

concept

related

related

http://vocabulary.semantic-web.at/spongebob/0

Character

http://vocabulary.semantic-web.at/spongebob/1

Gary

http://vocabulary.semantic-web.at/spongebob/2

http://vocabulary.semantic-web.at/spongebob/2

Mr. Crabs

http://vocabulary.semantic-web.at/spongebob/2

http://vocabulary.semantic-web.at/spongebob/3

Sandy

http://vocabulary.semantic-web.at/spongebob/1

http://vocabulary.semantic-web.at/spongebob/2

http://vocabulary.semantic-web.at/spongebob/4

Spongebob

http://vocabulary.semantic-web.at/spongebob/3

Example of an Excel sheet using skos:notation to identify concepts

Contains no concept scheme and has therefore to be imported at the right level of the taxonomy tree. In this case, it would have to be imported at the "Character" node. Note that there doesn't have to be an entry in the related column for every single concept.

Defines a custom relation between concepts. The custom scheme containing this custom relation has to exist and be enabled for the project for this import to work.

notation

concept

http://vocabulary.semantic-web.at/PoolParty/schema/Spongebob/knows

24

Gary

25

Mr. Crabs

27

26

Sandy

27

27

Spongebob

24

Example of an Excel sheet using a custom attribute to identify concepts

Contains a concept scheme and has therefore to be imported at project level. The custom scheme containing this custom id has to exist and be enabled for the project for this import to work.

Defines a skos:relatedMatch relation between concepts.

http://vocabulary.semantic-web.at/PoolParty/schema/Spongebob/id

scheme

concept

relatedMatch

relatedMatch

Character

34

Gary

37

35

Mr. Crabs

37

36

Sandy

37

34

37

Spongebob