If you want to reference something that already exists in the database, the so-called disambiguation must be set in the WissKI. Disambiguation is generally understood to mean the resolution of ambiguity. In the context of the WissKI system this means that it must be unambiguous in the system to which entity one refers, if one would like to refer to already existing.
An example: A location with the name Nuremberg im has already been created in the system. If a new object is created that has the collection location Nuremberg, it would be desirable that the collection location is linked to the already existing location.
To achieve this, the path for the collection location must be modeled and set so that the system offers existing locations (see Input Support, Chapter 126.96.36.199.) OR, if the location has not yet been created, creates a new one in the data pool of the locations (see Automatic Link Creation, Chapter 188.8.131.52.).
S1_collection_object → N23i_has_been_collected_by → S20_collection_process → P7_took_place_at → S39_Fundort → P87_is_identified_by → E44_Place_Appellation
So that a new location is created when new data is entered or the locations already created in the system are proposed when data is entered, the disambiguation must be set to the location so that the system looks up the locations in the data pool and searches for the location with the E44 Place Appellation entered, that is, the location name that identifies the location. A disambiguation therefore expresses what one wants to express with the entered values, in this case a place.
The entity of the path to be disambiguated to can be selected under "Edith Path":
By clicking on "Disambiguation Point" all entities in the path will be suggested to which disambiguation can be performed.
In our example the disambiguation to the location is necessary to display existing locations or to create new locations by filling in the field.