DIQA-Homepage - User contributions [en]

MediaWiki:Bottom-notice-ns-0

2022-07-24T10:36:00Z

WikiSysop:

<footer><div class="row">
<div class="col-md-4" style="text-align: justify;>
<h3>Important links:</h3><p>
* [[Solutions/Stop_searching_start_finding|Solutions]]
* [[Products]]
* [[Services]]
* [[Download/Get_evaluation_copy|Download evaluation copy]]
* [[Download/Purchase_license|Purchase licenses]]
* [[Company|About DIQA]]
* [[News]]
* [[Blog]]
* [[Contact]]
* [[Imprint]]
</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Find us here:</h3><p><b>DIQA Projektmanagement GmbH</b><br>Amalienbadstrasse 41 (Bau 52)<br>76227 Karlsruhe, Germany<br>Tel: +49 721 96495399<br>https://www.diqa.de<br>info@diqa-pm.de</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Microsoft partner:</h3>
<p>DIQA is certified Microsoft partner.</p><br>[[File:79px-MSISV_Logo.png|79px]]
</div>
</div></footer>

Imprint/Privacy Statement for Add-Ins

2022-07-24T10:33:25Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Kategorie=Seite
|Titel=Privacy statement for Sharepoint Add-ins/Apps
|Pfad=[[Main Page]] > [[Company]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">

;Introduction
DIQA Projektmanagement GmbH is publishing Add-ins ("Add-ins") through the Microsoft Store (at https://store.microsoft.com or https://appsource.microsoft.com/) which are installed in SharePoint on-premises or SharePoint online. These Add-ins are:
* TreeRefiner Add-in
* Easy Tagging Add-in

;Adherance to the Microsoft Store Policies
Our Add-ins are thoroughly tested and fully comply to the Microsoft Store Policies published at https://docs.microsoft.com/en-us/legal/windows/agreements/store-policies.

;No collection of personal or customer data through Add-in
After the installation and activation of the Add-in, it does not collect and submit personal or customer data to us. Although if you click in the Add-in on a URL that leads to the DIQA homepage then your visit on our homepage will be registered.

;How to contact DIQA
You can use these co-ordinates to contact us:

DIQA Prοjektmαnαgement GmbH<br>
Amalienbadstrasse 41 (Bau 52)<br>
76227 Kαrlsruhe, Germany<br>
T +49 721 96495399<br>
E ιnfo@diqa-pm.de

</div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Neuigkeiten/Linkboxes}}
</div>
</div>

Contact

2022-07-24T10:33:09Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Titel=Get in touch with DIQA
|Pfad=[[Main Page]] > [[Contact]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12">
== Just drop us an email, we will come back to you asap: ==
{{Emailformular
|Text=Hello guys at DIQA! We probably have work for you to do...
|Placeholder=
}}
== Find us here ==
<p><b>DIQA Projektmanagement GmbH</b><br>An der RaumFabrik 33c<br>76227 Karlsruhe<br>Tel: +49 721 96495399<br>http://www.diqa-pm.de<br>info@diqa-pm.de</p>

{{#display_map: Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe
|copycoords=yes
|zoom=17
}}

</div>
</div>

Imprint

2022-07-24T10:32:52Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Kategorie=Page
|Titel=Imprint and privacy statement
|Pfad=[[Main Page]] > [[Imprint]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">

;Impressum (Imprint)
Angaben gemäß § 5 TMG:

DIQA Prοjektmαnαgement GmbH<br>
Amalienbadstrasse 41 (Bau 52)<br>
76227 Kαrlsruhe<br>
T +49 721 96495399<br>
E ιnfo@diqa-pm.de

Eintragung im Handelsregister beim Amtsgericht Mannheim, Registernummer: HRB715454<br>
Vertretungsberechtigte Geschäftsführer:<br>
Dr. Mιchαel Erdmαnn, Dιpl.-Wιrtsch.-Inf. Dαnιel Hαnsch<br>
Umsatzsteueridentifikationsnummer gemäß §27 Umsatzsteuergesetz DE283037270<br>

;Nutzung der Website
Die Bedingungen gelten für alle Arten der Nutzung der Website der DIQA Projektmanagement GmbH. Durch das Aufrufen erklärt sich der Nutzer mit diesen Bedingungen und den Datenschutzvorschriften einverstanden.

SOFERN SIE NICHT MIT DIESEN BEDINGUNGEN IN GÄNZE EINVERSTANDEN SIND, VERLASSEN SIE BITTE DIESE WEBSITE.

;Geistiges Eigentum
Sofern nichts Gegenteiliges auf einer Seite dieser Website vermerkt ist, sind alle Inhalte dieser Website geistiges Eigentum der DIQA Projektmanagement GmbH. Das geistige Eigentum der DIQA Projektmanagement GmbH darf ausschließlich im Zusammenhang mit dieser Website genutzt und auf den eigenen Computer geladen werden. Eine Verwertung jedweder Art oder Veröffentlichung ist nicht gestattet. Die Urheberrechte Dritter werden berücksichtigt sofern Inhalte nicht vom Betreiber erstellt wurden. Entdecken Sie trotzdem eine Urheberrechtsverletzung auf dieser Website, dann bitten wir Sie um einen entsprechenden Hinweis. Wir werden die entsprechenden Inhalte dann umgehend entfernen bei Bekanntwerden von Rechtsverletzungen.

;Haftungsausschluss
Die bereitgestellten Informationen auf dieser Website wurden sorgfältig geprüft und werden regelmäßig aktualisiert. Jedoch kann keine Haftung oder Garantie dafür übernommen werden, dass alle Angaben zu jeder Zeit vollständig, richtig und stets aktuell sind. Dies gilt insbesondere für alle Links zu anderen Websites, auf die direkt oder indirekt verwiesen wird. Alle Angaben können ohne vorherige Ankündigung geändert, entfernt oder ergänzt werden. Gemäß § 7(1) TMG sind wir als Dienstanbieter für eigene Inhalte auf diesen Seiten nach den allgemeinen Gesetzen verantwortlich. Wir sind als Diensteanbieter gemäß §§ 8-10 TMG jedoch nicht verpflichtet, übermittelte oder gespeicherte fremde Information zu überwachen oder auf Hinweise einer rechtswidrigen Tätigkeit zu untersuchen. Die Verpflichtung zur Entfernung oder Sperrung zur Nutzung von Information nach den allgemeinen Gesetzen bleibt unberührt. Eine entsprechende Haftung ist erst ab dem Zeitpunkt der Kenntnis einer konkreten Rechtsverletzung möglich. Bei Bekanntwerden von solcher Rechtsverletzungen werden wir diese Inhalte umgehend entfernen. Unser Angebot enthält Links zu Webseiten Dritter, auf deren Inhalt wir keinen Einfluß haben. Für diese fremden Inhalte können wir deshalb keine Gewähr übernehmen. Es ist stets der jeweilige Anbieter der verlinkten Seiten für deren Inhalt verantwortlich. Rechtswidrige Inhalte waren zum Zeitpunkt der Verlinkung für uns nicht erkennbar. Bei Bekanntwerden von Rechtsverletzungen auf den verlinkten Seiten werden wir die Links sofort entfernen.

==Privacy Policy==

<p>We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the DIQA Projektmanagement GmbH. The use of the Internet pages of the DIQA Projektmanagement GmbH is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject.</p>

<p>The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable to the DIQA Projektmanagement GmbH. By means of this data protection declaration, our enterprise would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled.</p>

<p>As the controller, the DIQA Projektmanagement GmbH has implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed. For this reason, every data subject is free to transfer personal data to us via alternative means, e.g. by telephone. </p>

<h4>1. Definitions</h4>
<p>The data protection declaration of the DIQA Projektmanagement GmbH is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR). Our data protection declaration should be legible and understandable for the general public, as well as our customers and business partners. To ensure this, we would like to first explain the terminology used.</p>

<p>In this data protection declaration, we use, inter alia, the following terms:</p>

<ul style="list-style: none">
<li><h4>a) Personal data</h4>
<p>Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</p>
</li>
<li><h4>b) Data subject</h4>
<p>Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing.</p>
</li>
<li><h4>c) Processing</h4>
<p>Processing is any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. </p>
</li>
<li><h4>d) Restriction of processing</h4>
<p>Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future. </p>
</li>
<li><h4>e) Profiling</h4>
<p>Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements. </p>
</li>
<li><h4>f) Pseudonymisation</h4>
<p>Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person. </p>
</li>
<li><h4>g) Controller or controller responsible for the processing</h4>
<p>Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law. </p>
</li>
<li><h4>h) Processor</h4>
<p>Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller. </p>
</li>
<li><h4>i) Recipient</h4>
<p>Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing. </p>
</li>
<li><h4>j) Third party</h4>
<p>Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data.</p>
</li>
<li><h4>k) Consent</h4>
<p>Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. </p>
</li>
</ul>

<h4>2. Name and Address of the controller</h4>
<p>Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:

</p>

<p>DIQA Projektmanagement GmbH</p>
<p>Pfinztalstrasse 90</p>
<p>76227 Karlsruhe</p>
<p>Deutschland</p>
<p>Phone: 072160951726</p>
<p>Email: info@diqa-pm.de</p>
<p>Website: www.diqa-pm.de</p>

<h4>3. Cookies</h4>
<p>The Internet pages of the DIQA Projektmanagement GmbH use cookies. Cookies are text files that are stored in a computer system via an Internet browser.</p>

<p>Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the dats subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID.</p>

<p>Through the use of cookies, the DIQA Projektmanagement GmbH can provide the users of this website with more user-friendly services that would not be possible without the cookie setting.</p>

<p>By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies, e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user's computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie.</p>

<p>The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable.</p>

<h4>4. Collection of general data and information</h4>
<p>The website of the DIQA Projektmanagement GmbH collects a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files. Collected may be (1) the browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites, (5) the date and time of access to the Internet site, (6) an Internet protocol address (IP address), (7) the Internet service provider of the accessing system, and (8) any other similar data and information that may be used in the event of attacks on our information technology systems.</p>

<p>When using these general data and information, the DIQA Projektmanagement GmbH does not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack. Therefore, the DIQA Projektmanagement GmbH analyzes anonymously collected data and information statistically, with the aim of increasing the data protection and data security of our enterprise, and to ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from all personal data provided by a data subject.</p>

<h4>5. Contact possibility via the website </h4>
<p>The website of the DIQA Projektmanagement GmbH contains information that enables a quick electronic contact to our enterprise, as well as direct communication with us, which also includes a general address of the so-called electronic mail (e-mail address). If a data subject contacts the controller by e-mail or via a contact form, the personal data transmitted by the data subject are automatically stored. Such personal data transmitted on a voluntary basis by a data subject to the data controller are stored for the purpose of processing or contacting the data subject. There is no transfer of this personal data to third parties.</p>

<h4>6. Routine erasure and blocking of personal data</h4>
<p>The data controller shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the controller is subject to.</p>

<p>If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements.</p>

<h4>7. Rights of the data subject</h4>
<ul style="list-style: none;">
<li><h4>a) Right of confirmation</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact any employee of the controller.</p>
</li>
<li><h4>b) Right of access</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information:</p>

<ul style="list-style: none;">
<li>the purposes of the processing;</li>
<li>the categories of personal data concerned;</li>
<li>the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations;</li>
<li>where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period;</li>
<li>the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing;</li>
<li>the existence of the right to lodge a complaint with a supervisory authority;</li>
<li>where the personal data are not collected from the data subject, any available information as to their source;</li>
<li>the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject.</li>

</ul>
<p>Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organisation. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer.</p>

<p>If a data subject wishes to avail himself of this right of access, he or she may, at any time, contact any employee of the controller.</p>
</li>
<li><h4>c) Right to rectification </h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement.</p>

<p>If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact any employee of the controller.</p></li>
<li>
<h4>d) Right to erasure (Right to be forgotten) </h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary: </p>

<ul style="list-style: none;">
<li>The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.</li>
<li>The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing.</li>
<li>The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2) of the GDPR. </li>
<li>The personal data have been unlawfully processed.</li>
<li>The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.</li>
<li>The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR.</li>

</ul>
<p>If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by the DIQA Projektmanagement GmbH, he or she may, at any time, contact any employee of the controller. An employee of DIQA Projektmanagement GmbH shall promptly ensure that the erasure request is complied with immediately.</p>

<p>Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. An employees of the DIQA Projektmanagement GmbH will arrange the necessary measures in individual cases.</p>
</li>
<li><h4>e) Right of restriction of processing</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies:</p>

<ul style="list-style: none;">
<li>The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data. </li>
<li>The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead the restriction of their use instead.</li>
<li>The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defence of legal claims.</li>
<li>The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject.</li>

</ul>
<p>If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by the DIQA Projektmanagement GmbH, he or she may at any time contact any employee of the controller. The employee of the DIQA Projektmanagement GmbH will arrange the restriction of the processing. </p>
</li>
<li><h4>f) Right to data portability</h4>
<p>Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.</p>

<p>Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others.</p>

<p>In order to assert the right to data portability, the data subject may at any time contact any employee of the DIQA Projektmanagement GmbH.</p>

</li>
<li>
<h4>g) Right to object</h4>
<p>Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions.</p>

<p>The DIQA Projektmanagement GmbH shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or for the establishment, exercise or defence of legal claims.</p>

<p>If the DIQA Projektmanagement GmbH processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to the DIQA Projektmanagement GmbH to the processing for direct marketing purposes, the DIQA Projektmanagement GmbH will no longer process the personal data for these purposes.</p>

<p>In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to processing of personal data concerning him or her by the DIQA Projektmanagement GmbH for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest.</p>

<p>In order to exercise the right to object, the data subject may contact any employee of the DIQA Projektmanagement GmbH. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications.</p>
</li>
<li><h4>h) Automated individual decision-making, including profiling</h4>
<p>Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, or (3) is not based on the data subject's explicit consent.</p>

<p>If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject's explicit consent, the DIQA Projektmanagement GmbH shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision.</p>

<p>If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may, at any time, contact any employee of the DIQA Projektmanagement GmbH.</p>

</li>
<li><h4>i) Right to withdraw data protection consent </h4>
<p>Each data subject shall have the right granted by the European legislator to withdraw his or her consent to processing of his or her personal data at any time. </p>

<p>If the data subject wishes to exercise the right to withdraw the consent, he or she may, at any time, contact any employee of the DIQA Projektmanagement GmbH.</p>

</li>
</ul>
<h4>8. Data protection for applications and the application procedures</h4>
<p>The data controller shall collect and process the personal data of applicants for the purpose of the processing of the application procedure. The processing may also be carried out electronically. This is the case, in particular, if an applicant submits corresponding application documents by e-mail or by means of a web form on the website to the controller. If the data controller concludes an employment contract with an applicant, the submitted data will be stored for the purpose of processing the employment relationship in compliance with legal requirements. If no employment contract is concluded with the applicant by the controller, the application documents shall be automatically erased two months after notification of the refusal decision, provided that no other legitimate interests of the controller are opposed to the erasure. Other legitimate interest in this relation is, e.g. a burden of proof in a procedure under the General Equal Treatment Act (AGG).</p>

<h4>9. Data protection provisions about the application and use of Google Analytics (with anonymization function)</h4>
<p>On this website, the controller has integrated the component of Google Analytics (with the anonymizer function). Google Analytics is a web analytics service. Web analytics is the collection, gathering, and analysis of data about the behavior of visitors to websites. A web analysis service collects, inter alia, data about the website from which a person has come (the so-called referrer), which sub-pages were visited, or how often and for what duration a sub-page was viewed. Web analytics are mainly used for the optimization of a website and in order to carry out a cost-benefit analysis of Internet advertising.</p>

<p>The operator of the Google Analytics component is Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, United States.</p>

<p>For the web analytics through Google Analytics the controller uses the application "_gat. _anonymizeIp". By means of this application the IP address of the Internet connection of the data subject is abridged by Google and anonymised when accessing our websites from a Member State of the European Union or another Contracting State to the Agreement on the European Economic Area.</p>

<p>The purpose of the Google Analytics component is to analyze the traffic on our website. Google uses the collected data and information, inter alia, to evaluate the use of our website and to provide online reports, which show the activities on our websites, and to provide other services concerning the use of our Internet site for us.</p>

<p>Google Analytics places a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, Google is enabled to analyze the use of our website. With each call-up to one of the individual pages of this Internet site, which is operated by the controller and into which a Google Analytics component was integrated, the Internet browser on the information technology system of the data subject will automatically submit data through the Google Analytics component for the purpose of online advertising and the settlement of commissions to Google. During the course of this technical procedure, the enterprise Google gains knowledge of personal information, such as the IP address of the data subject, which serves Google, inter alia, to understand the origin of visitors and clicks, and subsequently create commission settlements.</p>

<p>The cookie is used to store personal information, such as the access time, the location from which the access was made, and the frequency of visits of our website by the data subject. With each visit to our Internet site, such personal data, including the IP address of the Internet access used by the data subject, will be transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties.

</p>

<p>The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the Internet browser used would also prevent Google Analytics from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Google Analytics may be deleted at any time via a web browser or other software programs.</p>

<p>In addition, the data subject has the possibility of objecting to a collection of data that are generated by Google Analytics, which is related to the use of this website, as well as the processing of this data by Google and the chance to preclude any such. For this purpose, the data subject must download a browser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This browser add-on tells Google Analytics through a JavaScript, that any data and information about the visits of Internet pages may not be transmitted to Google Analytics. The installation of the browser add-ons is considered an objection by Google. If the information technology system of the data subject is later deleted, formatted, or newly installed, then the data subject must reinstall the browser add-ons to disable Google Analytics. If the browser add-on was uninstalled by the data subject or any other person who is attributable to their sphere of competence, or is disabled, it is possible to execute the reinstallation or reactivation of the browser add-ons.</p>

<p>Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html. Google Analytics is further explained under the following Link https://www.google.com/analytics/.</p>

<h4>10. Data protection provisions about the application and use of Google-AdWords</h4>

<p>On this website, the controller has integrated Google AdWords. Google AdWords is a service for Internet advertising that allows the advertiser to place ads in Google search engine results and the Google advertising network. Google AdWords allows an advertiser to pre-define specific keywords with the help of which an ad on Google's search results only then displayed, when the user utilizes the search engine to retrieve a keyword-relevant search result. In the Google Advertising Network, the ads are distributed on relevant web pages using an automatic algorithm, taking into account the previously defined keywords.</p>

<p>The operating company of Google AdWords is Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, UNITED STATES.</p>

<p>The purpose of Google AdWords is the promotion of our website by the inclusion of relevant advertising on the websites of third parties and in the search engine results of the search engine Google and an insertion of third-party advertising on our website.</p>

<p>If a data subject reaches our website via a Google ad, a conversion cookie is filed on the information technology system of the data subject through Google. The definition of cookies is explained above. A conversion cookie loses its validity after 30 days and is not used to identify the data subject. If the cookie has not expired, the conversion cookie is used to check whether certain sub-pages, e.g, the shopping cart from an online shop system, were called up on our website. Through the conversion cookie, both Google and the controller can understand whether a person who reached an AdWords ad on our website generated sales, that is, executed or canceled a sale of goods.</p>

<p>The data and information collected through the use of the conversion cookie is used by Google to create visit statistics for our website. These visit statistics are used in order to determine the total number of users who have been served through AdWords ads to ascertain the success or failure of each AdWords ad and to optimize our AdWords ads in the future. Neither our company nor other Google AdWords advertisers receive information from Google that could identify the data subject.</p>

<p>The conversion cookie stores personal information, e.g. the Internet pages visited by the data subject. Each time we visit our Internet pages, personal data, including the IP address of the Internet access used by the data subject, is transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties.</p>

<p>The data subject may, at any time, prevent the setting of cookies by our website, as stated above, by means of a corresponding setting of the Internet browser used and thus permanently deny the setting of cookies. Such a setting of the Internet browser used would also prevent Google from placing a conversion cookie on the information technology system of the data subject. In addition, a cookie set by Google AdWords may be deleted at any time via the Internet browser or other software programs.</p>

<p>The data subject has a possibility of objecting to the interest based advertisement of Google. Therefore, the data subject must access from each of the browsers in use the link www.google.de/settings/ads and set the desired settings.</p>

<p>Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/.</p>

<h4>11. Data protection provisions about the application and use of LinkedIn</h4>
<p>The controller has integrated components of the LinkedIn Corporation on this website. LinkedIn is a web-based social network that enables users with existing business contacts to connect and to make new business contacts. Over 400 million registered people in more than 200 countries use LinkedIn. Thus, LinkedIn is currently the largest platform for business contacts and one of the most visited websites in the world.</p>

<p>The operating company of LinkedIn is LinkedIn Corporation, 2029 Stierlin Court Mountain View, CA 94043, UNITED STATES. For privacy matters outside of the UNITED STATES LinkedIn Ireland, Privacy Policy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ireland, is responsible.</p>

<p>With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a LinkedIn component (LinkedIn plug-in) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to the download of a display of the corresponding LinkedIn component of LinkedIn. Further information about the LinkedIn plug-in may be accessed under https://developer.linkedin.com/plugins. During the course of this technical procedure, LinkedIn gains knowledge of what specific sub-page of our website was visited by the data subject.</p>

<p>If the data subject is logged in at the same time on LinkedIn, LinkedIn detects with every call-up to our website by the data subject—and for the entire duration of their stay on our Internet site—which specific sub-page of our Internet page was visited by the data subject. This information is collected through the LinkedIn component and associated with the respective LinkedIn account of the data subject. If the data subject clicks on one of the LinkedIn buttons integrated on our website, then LinkedIn assigns this information to the personal LinkedIn user account of the data subject and stores the personal data.</p>

<p>LinkedIn receives information via the LinkedIn component that the data subject has visited our website, provided that the data subject is logged in at LinkedIn at the time of the call-up to our website. This occurs regardless of whether the person clicks on the LinkedIn button or not. If such a transmission of information to LinkedIn is not desirable for the data subject, then he or she may prevent this by logging off from their LinkedIn account before a call-up to our website is made.</p>

<p>LinkedIn provides under https://www.linkedin.com/psettings/guest-controls the possibility to unsubscribe from e-mail messages, SMS messages and targeted ads, as well as the ability to manage ad settings. LinkedIn also uses affiliates such as Eire, Google Analytics, BlueKai, DoubleClick, Nielsen, Comscore, Eloqua, and Lotame. The setting of such cookies may be denied under https://www.linkedin.com/legal/cookie-policy. The applicable privacy policy for LinkedIn is available under https://www.linkedin.com/legal/privacy-policy. The LinkedIn Cookie Policy is available under https://www.linkedin.com/legal/cookie-policy.</p>

<h4>12. Data protection provisions about the application and use of SlideShare</h4>
<p>On this website, the controller has integrated SlideShare components. LinkedIn SlideShare as a file hosting service allows you to exchange and archive presentations and other documents, such as PDF files, videos, and webinars. The file hosting service allows users to upload media content in all popular formats, with the documents either publicly-accessible or private-labeled.</p>

<p>The operating company of SlideShare is LinkedIn Corporation, 2029 Stierlin Court Mountain View, CA 94043, United States. For privacy matters outside of the United States the LinkedIn Ireland, Privacy Policy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ireland, is responsible.</p>

<p>LinkedIn SlideShare provides so-called embedded codes for the media content (e.g. presentations, PDF files, videos, photos, etc.) stored there. Embedded codes are program codes that are embedded in the Internet pages to display external content on their own website. Embedded codes allow content to be reproduced on its own website without storing it on its own server, possibly violating the right of reproduction of the respective author of the content. A further advantage of the use of an embedded code is that the respective operator of a website does not use its own storage space and the own server is thereby relieved. An embedded code may be integrated at any point on another website so that an external content may also be inserted within the own text. The purpose of using LinkedIn SlideShare is to relieve our server and to avoid copyright infringements, while at the same time using third-party content.</p>

<p>With each call-up to our Internet site, which is equipped with a SlideShare component (embedded code), this component prompts the browser that you are using to download the according embedded data from SlideShare. During the course of this technical procedure, LinkedIn gains knowledge of which specific sub-page of our website is visited by the data subject.</p>

<p>If the data subject is logged in on SlideShare at the same time, SlideShare recognizes with each call-up to our website by the data subject and for the entire duration of their stay on our Internet site which specific sub-page was visited by the data subject. This information is collected by SlideShare and assigned to the respective SlideShare account of the data subject through LinkedIn.</p>

<p>LinkedIn obtains information via the SlideShare component that the data subject has visited our website, provided that the data subject is logged in at SlideShare at the time of the call-up to our website. This occurs regardless of whether the person clicks on the embedded media data or not. If such a transmission of information to SlideShare is not desirable for the data subject, then he or she may prevent this by logging off from their SlideShare account before a call-up to our website is made.</p>

<p>LinkedIn also uses affiliates such as Eire, Google Analytics, BlueKai, DoubleClick, Nielsen, Comscore, Eloqua, and Lotame. The setting of such cookies may be denied under https://www.linkedin.com/legal/cookie-policy. The applicable data protection provisions for LinkedIn is available under https://www.linkedin.com/legal/privacy-policy.</p>

<h4>13. Data protection provisions about the application and use of Xing</h4>
<p>On this website, the controller has integrated components of XING. XING is an Internet-based social network that enables users to connect with existing business contacts and to create new business contacts. The individual users can create a personal profile of themselves at XING. Companies may, e.g. create company profiles or publish jobs on XING.</p>

<p>The operating company of XING is XING SE, Dammtorstraße 30, 20354 Hamburg, Germany.</p>

<p>With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a XING component (XING plug-in) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to download a display of the corresponding XING component of XING. Further information about the XING plug-in the may be accessed under https://dev.xing.com/plugins. During the course of this technical procedure, XING gains knowledge of what specific sub-page of our website was visited by the data subject.</p>

<p>If the data subject is logged in at the same time on XING, XING detects with every call-up to our website by the data subject—and for the entire duration of their stay on our Internet site—which specific sub-page of our Internet page was visited by the data subject. This information is collected through the XING component and associated with the respective XING account of the data subject. If the data subject clicks on the XING button integrated on our Internet site, e.g. the "Share"-button, then XING assigns this information to the personal XING user account of the data subject and stores the personal data.</p>

<p>XING receives information via the XING component that the data subject has visited our website, provided that the data subject is logged in at XING at the time of the call to our website. This occurs regardless of whether the person clicks on the XING component or not. If such a transmission of information to XING is not desirable for the data subject, then he or she can prevent this by logging off from their XING account before a call-up to our website is made.</p>

<p>The data protection provisions published by XING, which is available under https://www.xing.com/privacy, provide information on the collection, processing and use of personal data by XING. In addition, XING has published privacy notices for the XING share button under https://www.xing.com/app/share?op=data_protection.</p>

<h4>14. Legal basis for the processing </h4>
<p>Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR.
In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Art. 6(1) lit. d GDPR.
Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations which are not covered by any of the abovementioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR).
</p>

<h4>15. The legitimate interests pursued by the controller or by a third party</h4>
<p>Where the processing of personal data is based on Article 6(1) lit. f GDPR our legitimate interest is to carry out our business in favor of the well-being of all our employees and the shareholders.</p>

<h4>16. Period for which the personal data will be stored</h4>
<p>The criteria used to determine the period of storage of personal data is the respective statutory retention period. After expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract.</p>

<h4>17. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data </h4>
<p>We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner).

Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded.

Before personal data is provided by the data subject, the data subject must contact any employee. The employee clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data.
</p>

<h4>18. Existence of automated decision-making</h4>
<p>As a responsible company, we do not use automatic decision-making or profiling.</p>

<p>This Privacy Policy has been generated by the Privacy Policy Generator of the <a href="https://dg-datenschutz.de/services/external-data-protection-officer/?lang=en">DGD - Your External DPO</a> that was developed in cooperation with <a href="https://www.wbs-law.de/eng/">German Lawyers</a> from WILDE BEUGER SOLMECKE, Cologne.
</p>

* Nutzung unserer veröffentlichten Kontaktdaten
: '''Wir veröffentlichen unsere Kontaktdaten im Rahmen der Impressumspflicht. Deren Nutzung durch Dritte zur Übersendung von nicht ausdrücklich angeforderter Werbung und Informationsmaterialien widersprechen wir hiermit ausdrücklich. Wir behalten uns ausdrücklich rechtliche Schritte vor im Falle der unverlangten Zusendung von Werbeinformation.'''

;Geltendes Recht und Gerichtsbarkeit
Diese Konditionen unterliegen den Gesetzen der Bundesrepublik Deutschland. Die Parteien verpflichten sich, sich der nicht ausschließlichen Gerichtsbarkeit der deutschen Gerichte zu unterwerfen. Wenn ein Teil dieser Konditionen nichtig wird, hat dies keine Auswirkungen auf die Gültigkeit und die Einklagbarkeit der übrigen Bestimmungen. Der nichtige Teil wird durch Bestimmungen ersetzt, die gültig und rechtskräftig sind.

;Quellenangaben für verwendete Bilder und Grafiken:
Auf dieser Website werde unter anderem Bilddateien von Dritten (oder Abwandlungen davon) verwendet. Informationen zu Autor und Lizenz finden Sie auf der jeweiligen Bildseite:
* [[:File:ServiceHeader-Solutions.png]]

</div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Neuigkeiten/Linkboxes}}
</div>
</div>

MediaWiki:Bottom-notice-ns-0

2022-07-24T10:32:42Z

WikiSysop:

<footer><div class="row">
<div class="col-md-4" style="text-align: justify;>
<h3>Important links:</h3><p>
* [[Solutions/Stop_searching_start_finding|Solutions]]
* [[Products]]
* [[Services]]
* [[Download/Get_evaluation_copy|Download evaluation copy]]
* [[Download/Purchase_license|Purchase licenses]]
* [[Company|About DIQA]]
* [[News]]
* [[Blog]]
* [[Contact]]
* [[Imprint]]
</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Find us here:</h3><p><b>DIQA Projektmanagement GmbH</b><br>Amalienbadstrasse 41 (Bau 52)<br>76227 Karlsruhe, Germany<br>Tel: +49 721 96495399<br>http://www.diqa-pm.de<br>info@diqa-pm.de</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Microsoft partner:</h3>
<p>DIQA is certified Microsoft partner.</p><br>[[File:79px-MSISV_Logo.png|79px]]
</div>
</div></footer>

Contact

2022-05-13T16:25:32Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Titel=Get in touch with DIQA
|Pfad=[[Main Page]] > [[Contact]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12">
== Just drop us an email, we will come back to you asap: ==
{{Emailformular
|Text=Hello guys at DIQA! We probably have work for you to do...
|Placeholder=
}}
== Find us here ==
<p><b>DIQA Projektmanagement GmbH</b><br>An der RaumFabrik 33c<br>76227 Karlsruhe<br>Tel: +49 176 64078339<br>http://www.diqa-pm.de<br>info@diqa-pm.de</p>

{{#display_map: Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe
|copycoords=yes
|zoom=17
}}

</div>
</div>

Template:Ansprechpartner

2022-05-13T16:25:19Z

WikiSysop:

<noinclude>
{{Ansprechpartner|hansch}}
{{Ansprechpartner|erdmann}}
{{Ansprechpartner|kuehn}}
</noinclude><includeonly>{{Linkbox
|color=#a0b844
|heading=contact
|links=
{{#switch:{{{1|}}}
|hansch=<div style="text-align: center;"><html><img src="/mediawiki/images/3/3d/145px-Dhansch2.jpg" width="120" alt="Daniel Hansch"></html><br />Dipl.-Wirtsch.-Inf.<br /><strong>Daniel Hansch</strong><br />Machine Learning expert, software engineer, project manager<br />Tel.: +49-176 64078339<br />[mailto:hansch@diqa-pm.de hansch@diqa-pm.de]</div>
|erdmann=<div style="text-align: center;"><html><img src="/mediawiki/images/e/ef/145px-Merdmann2.jpg" width="120" alt="Dr Michael Erdmann"></html><br /><strong>Dr Michael Erdmann</strong><br />Software architect, consultant, project manager<br />Tel.: +49-176 64078339<br />[mailto:erdmann@diqa-pm.de erdmann@diqa-pm.de]</div>
|kuehn=<div style="text-align: center;"><html><img src="/mediawiki/images/7/78/145px-Kkuehn2.jpg" width="120" alt="Kai Kühn"></html><br />Dipl.-Inf.<br /><strong>Kai Kühn</strong><br />Consultant, Software Engineer <br />Tel.: +49-176 64078339<br />[mailto:kuehn@diqa-pm.de kuehn@diqa-pm.de]</div>
}}
}}<includeonly>

MediaWiki:Bottom-notice-ns-0

2022-05-13T16:24:57Z

WikiSysop:

<footer><div class="row">
<div class="col-md-4" style="text-align: justify;>
<h3>Important links:</h3><p>
* [[Solutions/Stop_searching_start_finding|Solutions]]
* [[Products]]
* [[Services]]
* [[Download/Get_evaluation_copy|Download evaluation copy]]
* [[Download/Purchase_license|Purchase licenses]]
* [[Company|About DIQA]]
* [[News]]
* [[Blog]]
* [[Contact]]
* [[Imprint]]
</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Find us here:</h3><p><b>DIQA Projektmanagement GmbH</b><br>Amalienbadstrasse 41 (Bau 52)<br>76227 Karlsruhe, Germany<br>Tel: +49 176 64078339<br>http://www.diqa-pm.de<br>info@diqa-pm.de</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Microsoft partner:</h3>
<p>DIQA is certified Microsoft partner.</p><br>[[File:79px-MSISV_Logo.png|79px]]
</div>
</div></footer>

MediaWiki:Lizenz TermExtractor

2022-04-29T21:44:17Z

WikiSysop:

Software License Agreement for "Easy Tagging"

ATTENTION: PLEASE READ THIS DOCUMENT CAREFULLY BEFORE DOWNLOADING AND/OR COMPLETING THIS INSTALLATION. THE INDIVIDUAL OR ENTITY RUNNING THIS INSTALLATION (THE "END-USER") AGREES TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE WITH THIS LICENSE, DO NOT COMPLETE THIS INSTALLATION. YOUR DOWNLOAD OF AND/OR THE INSTALLATION OF THIS SOLUTION CONSTITUTES ACCEPTANCE OF THIS LICENSE AGREEMENT.

Between You and DIQA Projektmanagement GmbH (DIQA) Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe, Germany

1 Subject of the agreement

1.1 The enclosed computer program(s) ("Software") and the accompanying documentation (altogether the "Subject Of Agreement") are provided to You ("Licensee") according to the terms of this agreement ("the Agreement").

2 Terms and conditions of this Agreement

2.1 Subject to the terms and conditions of this Agreement, DIQA hereby grants to Licensee a royalty-free, worldwide, non-exclusive, non-transferable license to use the Software for 30 days. Licensee must respect the license terms of the contained open source software and may not sell, rent, lease or sublicense rights in the Software, remove or alter any trademark, logo, copyright or other proprietary notices, legends, symbols or labels.

2.2 THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

2.3 The Product is designed for general office use. It is not designed or intended for use in air traffic control, mass transit systems, critical medical purposes, the operation of nuclear facilities or any other use which could result in a high risk of safety or property damage. You warrant that you will not use the Product for such purposes.

2.4 Contact info@diqa-pm.de to obtain a license for perpetual use.

Imprint/Privacy Statement for Add-Ins

2022-04-29T21:44:05Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Kategorie=Seite
|Titel=Privacy statement for Sharepoint Add-ins/Apps
|Pfad=[[Main Page]] > [[Company]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">

;Introduction
DIQA Projektmanagement GmbH is publishing Add-ins ("Add-ins") through the Microsoft Store (at https://store.microsoft.com or https://appsource.microsoft.com/) which are installed in SharePoint on-premises or SharePoint online. These Add-ins are:
* TreeRefiner Add-in
* Easy Tagging Add-in

;Adherance to the Microsoft Store Policies
Our Add-ins are thoroughly tested and fully comply to the Microsoft Store Policies published at https://docs.microsoft.com/en-us/legal/windows/agreements/store-policies.

;No collection of personal or customer data through Add-in
After the installation and activation of the Add-in, it does not collect and submit personal or customer data to us. Although if you click in the Add-in on a URL that leads to the DIQA homepage then your visit on our homepage will be registered.

;How to contact DIQA
You can use these co-ordinates to contact us:

DIQA Prοjektmαnαgement GmbH<br>
Amalienbadstrasse 41 (Bau 52)<br>
76227 Kαrlsruhe, Germany<br>
T +49 721 6ο9 517 26<br>
E ιnfo@diqa-pm.de

</div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Neuigkeiten/Linkboxes}}
</div>
</div>

Contact

2022-04-29T21:43:44Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Titel=Get in touch with DIQA
|Pfad=[[Main Page]] > [[Contact]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12">
== Just drop us an email, we will come back to you asap: ==
{{Emailformular
|Text=Hello guys at DIQA! We probably have work for you to do...
|Placeholder=
}}
== Find us here ==
<p><b>DIQA Projektmanagement GmbH</b><br>An der RaumFabrik 33c<br>76227 Karlsruhe<br>Tel: +49 721 609 517 26<br>http://www.diqa-pm.de<br>info@diqa-pm.de</p>

{{#display_map: Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe
|copycoords=yes
|zoom=17
}}

</div>
</div>

Imprint

2022-04-29T21:43:32Z

WikiSysop:

{{Seite
|Image=DIQA_banner_x150.png
|verlauf=
|Bereich=
|Kategorie=Page
|Titel=Imprint and privacy statement
|Pfad=[[Main Page]] > [[Imprint]]
|Description=Hier finden Sie Information übder die Firma DIQA.
|Keywords=DIQA, Unternehmen
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">

;Impressum (Imprint)
Angaben gemäß § 5 TMG:

DIQA Prοjektmαnαgement GmbH<br>
Amalienbadstrasse 41 (Bau 52)<br>
76227 Kαrlsruhe<br>
T +49 721 6ο9 517 26<br>
E ιnfo@diqa-pm.de

Eintragung im Handelsregister beim Amtsgericht Mannheim, Registernummer: HRB715454<br>
Vertretungsberechtigte Geschäftsführer:<br>
Dr. Mιchαel Erdmαnn, Dιpl.-Wιrtsch.-Inf. Dαnιel Hαnsch<br>
Umsatzsteueridentifikationsnummer gemäß §27 Umsatzsteuergesetz DE283037270<br>

;Nutzung der Website
Die Bedingungen gelten für alle Arten der Nutzung der Website der DIQA Projektmanagement GmbH. Durch das Aufrufen erklärt sich der Nutzer mit diesen Bedingungen und den Datenschutzvorschriften einverstanden.

SOFERN SIE NICHT MIT DIESEN BEDINGUNGEN IN GÄNZE EINVERSTANDEN SIND, VERLASSEN SIE BITTE DIESE WEBSITE.

;Geistiges Eigentum
Sofern nichts Gegenteiliges auf einer Seite dieser Website vermerkt ist, sind alle Inhalte dieser Website geistiges Eigentum der DIQA Projektmanagement GmbH. Das geistige Eigentum der DIQA Projektmanagement GmbH darf ausschließlich im Zusammenhang mit dieser Website genutzt und auf den eigenen Computer geladen werden. Eine Verwertung jedweder Art oder Veröffentlichung ist nicht gestattet. Die Urheberrechte Dritter werden berücksichtigt sofern Inhalte nicht vom Betreiber erstellt wurden. Entdecken Sie trotzdem eine Urheberrechtsverletzung auf dieser Website, dann bitten wir Sie um einen entsprechenden Hinweis. Wir werden die entsprechenden Inhalte dann umgehend entfernen bei Bekanntwerden von Rechtsverletzungen.

;Haftungsausschluss
Die bereitgestellten Informationen auf dieser Website wurden sorgfältig geprüft und werden regelmäßig aktualisiert. Jedoch kann keine Haftung oder Garantie dafür übernommen werden, dass alle Angaben zu jeder Zeit vollständig, richtig und stets aktuell sind. Dies gilt insbesondere für alle Links zu anderen Websites, auf die direkt oder indirekt verwiesen wird. Alle Angaben können ohne vorherige Ankündigung geändert, entfernt oder ergänzt werden. Gemäß § 7(1) TMG sind wir als Dienstanbieter für eigene Inhalte auf diesen Seiten nach den allgemeinen Gesetzen verantwortlich. Wir sind als Diensteanbieter gemäß §§ 8-10 TMG jedoch nicht verpflichtet, übermittelte oder gespeicherte fremde Information zu überwachen oder auf Hinweise einer rechtswidrigen Tätigkeit zu untersuchen. Die Verpflichtung zur Entfernung oder Sperrung zur Nutzung von Information nach den allgemeinen Gesetzen bleibt unberührt. Eine entsprechende Haftung ist erst ab dem Zeitpunkt der Kenntnis einer konkreten Rechtsverletzung möglich. Bei Bekanntwerden von solcher Rechtsverletzungen werden wir diese Inhalte umgehend entfernen. Unser Angebot enthält Links zu Webseiten Dritter, auf deren Inhalt wir keinen Einfluß haben. Für diese fremden Inhalte können wir deshalb keine Gewähr übernehmen. Es ist stets der jeweilige Anbieter der verlinkten Seiten für deren Inhalt verantwortlich. Rechtswidrige Inhalte waren zum Zeitpunkt der Verlinkung für uns nicht erkennbar. Bei Bekanntwerden von Rechtsverletzungen auf den verlinkten Seiten werden wir die Links sofort entfernen.

==Privacy Policy==

<p>We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the DIQA Projektmanagement GmbH. The use of the Internet pages of the DIQA Projektmanagement GmbH is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject.</p>

<p>The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable to the DIQA Projektmanagement GmbH. By means of this data protection declaration, our enterprise would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled.</p>

<p>As the controller, the DIQA Projektmanagement GmbH has implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed. For this reason, every data subject is free to transfer personal data to us via alternative means, e.g. by telephone. </p>

<h4>1. Definitions</h4>
<p>The data protection declaration of the DIQA Projektmanagement GmbH is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR). Our data protection declaration should be legible and understandable for the general public, as well as our customers and business partners. To ensure this, we would like to first explain the terminology used.</p>

<p>In this data protection declaration, we use, inter alia, the following terms:</p>

<ul style="list-style: none">
<li><h4>a) Personal data</h4>
<p>Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</p>
</li>
<li><h4>b) Data subject</h4>
<p>Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing.</p>
</li>
<li><h4>c) Processing</h4>
<p>Processing is any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. </p>
</li>
<li><h4>d) Restriction of processing</h4>
<p>Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future. </p>
</li>
<li><h4>e) Profiling</h4>
<p>Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements. </p>
</li>
<li><h4>f) Pseudonymisation</h4>
<p>Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person. </p>
</li>
<li><h4>g) Controller or controller responsible for the processing</h4>
<p>Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law. </p>
</li>
<li><h4>h) Processor</h4>
<p>Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller. </p>
</li>
<li><h4>i) Recipient</h4>
<p>Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing. </p>
</li>
<li><h4>j) Third party</h4>
<p>Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data.</p>
</li>
<li><h4>k) Consent</h4>
<p>Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. </p>
</li>
</ul>

<h4>2. Name and Address of the controller</h4>
<p>Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:

</p>

<p>DIQA Projektmanagement GmbH</p>
<p>Pfinztalstrasse 90</p>
<p>76227 Karlsruhe</p>
<p>Deutschland</p>
<p>Phone: 072160951726</p>
<p>Email: info@diqa-pm.de</p>
<p>Website: www.diqa-pm.de</p>

<h4>3. Cookies</h4>
<p>The Internet pages of the DIQA Projektmanagement GmbH use cookies. Cookies are text files that are stored in a computer system via an Internet browser.</p>

<p>Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the dats subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID.</p>

<p>Through the use of cookies, the DIQA Projektmanagement GmbH can provide the users of this website with more user-friendly services that would not be possible without the cookie setting.</p>

<p>By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies, e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user's computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie.</p>

<p>The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable.</p>

<h4>4. Collection of general data and information</h4>
<p>The website of the DIQA Projektmanagement GmbH collects a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files. Collected may be (1) the browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites, (5) the date and time of access to the Internet site, (6) an Internet protocol address (IP address), (7) the Internet service provider of the accessing system, and (8) any other similar data and information that may be used in the event of attacks on our information technology systems.</p>

<p>When using these general data and information, the DIQA Projektmanagement GmbH does not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack. Therefore, the DIQA Projektmanagement GmbH analyzes anonymously collected data and information statistically, with the aim of increasing the data protection and data security of our enterprise, and to ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from all personal data provided by a data subject.</p>

<h4>5. Contact possibility via the website </h4>
<p>The website of the DIQA Projektmanagement GmbH contains information that enables a quick electronic contact to our enterprise, as well as direct communication with us, which also includes a general address of the so-called electronic mail (e-mail address). If a data subject contacts the controller by e-mail or via a contact form, the personal data transmitted by the data subject are automatically stored. Such personal data transmitted on a voluntary basis by a data subject to the data controller are stored for the purpose of processing or contacting the data subject. There is no transfer of this personal data to third parties.</p>

<h4>6. Routine erasure and blocking of personal data</h4>
<p>The data controller shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the controller is subject to.</p>

<p>If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements.</p>

<h4>7. Rights of the data subject</h4>
<ul style="list-style: none;">
<li><h4>a) Right of confirmation</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact any employee of the controller.</p>
</li>
<li><h4>b) Right of access</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information:</p>

<ul style="list-style: none;">
<li>the purposes of the processing;</li>
<li>the categories of personal data concerned;</li>
<li>the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations;</li>
<li>where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period;</li>
<li>the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing;</li>
<li>the existence of the right to lodge a complaint with a supervisory authority;</li>
<li>where the personal data are not collected from the data subject, any available information as to their source;</li>
<li>the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject.</li>

</ul>
<p>Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organisation. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer.</p>

<p>If a data subject wishes to avail himself of this right of access, he or she may, at any time, contact any employee of the controller.</p>
</li>
<li><h4>c) Right to rectification </h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement.</p>

<p>If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact any employee of the controller.</p></li>
<li>
<h4>d) Right to erasure (Right to be forgotten) </h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary: </p>

<ul style="list-style: none;">
<li>The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.</li>
<li>The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing.</li>
<li>The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2) of the GDPR. </li>
<li>The personal data have been unlawfully processed.</li>
<li>The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.</li>
<li>The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR.</li>

</ul>
<p>If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by the DIQA Projektmanagement GmbH, he or she may, at any time, contact any employee of the controller. An employee of DIQA Projektmanagement GmbH shall promptly ensure that the erasure request is complied with immediately.</p>

<p>Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. An employees of the DIQA Projektmanagement GmbH will arrange the necessary measures in individual cases.</p>
</li>
<li><h4>e) Right of restriction of processing</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies:</p>

<ul style="list-style: none;">
<li>The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data. </li>
<li>The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead the restriction of their use instead.</li>
<li>The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defence of legal claims.</li>
<li>The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject.</li>

</ul>
<p>If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by the DIQA Projektmanagement GmbH, he or she may at any time contact any employee of the controller. The employee of the DIQA Projektmanagement GmbH will arrange the restriction of the processing. </p>
</li>
<li><h4>f) Right to data portability</h4>
<p>Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.</p>

<p>Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others.</p>

<p>In order to assert the right to data portability, the data subject may at any time contact any employee of the DIQA Projektmanagement GmbH.</p>

</li>
<li>
<h4>g) Right to object</h4>
<p>Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions.</p>

<p>The DIQA Projektmanagement GmbH shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or for the establishment, exercise or defence of legal claims.</p>

<p>If the DIQA Projektmanagement GmbH processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to the DIQA Projektmanagement GmbH to the processing for direct marketing purposes, the DIQA Projektmanagement GmbH will no longer process the personal data for these purposes.</p>

<p>In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to processing of personal data concerning him or her by the DIQA Projektmanagement GmbH for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest.</p>

<p>In order to exercise the right to object, the data subject may contact any employee of the DIQA Projektmanagement GmbH. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications.</p>
</li>
<li><h4>h) Automated individual decision-making, including profiling</h4>
<p>Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, or (3) is not based on the data subject's explicit consent.</p>

<p>If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject's explicit consent, the DIQA Projektmanagement GmbH shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision.</p>

<p>If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may, at any time, contact any employee of the DIQA Projektmanagement GmbH.</p>

</li>
<li><h4>i) Right to withdraw data protection consent </h4>
<p>Each data subject shall have the right granted by the European legislator to withdraw his or her consent to processing of his or her personal data at any time. </p>

<p>If the data subject wishes to exercise the right to withdraw the consent, he or she may, at any time, contact any employee of the DIQA Projektmanagement GmbH.</p>

</li>
</ul>
<h4>8. Data protection for applications and the application procedures</h4>
<p>The data controller shall collect and process the personal data of applicants for the purpose of the processing of the application procedure. The processing may also be carried out electronically. This is the case, in particular, if an applicant submits corresponding application documents by e-mail or by means of a web form on the website to the controller. If the data controller concludes an employment contract with an applicant, the submitted data will be stored for the purpose of processing the employment relationship in compliance with legal requirements. If no employment contract is concluded with the applicant by the controller, the application documents shall be automatically erased two months after notification of the refusal decision, provided that no other legitimate interests of the controller are opposed to the erasure. Other legitimate interest in this relation is, e.g. a burden of proof in a procedure under the General Equal Treatment Act (AGG).</p>

<h4>9. Data protection provisions about the application and use of Google Analytics (with anonymization function)</h4>
<p>On this website, the controller has integrated the component of Google Analytics (with the anonymizer function). Google Analytics is a web analytics service. Web analytics is the collection, gathering, and analysis of data about the behavior of visitors to websites. A web analysis service collects, inter alia, data about the website from which a person has come (the so-called referrer), which sub-pages were visited, or how often and for what duration a sub-page was viewed. Web analytics are mainly used for the optimization of a website and in order to carry out a cost-benefit analysis of Internet advertising.</p>

<p>The operator of the Google Analytics component is Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, United States.</p>

<p>For the web analytics through Google Analytics the controller uses the application "_gat. _anonymizeIp". By means of this application the IP address of the Internet connection of the data subject is abridged by Google and anonymised when accessing our websites from a Member State of the European Union or another Contracting State to the Agreement on the European Economic Area.</p>

<p>The purpose of the Google Analytics component is to analyze the traffic on our website. Google uses the collected data and information, inter alia, to evaluate the use of our website and to provide online reports, which show the activities on our websites, and to provide other services concerning the use of our Internet site for us.</p>

<p>Google Analytics places a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, Google is enabled to analyze the use of our website. With each call-up to one of the individual pages of this Internet site, which is operated by the controller and into which a Google Analytics component was integrated, the Internet browser on the information technology system of the data subject will automatically submit data through the Google Analytics component for the purpose of online advertising and the settlement of commissions to Google. During the course of this technical procedure, the enterprise Google gains knowledge of personal information, such as the IP address of the data subject, which serves Google, inter alia, to understand the origin of visitors and clicks, and subsequently create commission settlements.</p>

<p>The cookie is used to store personal information, such as the access time, the location from which the access was made, and the frequency of visits of our website by the data subject. With each visit to our Internet site, such personal data, including the IP address of the Internet access used by the data subject, will be transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties.

</p>

<p>The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the Internet browser used would also prevent Google Analytics from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Google Analytics may be deleted at any time via a web browser or other software programs.</p>

<p>In addition, the data subject has the possibility of objecting to a collection of data that are generated by Google Analytics, which is related to the use of this website, as well as the processing of this data by Google and the chance to preclude any such. For this purpose, the data subject must download a browser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This browser add-on tells Google Analytics through a JavaScript, that any data and information about the visits of Internet pages may not be transmitted to Google Analytics. The installation of the browser add-ons is considered an objection by Google. If the information technology system of the data subject is later deleted, formatted, or newly installed, then the data subject must reinstall the browser add-ons to disable Google Analytics. If the browser add-on was uninstalled by the data subject or any other person who is attributable to their sphere of competence, or is disabled, it is possible to execute the reinstallation or reactivation of the browser add-ons.</p>

<p>Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html. Google Analytics is further explained under the following Link https://www.google.com/analytics/.</p>

<h4>10. Data protection provisions about the application and use of Google-AdWords</h4>

<p>On this website, the controller has integrated Google AdWords. Google AdWords is a service for Internet advertising that allows the advertiser to place ads in Google search engine results and the Google advertising network. Google AdWords allows an advertiser to pre-define specific keywords with the help of which an ad on Google's search results only then displayed, when the user utilizes the search engine to retrieve a keyword-relevant search result. In the Google Advertising Network, the ads are distributed on relevant web pages using an automatic algorithm, taking into account the previously defined keywords.</p>

<p>The operating company of Google AdWords is Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, UNITED STATES.</p>

<p>The purpose of Google AdWords is the promotion of our website by the inclusion of relevant advertising on the websites of third parties and in the search engine results of the search engine Google and an insertion of third-party advertising on our website.</p>

<p>If a data subject reaches our website via a Google ad, a conversion cookie is filed on the information technology system of the data subject through Google. The definition of cookies is explained above. A conversion cookie loses its validity after 30 days and is not used to identify the data subject. If the cookie has not expired, the conversion cookie is used to check whether certain sub-pages, e.g, the shopping cart from an online shop system, were called up on our website. Through the conversion cookie, both Google and the controller can understand whether a person who reached an AdWords ad on our website generated sales, that is, executed or canceled a sale of goods.</p>

<p>The data and information collected through the use of the conversion cookie is used by Google to create visit statistics for our website. These visit statistics are used in order to determine the total number of users who have been served through AdWords ads to ascertain the success or failure of each AdWords ad and to optimize our AdWords ads in the future. Neither our company nor other Google AdWords advertisers receive information from Google that could identify the data subject.</p>

<p>The conversion cookie stores personal information, e.g. the Internet pages visited by the data subject. Each time we visit our Internet pages, personal data, including the IP address of the Internet access used by the data subject, is transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties.</p>

<p>The data subject may, at any time, prevent the setting of cookies by our website, as stated above, by means of a corresponding setting of the Internet browser used and thus permanently deny the setting of cookies. Such a setting of the Internet browser used would also prevent Google from placing a conversion cookie on the information technology system of the data subject. In addition, a cookie set by Google AdWords may be deleted at any time via the Internet browser or other software programs.</p>

<p>The data subject has a possibility of objecting to the interest based advertisement of Google. Therefore, the data subject must access from each of the browsers in use the link www.google.de/settings/ads and set the desired settings.</p>

<p>Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/.</p>

<h4>11. Data protection provisions about the application and use of LinkedIn</h4>
<p>The controller has integrated components of the LinkedIn Corporation on this website. LinkedIn is a web-based social network that enables users with existing business contacts to connect and to make new business contacts. Over 400 million registered people in more than 200 countries use LinkedIn. Thus, LinkedIn is currently the largest platform for business contacts and one of the most visited websites in the world.</p>

<p>The operating company of LinkedIn is LinkedIn Corporation, 2029 Stierlin Court Mountain View, CA 94043, UNITED STATES. For privacy matters outside of the UNITED STATES LinkedIn Ireland, Privacy Policy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ireland, is responsible.</p>

<p>With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a LinkedIn component (LinkedIn plug-in) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to the download of a display of the corresponding LinkedIn component of LinkedIn. Further information about the LinkedIn plug-in may be accessed under https://developer.linkedin.com/plugins. During the course of this technical procedure, LinkedIn gains knowledge of what specific sub-page of our website was visited by the data subject.</p>

<p>If the data subject is logged in at the same time on LinkedIn, LinkedIn detects with every call-up to our website by the data subject—and for the entire duration of their stay on our Internet site—which specific sub-page of our Internet page was visited by the data subject. This information is collected through the LinkedIn component and associated with the respective LinkedIn account of the data subject. If the data subject clicks on one of the LinkedIn buttons integrated on our website, then LinkedIn assigns this information to the personal LinkedIn user account of the data subject and stores the personal data.</p>

<p>LinkedIn receives information via the LinkedIn component that the data subject has visited our website, provided that the data subject is logged in at LinkedIn at the time of the call-up to our website. This occurs regardless of whether the person clicks on the LinkedIn button or not. If such a transmission of information to LinkedIn is not desirable for the data subject, then he or she may prevent this by logging off from their LinkedIn account before a call-up to our website is made.</p>

<p>LinkedIn provides under https://www.linkedin.com/psettings/guest-controls the possibility to unsubscribe from e-mail messages, SMS messages and targeted ads, as well as the ability to manage ad settings. LinkedIn also uses affiliates such as Eire, Google Analytics, BlueKai, DoubleClick, Nielsen, Comscore, Eloqua, and Lotame. The setting of such cookies may be denied under https://www.linkedin.com/legal/cookie-policy. The applicable privacy policy for LinkedIn is available under https://www.linkedin.com/legal/privacy-policy. The LinkedIn Cookie Policy is available under https://www.linkedin.com/legal/cookie-policy.</p>

<h4>12. Data protection provisions about the application and use of SlideShare</h4>
<p>On this website, the controller has integrated SlideShare components. LinkedIn SlideShare as a file hosting service allows you to exchange and archive presentations and other documents, such as PDF files, videos, and webinars. The file hosting service allows users to upload media content in all popular formats, with the documents either publicly-accessible or private-labeled.</p>

<p>The operating company of SlideShare is LinkedIn Corporation, 2029 Stierlin Court Mountain View, CA 94043, United States. For privacy matters outside of the United States the LinkedIn Ireland, Privacy Policy Issues, Wilton Plaza, Wilton Place, Dublin 2, Ireland, is responsible.</p>

<p>LinkedIn SlideShare provides so-called embedded codes for the media content (e.g. presentations, PDF files, videos, photos, etc.) stored there. Embedded codes are program codes that are embedded in the Internet pages to display external content on their own website. Embedded codes allow content to be reproduced on its own website without storing it on its own server, possibly violating the right of reproduction of the respective author of the content. A further advantage of the use of an embedded code is that the respective operator of a website does not use its own storage space and the own server is thereby relieved. An embedded code may be integrated at any point on another website so that an external content may also be inserted within the own text. The purpose of using LinkedIn SlideShare is to relieve our server and to avoid copyright infringements, while at the same time using third-party content.</p>

<p>With each call-up to our Internet site, which is equipped with a SlideShare component (embedded code), this component prompts the browser that you are using to download the according embedded data from SlideShare. During the course of this technical procedure, LinkedIn gains knowledge of which specific sub-page of our website is visited by the data subject.</p>

<p>If the data subject is logged in on SlideShare at the same time, SlideShare recognizes with each call-up to our website by the data subject and for the entire duration of their stay on our Internet site which specific sub-page was visited by the data subject. This information is collected by SlideShare and assigned to the respective SlideShare account of the data subject through LinkedIn.</p>

<p>LinkedIn obtains information via the SlideShare component that the data subject has visited our website, provided that the data subject is logged in at SlideShare at the time of the call-up to our website. This occurs regardless of whether the person clicks on the embedded media data or not. If such a transmission of information to SlideShare is not desirable for the data subject, then he or she may prevent this by logging off from their SlideShare account before a call-up to our website is made.</p>

<p>LinkedIn also uses affiliates such as Eire, Google Analytics, BlueKai, DoubleClick, Nielsen, Comscore, Eloqua, and Lotame. The setting of such cookies may be denied under https://www.linkedin.com/legal/cookie-policy. The applicable data protection provisions for LinkedIn is available under https://www.linkedin.com/legal/privacy-policy.</p>

<h4>13. Data protection provisions about the application and use of Xing</h4>
<p>On this website, the controller has integrated components of XING. XING is an Internet-based social network that enables users to connect with existing business contacts and to create new business contacts. The individual users can create a personal profile of themselves at XING. Companies may, e.g. create company profiles or publish jobs on XING.</p>

<p>The operating company of XING is XING SE, Dammtorstraße 30, 20354 Hamburg, Germany.</p>

<p>With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a XING component (XING plug-in) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to download a display of the corresponding XING component of XING. Further information about the XING plug-in the may be accessed under https://dev.xing.com/plugins. During the course of this technical procedure, XING gains knowledge of what specific sub-page of our website was visited by the data subject.</p>

<p>If the data subject is logged in at the same time on XING, XING detects with every call-up to our website by the data subject—and for the entire duration of their stay on our Internet site—which specific sub-page of our Internet page was visited by the data subject. This information is collected through the XING component and associated with the respective XING account of the data subject. If the data subject clicks on the XING button integrated on our Internet site, e.g. the "Share"-button, then XING assigns this information to the personal XING user account of the data subject and stores the personal data.</p>

<p>XING receives information via the XING component that the data subject has visited our website, provided that the data subject is logged in at XING at the time of the call to our website. This occurs regardless of whether the person clicks on the XING component or not. If such a transmission of information to XING is not desirable for the data subject, then he or she can prevent this by logging off from their XING account before a call-up to our website is made.</p>

<p>The data protection provisions published by XING, which is available under https://www.xing.com/privacy, provide information on the collection, processing and use of personal data by XING. In addition, XING has published privacy notices for the XING share button under https://www.xing.com/app/share?op=data_protection.</p>

<h4>14. Legal basis for the processing </h4>
<p>Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR.
In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Art. 6(1) lit. d GDPR.
Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations which are not covered by any of the abovementioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR).
</p>

<h4>15. The legitimate interests pursued by the controller or by a third party</h4>
<p>Where the processing of personal data is based on Article 6(1) lit. f GDPR our legitimate interest is to carry out our business in favor of the well-being of all our employees and the shareholders.</p>

<h4>16. Period for which the personal data will be stored</h4>
<p>The criteria used to determine the period of storage of personal data is the respective statutory retention period. After expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract.</p>

<h4>17. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data </h4>
<p>We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner).

Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded.

Before personal data is provided by the data subject, the data subject must contact any employee. The employee clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data.
</p>

<h4>18. Existence of automated decision-making</h4>
<p>As a responsible company, we do not use automatic decision-making or profiling.</p>

<p>This Privacy Policy has been generated by the Privacy Policy Generator of the <a href="https://dg-datenschutz.de/services/external-data-protection-officer/?lang=en">DGD - Your External DPO</a> that was developed in cooperation with <a href="https://www.wbs-law.de/eng/">German Lawyers</a> from WILDE BEUGER SOLMECKE, Cologne.
</p>

* Nutzung unserer veröffentlichten Kontaktdaten
: '''Wir veröffentlichen unsere Kontaktdaten im Rahmen der Impressumspflicht. Deren Nutzung durch Dritte zur Übersendung von nicht ausdrücklich angeforderter Werbung und Informationsmaterialien widersprechen wir hiermit ausdrücklich. Wir behalten uns ausdrücklich rechtliche Schritte vor im Falle der unverlangten Zusendung von Werbeinformation.'''

;Geltendes Recht und Gerichtsbarkeit
Diese Konditionen unterliegen den Gesetzen der Bundesrepublik Deutschland. Die Parteien verpflichten sich, sich der nicht ausschließlichen Gerichtsbarkeit der deutschen Gerichte zu unterwerfen. Wenn ein Teil dieser Konditionen nichtig wird, hat dies keine Auswirkungen auf die Gültigkeit und die Einklagbarkeit der übrigen Bestimmungen. Der nichtige Teil wird durch Bestimmungen ersetzt, die gültig und rechtskräftig sind.

;Quellenangaben für verwendete Bilder und Grafiken:
Auf dieser Website werde unter anderem Bilddateien von Dritten (oder Abwandlungen davon) verwendet. Informationen zu Autor und Lizenz finden Sie auf der jeweiligen Bildseite:
* [[:File:ServiceHeader-Solutions.png]]

</div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Neuigkeiten/Linkboxes}}
</div>
</div>

MediaWiki:Bottom-notice-ns-0

2022-04-29T21:43:18Z

WikiSysop:

<footer><div class="row">
<div class="col-md-4" style="text-align: justify;>
<h3>Important links:</h3><p>
* [[Solutions/Stop_searching_start_finding|Solutions]]
* [[Products]]
* [[Services]]
* [[Download/Get_evaluation_copy|Download evaluation copy]]
* [[Download/Purchase_license|Purchase licenses]]
* [[Company|About DIQA]]
* [[News]]
* [[Blog]]
* [[Contact]]
* [[Imprint]]
</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Find us here:</h3><p><b>DIQA Projektmanagement GmbH</b><br>Amalienbadstrasse 41 (Bau 52)<br>76227 Karlsruhe, Germany<br>Tel: +49 721 609 517 26<br>http://www.diqa-pm.de<br>info@diqa-pm.de</p>
</div>
<div class="col-md-4" style="text-align: justify;>
<h3>Microsoft partner:</h3>
<p>DIQA is certified Microsoft partner.</p><br>[[File:79px-MSISV_Logo.png|79px]]
</div>
</div></footer>

MediaWiki:Lizenz GRASP

2022-04-29T21:43:04Z

WikiSysop:

Software License Agreement for GRASP v1.x

ATTENTION: PLEASE READ THIS DOCUMENT CAREFULLY BEFORE DOWNLOADING AND/OR COMPLETING THIS INSTALLATION. THE INDIVIDUAL OR ENTITY RUNNING THIS INSTALLATION (THE "END-USER") AGREES TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE WITH THIS LICENSE, DO NOT COMPLETE THIS INSTALLATION. YOUR DOWNLOAD OF AND/OR THE INSTALLATION OF THIS SOLUTION CONSTITUTES ACCEPTANCE OF THIS LICENSE AGREEMENT.

Between You and DIQA Projektmanagement GmbH (DIQA) Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe, Germany

1 Subject of the agreement

1.1 The enclosed computer program(s) ("Software") and the accompanying documentation (altogether the "Subject Of Agreement") are provided to You ("Licensee") according to the terms of this agreement ("the Agreement").

2 Terms and conditions of this Agreement

2.1 Subject to the terms and conditions of this Agreement, DIQA hereby grants to Licensee a royalty-free, worldwide, non-exclusive, non-transferable license to use the Software for 30 days. Licensee must respect the license terms of the contained open source software and may not sell, rent, lease or sublicense rights in the Software, remove or alter any trademark, logo, copyright or other proprietary notices, legends, symbols or labels.

2.2 THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

2.3 The Product is designed for general office use. It is not designed or intended for use in air traffic control, mass transit systems, critical medical purposes, the operation of nuclear facilities or any other use which could result in a high risk of safety or property damage. You warrant that you will not use the Product for such purposes.

2.4 Contact info@diqa-pm.de to obtain a license for perpetual use.

MediaWiki:Lizenz PowerSearch

2022-04-29T21:42:52Z

WikiSysop:

Software License Agreement for Power-Search 1.x

ATTENTION: PLEASE READ THIS DOCUMENT CAREFULLY BEFORE DOWNLOADING AND/OR COMPLETING THIS INSTALLATION. THE INDIVIDUAL OR ENTITY RUNNING THIS INSTALLATION (THE "END-USER") AGREES TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE WITH THIS LICENSE, DO NOT COMPLETE THIS INSTALLATION. YOUR DOWNLOAD OF AND/OR THE INSTALLATION OF THIS SOLUTION CONSTITUTES ACCEPTANCE OF THIS LICENSE AGREEMENT.

Between You and DIQA Projektmanagement GmbH (DIQA) Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe, Germany

1 Subject of the agreement

1.1 The enclosed computer program(s) ("Software") and the accompanying documentation (altogether the "Subject Of Agreement") are provided to You ("Licensee") according to the terms of this agreement ("the Agreement").

2 Terms and conditions of this Agreement

2.1 Subject to the terms and conditions of this Agreement, DIQA hereby grants to Licensee a royalty-free, worldwide, non-exclusive, non-transferable license to use the Software for 30 days. Licensee must respect the license terms of the contained open source software and may not sell, rent, lease or sublicense rights in the Software, remove or alter any trademark, logo, copyright or other proprietary notices, legends, symbols or labels.

2.2 THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

2.3 The Product is designed for general office use. It is not designed or intended for use in air traffic control, mass transit systems, critical medical purposes, the operation of nuclear facilities or any other use which could result in a high risk of safety or property damage. You warrant that you will not use the Product for such purposes.

2.4 Contact info@diqa-pm.de to obtain a license for perpetual use.

MediaWiki:Lizenz SemanticSearch

2022-04-29T21:42:32Z

WikiSysop:

Software License Agreement for Semantic Search WebParts v2.x

ATTENTION: PLEASE READ THIS DOCUMENT CAREFULLY BEFORE DOWNLOADING AND/OR COMPLETING THIS INSTALLATION. THE INDIVIDUAL OR ENTITY RUNNING THIS INSTALLATION (THE "END-USER") AGREES TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE WITH THIS LICENSE, DO NOT COMPLETE THIS INSTALLATION. YOUR DOWNLOAD OF AND/OR THE INSTALLATION OF THIS SOLUTION CONSTITUTES ACCEPTANCE OF THIS LICENSE AGREEMENT.

Between You and DIQA Projektmanagement GmbH (DIQA) Amalienbadstrasse 41 (Bau 52) 76227 Karlsruhe, Germany

1 Subject of the agreement

1.1 The enclosed computer program(s) ("Software") and the accompanying documentation (altogether the "Subject Of Agreement") are provided to You ("Licensee") according to the terms of this agreement ("the Agreement").

2 Terms and conditions of this Agreement

2.1 Subject to the terms and conditions of this Agreement, DIQA hereby grants to Licensee a royalty-free, worldwide, non-exclusive, non-transferable license to use the Software for 30 days. Licensee must respect the license terms of the contained open source software and may not sell, rent, lease or sublicense rights in the Software, remove or alter any trademark, logo, copyright or other proprietary notices, legends, symbols or labels.

2.2 THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

2.3 The Product is designed for general office use. It is not designed or intended for use in air traffic control, mass transit systems, critical medical purposes, the operation of nuclear facilities or any other use which could result in a high risk of safety or property damage. You warrant that you will not use the Product for such purposes.

2.4 Contact info@diqa-pm.de to obtain a license for perpetual use.

Contact form

2021-11-05T08:38:17Z

WikiSysop: Redirected page to Contact

#REDIRECT [[Contact]]

Blog/Automatically process shared inboxes in O365

2021-05-10T15:30:06Z

WikiSysop:

{{BlogHeader
|Titel=O365: Automatically process shared inboxes
|News image=File:EasyTaggingText.png
|Publication date=2021/05/10
|Published=1
|Keywords=sharepoint, office 365, o365
|SEO-Description=This App scans shared inboxes for new emails and forwards them to the appropriate recipient for further processing ⇒reade more!
|Description=The new "Email Dispatcher"-feature of the Easy Tagging App learns to assign emails in shared inboxes to classes and automatically forwards them to specific email addresses. This reduces the time needed to monitor and process shared mailboxes, like support@yourcompany.com, or inquiries@yourdepartment.com.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Managing shared inboxes, like support@yourcompany.com, or inquiries@yourdepartment.com, can be errorprone and time consuming: a group of persons are scanning incoming emails from the inbox, and forwarding them to their email inbox before they reply to the customer, colleague, or other external stakeholder. This approach requires that the persons regularily go through all emails in the shared inbox, read and understand if they should reply to an specific email.
</p>
<p>
You can improve this process if you teach the Easy Tagging App to assign emails to a set of classes, like: job applications, inquiries, issues, invocies etc. In a second step, the App scans a shared inbox periodically for new emails, classifies them and forwards them to the recipient who is assigned to a class. This allows you to automate the process and each email is directed to a responsible person in a timely manner.
</p>
<p>
<big>The following steps assume that you have Sharepoint Online/Office 365 and a shared inbox that contains a couple of emails. Further you should be able to assign each email to a specific set of classes, like invoices, job applications etc. After you have completed these steps, your shared inbox will be scanned periodically for new emails, which will be analysed, categorized and forwarded to the recipient who is associated to the class.</big></p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=1G9apnEyH9Q
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare a library of example emails</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset for your classes of emails ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "email categories"
# Create a term for each email class that is kept in your shared inbox, like: e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Terms1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a document library that will contain the emails used for the teach-in ===
# Open the site contents of your site
# Add a library, e.g. "Examples for emails"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Emailslib1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Create a column for your emails library that contains the class of each example email ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "email category"
# Select "managed metadata" as type
# In the term set settings: select the termset "email categories" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Col1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Copy example emails from the shared inbox to the library ===
# Open the shared inbox in a Outlook client and copy the emails into the library (you will receive better classification results with more examples).
# Tag each example by assigning a term to it.
# As soon as you have provided each example email with a tag, you can initiate the training.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Copy1.PNG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Teach-in the Easy Tagging App</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create an "Email Dispatcher Task" and process the shared inbox automatically</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Email Dispatcher task ===
# Open the Easy Tagging App default page, activate the "predictors and taggers"-tab.
# Create a Mail Dispatcher task which uses the Predictor to classify new emails in your shared inbox.
# Associate each classification term with a recipient mail address.
# You can set a schedule which launches the Dispatcher regularily, for example each hour or once a day.
# You can launch the dispatcher at any time manually by clicking on "start".
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagger1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the Mail Dispatcher task manually ===
# Click on the "START" action link to launch the Mail Dispatcher task.
# The dispatcher scans the shared inbox for new emails, performs an analysis and a classification, and forwards each email to the recipient associated with a class.
# After a dispatcher run you can inspect the dispatcher log.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Run1.PNG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Create predictors that process your document libraries automatically, e.g.:
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=1G9apnEyH9Q}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Automatically process shared inboxes in O365

2021-05-10T15:27:24Z

WikiSysop:

Blog/Automatically process shared inboxes in O365

2021-05-10T14:21:46Z

WikiSysop:

Blog/Automatically process shared inboxes in O365

2021-05-10T14:20:09Z

WikiSysop:

File:Run1.PNG

2021-05-10T14:17:02Z

WikiSysop:

Blog/Automatically process shared inboxes in O365

2021-05-10T13:08:24Z

WikiSysop:

{{BlogHeader
|Titel=O365: Automatically process shared inboxes
|News image=File:EasyTaggingText.png
|Publication date=2021/05/10
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=This App scans shared inboxes for new emails and forwards them to the appropriate recipient for further processing ⇒reade more!
|Description=The new "Email Dispatcher"-feature of the Easy Tagging App learns to assign emails in shared inboxes to classes and automatically forwards them to specific email addresses. This reduces the time needed to monitor and process shared mailboxes, like support@yourcompany.com, or inquiries@yourdepartment.com.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Managing shared inboxes, like support@yourcompany.com, or inquiries@yourdepartment.com, can be errorprone and time consuming: a group of persons are scanning incoming emails from the inbox, and forwarding them to their email inbox before they reply to the customer, colleague, or other external stakeholder. This approach requires that the persons regularily go through all emails in the shared inbox, read and understand if they should reply to an specific email.
</p>
<p>
You can improve this process if you teach the Easy Tagging App to assign emails to a set of classes, like: job applications, inquiries, issues, invocies etc. In a second step, the App scans a shared inbox periodically for new emails, classifies them and forwards them to the recipient who is assigned to a class. This allows you to automate the process and each email is directed to a responsible person in a timely manner.
</p>
<p>
<big>The following steps assume that you have Sharepoint Online/Office 365 and a shared inbox that contains a couple of emails. Further you should be able to assign each email to a specific set of classes, like invoices, job applications etc.</big></p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=1G9apnEyH9Q
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Teach-in the Easy Tagging App</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset for your classes of emails ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "email categories"
# Create a term for each email class that is kept in your shared inbox, like: e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Terms1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a document library that will contain the emails used for the teach-in ===
# Open the site contents of your site
# Add a library, e.g. "Examples for emails"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Emailslib1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Create a column for your emails library that contains the class of each example email ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "email category"
# Select "managed metadata" as type
# In the term set settings: select the termset "email categories" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Col1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Copy example emails from the shared inbox to the library ===
# Open the shared inbox in a Outlook client and copy the emails into the library (you will receive better classification results with more examples).
# Tag each example by assigning a term to it.
# As soon as you have provided each example email with a tag, you can initiate the training.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Copy1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 7. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 8. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 9. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>

</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

File:Tagger1.PNG

2021-05-10T13:04:45Z

WikiSysop:

File:Wiz1.PNG

2021-05-10T12:59:53Z

WikiSysop:

Blog/Automatically process shared inboxes in O365

2021-05-10T12:56:01Z

WikiSysop:

{{BlogHeader
|Titel=O365: Automatically process shared inboxes
|News image=File:EasyTaggingText.png
|Publication date=2021/05/10
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=This App scans shared inboxes for new emails and forwards them to the appropriate recipient for further processing ⇒reade more!
|Description=The new "Email Dispatcher"-feature of the Easy Tagging App learns to assign emails in shared inboxes to classes and automatically forwards them to specific email addresses. This reduces the time needed to monitor and process shared mailboxes, like support@yourcompany.com, or inquiries@yourdepartment.com.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Managing shared inboxes, like support@yourcompany.com, or inquiries@yourdepartment.com, can be errorprone and time consuming: a group of persons are scanning incoming emails from the inbox, and forwarding them to their email inbox before they reply to the customer, colleague, or other external stakeholder. This approach requires that the persons regularily go through all emails in the shared inbox, read and understand if they should reply to an specific email.
</p>
<p>
You can improve this process if you teach the Easy Tagging App to assign emails to a set of classes, like: job applications, inquiries, issues, invocies etc. In a second step, the App scans a shared inbox periodically for new emails, classifies them and forwards them to the recipient who is assigned to a class. This allows you to automate the process and each email is directed to a responsible person in a timely manner.
</p>
<p>
<big>The following steps assume that you have Sharepoint Online/Office 365 and a shared inbox that contains a couple of emails. Further you should be able to assign each email to a specific set of classes, like invoices, job applications etc.</big></p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=1G9apnEyH9Q
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Teach-in the Easy Tagging App</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset for your classes of emails ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "email categories"
# Create a term for each email class that is kept in your shared inbox, like: e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Terms1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a document library that will contain the emails used for the teach-in ===
# Open the site contents of your site
# Add a library, e.g. "Examples for emails"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Emailslib1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Create a column for your emails library that contains the class of each example email ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "email category"
# Select "managed metadata" as type
# In the term set settings: select the termset "email categories" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Col1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Copy example emails from the shared inbox to the library ===
# Open the shared inbox in a Outlook client and copy the emails into the library (you will receive better classification results with more examples).
# Tag each example by assigning a term to it.
# As soon as you have provided each example email with a tag, you can initiate the training.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Copy1.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

File:Copy1.PNG

2021-05-10T12:53:17Z

WikiSysop:

File:Col1.PNG

2021-05-10T12:47:08Z

WikiSysop:

File:Emailslib1.PNG

2021-05-10T12:29:11Z

WikiSysop:

File:Terms1.PNG

2021-05-10T12:26:58Z

WikiSysop:

Blog/Automatically process shared inboxes in O365

2021-05-10T12:14:32Z

WikiSysop: Created page with "{{BlogHeader |Titel=O365: Automatically process shared inboxes |News image=File:EasyTaggingText.png |Publication date=2021/05/10 |Published=0 |Keywords=sharepoint, office 365,..."

{{BlogHeader
|Titel=O365: Automatically process shared inboxes
|News image=File:EasyTaggingText.png
|Publication date=2021/05/10
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=This App scans shared inboxes for new emails and forwards them to the appropriate recipient for further processing ⇒reade more!
|Description=The new "Email Dispatcher"-feature of the Easy Tagging App learns to assign emails in shared inboxes to classes and automatically forwards them to specific email addresses. This reduces the time needed to monitor and process shared mailboxes, like support@yourcompany.com, or inquiries@yourdepartment.com.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Managing shared inboxes, like support@yourcompany.com, or inquiries@yourdepartment.com, can be errorprone and time consuming: a group of persons are scanning incoming emails from the inbox, and forwarding them to their email inbox before they reply to the customer, colleague, or other external stakeholder. This approach requires that the persons regularily go through all emails in the shared inbox, read and understand if they should reply to an specific email.
</p>
<p>
You can improve this process if you teach the Easy Tagging App to assign emails to a set of classes, like: job applications, inquiries, issues, invocies etc. In a second step, the App scans a shared inbox periodically for new emails, classifies them and forwards them to the recipient who is assigned to a class. This allows you to automate the process and each email is directed to a responsible person in a timely manner.
</p>
<p>
The following steps assume that you have Sharepoint Online/Office 365 and a shared inbox that contains a couple of emails. Further you should be able to assign each email to a specific set of classes, like invoices, job applications etc.</p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=1G9apnEyH9Q
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Main Page

2021-05-06T13:59:28Z

WikiSysop:

<div id="hauptseite"><div class="row"><div class="col-xs-12" style="padding-left: 0px !important; padding-right: 0px !important; padding-bottom: 0px;"><html>
<div id="slideshow" class="hideXS" width="100%" style="display: none; text-align: left;">
<div id="container" class="cf" style="display: block; min-height: 268px;">
<div class="mainslider" id="main" role="main" style="width:100%; margin: 0px; display: none;">
<section class="slider">
<div class="flexslider">
<ul class="slides" style="margin:0px;padding:0px;">
<li class="" style="min-height: 268px; background-image: url('/mediawiki_en/images/1/11/Finden_statt_suchen_frontpage.jpg'); background-repeat: no-repeat; background-position: right top; background-size: auto; background-clip: content-box;">
<div class="slidercontent" style="text-decoration-line: inherit;">
<span class="slidertext" style="text-align: left; background-color:rgba(255,255,255,0.7); color:#545050; text-decoration-line: inherit;">
DIQA's products and know-How are helping your Sharepoint-users to find documents faster and to reduce tagging effort.</span>
</html>{{Button|color=#A0B844|margin=0em|text-align=left|page=Solutions/Stop_searching_start_finding|text=more...}}<html>
</div>
</li>
<li style="min-height: 268px; background-image: url('/mediawiki_en/images/0/07/EasyTaggingMainPage.png'); background-repeat: no-repeat; background-position: right top; background-size: auto; background-clip: content-box;">
<div class="slidercontent">
<span class="slidertext" style="text-align: left; background-color:rgba(255,255,255,0.7); color:#545050;">
Easy Tagging App for Sharepoint greatly reduces the time to provide large numbers of documents with consistent tags.
</span>
</html>{{Button|color=#A0B844|margin=0em|text-align=left|page=Easy_Tagging_for_SharePoint_online|text=more...}}<html>
</div>
</li>
<li style="min-height: 268px; background-image: url('/mediawiki/resources/assets/diqa/devices-banner.png'); background-repeat: no-repeat; background-position: right top; background-size: auto; background-clip: content-box;">
<div class="slidercontent">
<span class="slidertext" style="text-align: left; background-color:rgba(255,255,255,0.7); color:#545050;">
DIQA is Microsoft certified, we develop your modern Apps/Add-ins for SharePoint onpremise or online.</span>
</html>{{Button|color=#A0B844|margin=0em|text-align=left|page=Services|text=more}}<html>
</div>
</li>
</ul>
</div>
</section>
</div>
</div>
</div>
</html></div></div><article>

<div style="background: #a0b84412;">
<div class="row">
<div class="col-xs-12" style="text-align: center; margin-bottom: 10px; margin-top: 10px;">
<h1 style="font-size: 25px; line-height: 180%; letter-spacing: 0.0em; color: #545050;">Welcome at DIQA – the experts from Germany for intelligent SharePoint Apps and Machine Learning with Microsoft- and Open Source-technologies.</h1>
</div>
</div>
</div>

<div style="background: #f6f8ec; margin-bottom: 10px;">
<div style="text-align: center;">
<h2 style="">Offers:</h2>
</div>
<div class="row row-eq-height">
<div class="col-md-4" style="text-align: center; background-color: rgb(160,186,68); border: 10px solid #f6f8ec;">
<div style=" margin: 0 auto;"><h3>TreeRefiner Webpart:</h3></div>
<div style=" min-height: 180px; margin: 0 10px 10px; background-image: url('/mediawiki_en/images/7/71/Treerefiner_frontpage.jpg'); background-repeat: no-repeat; background-size: cover;">
{{ParentLinksToPage|TreeRefiner Webpart|title=Video and Download}}
</div>
<div style="margin: 0 10px 10px;"><p>The TreeRefiner Webpart for SharePoint online/onpremise greatly improves Sharepoint search centers: this search refiner displays the '''term hierarchy in a tree'''.<br>Your benefit: easier navigation in filter terms for metadata columns.         </p></div>
<div class="showSM" style="margin: 0 auto;">{{Button|fontsize=medium|color=#FF4242|page=Semantic Search Webparts|text=Video und Download}}
</div>
</div>
<div class="col-md-4" style="text-align: center; background-color: rgb(160,186,68); border: 10px solid #f6f8ec;">
<div style=" margin: 0 auto;"><h3>Easy Tagging App:</h3></div>
<div style=" min-height: 180px; margin: 0 10px 10px; background-image: url('/mediawiki_en/images/e/ea/Automatic_Tagging_with_Easy_Tagging_App-frontpage.jpg'); background-repeat: no-repeat; background-size: cover;">
{{ParentLinksToPage|Easy_Tagging_for_SharePoint_online|title=Easy Tagging App}}
</div>
<div style="margin: 0 10px 10px;"><p>The Easy Tagging App for Sharepoint online '''analyses and forwards emails''' in shared mailboxes and automatically '''provides document libraries with searchable tags'''.<br>Your benefit: save resources to manage shared inboxes and to improve document findability.</p></div>
<div class="showSM" style="margin: 0 auto;">{{Button|fontsize=medium|color=#FF4242|page=Easy_Tagging_for_SharePoint_online|text=Evaluate now}}
</div>
</div>
<div class="col-md-4" style="text-align: center; background-color: rgb(160,186,68); border: 10px solid #f6f8ec;">
<div style=" margin: 0 auto;"><h3>Professional Services:</h3></div>

<div style="margin: 0 10px 10px; text-align: left;"><p>DIQA provides you with services in the fields of <b>Sharepoint, Machine Learning, Semantic Technologies and MediaWiki</b>:
*[[Services|Sharepoint Apps/Add-ins and webparts development]]
*: Development of custom made Apps, Add-ins, and webparts for SharePoint onprem/online.
*[[Services|Machine learning for text analysis]]
*: Provision of methods to analyse vast document sets: entitiy recognition, document clusters, classification
*[[Services|MediaWiki extension development for commercial use]]
*: Installation, testing and operation of (Semantic) MediaWiki, customizing MediaWiki extensions.
*[[Services|Semantic Web technologies]]
*: Consultancy in semantic technologies and ontology modeling.
</p></div>
<div class="showSM" style="margin: 0 auto;">{{Button|fontsize=medium|color=#FF4242|page=Services|text=All services}}
</div>
</div>
</div>
<div class="row row-eq-height hideSM">
<div class="col-md-4" style="text-align: center; background-color: rgb(160,186,68); border: 10px solid #f6f8ec; border-top-width: 0px;">{{ParentLinksToPage|TreeRefiner Webpart|title=Video and Download}}<div style="margin: 0 auto;">{{Button|fontsize=medium|color=#FF4242|page=TreeRefiner Webpart|text=Video and Download}}
</div>
</div>
<div class="col-md-4" style="text-align: center; background-color: rgb(160,186,68); border: 10px solid #f6f8ec; border-top-width: 0px;">{{ParentLinksToPage|Easy_Tagging_for_SharePoint_online|title=Get it now!}}<div style="margin: 0 auto;">{{Button|fontsize=medium|color=#FF4242|page=Easy_Tagging_for_SharePoint_online|text=Get it now!}}
</div>
</div>
<div class="col-md-4" style="text-align: center; background-color: rgb(160,186,68); border: 10px solid #f6f8ec; border-top-width: 0px;">
<div style="margin: 0 auto;">{{Button|fontsize=medium|color=#FF4242|page=Services|text=All services}}
</div>
</div>
</div>


</div>

<div style="">
<div class="row">
<div class="col-md-12 col-lg-6" style="">
<div class="diqa-container">
<div class="row" style="border-bottom:3px solid #333333; margin-bottom: 10px;">
<div class="col-xs-9" style="padding-top: 30px; "><h2 style="text-decoration: none; margin-bottom: 0px; text-align: left;"><span style="">Webinars</span></h2></div>
<div class="col-xs-3" style="text-align: right; margin-bottom: 0px; margin-top: 60px;"><span style="">[[Webinars|All Webinars]]</span></div>
</div>
<div class="row">
<div class="col-xs-12">
<div>
{{#ask: [[Category:Veranstaltung]][[Published::1]]
|link=none
|sort=Event start
|order=desc
|limit=1
|default=''no webinars planned.''
|format=template
|userparam=condensed
|template=EventZeile
|searchlabel=}}
</div>
</div>
</div>
</div>
</div>
<div class="col-md-12 col-lg-6 " style="text-align: justify;>
<div class="diqa-container">
<div class="row" style="border-bottom:3px solid #333333; margin-bottom: 10px;">
<div class="col-xs-9" style="padding-top: 30px; "><h2 style="text-decoration: none; margin-bottom: 0px; "><span style="">News</span></h2></div>
<div class="col-xs-3" style="text-align: right; margin-bottom: 0px; margin-top: 60px;"><span style="">[[News|All news]]</span></div>
</div>
<div class="row">
<div class="col-xs-12">
<div>
{{#ask: [[News::+]][[Published::1]][[Publication date::+]]
|link=none
|sort=Publication date
|order=desc
|limit=1
|default=''no news.''
|format=template
|userparam=condensed
|template=NewsZeile
|searchlabel=}}
</div>
</div>
</div>
</div>
</div>
</div>
</div>

<div style="background: #a0b84412;">
<div class="row">
<div class="col-xs-12" style="text-align: center; margin-bottom: 10px;">
<h2>Clients:</h2>
<p>Companies from different industries are using our software or services. Some of our clients:</p>
<div class="" style="text-align: center; margin-bottom: 10px; height: 100%; white-space: nowrap; overflow-x: scroll;">
<div style="width:100%;">
<a href="{{localurl:Clients}}" target="_self" title="Kunden" style="">
<img src="{{filepath:Altran.png}}" class="padding "><img src="{{filepath:Bertrand AG.png}}" class="padding "><img src="{{filepath:DHBW.png}}" class="padding "><img src="{{filepath:DILA.png}}" class="padding "><img src="{{filepath:Elsevier.png}}" class="padding "><img src="{{filepath:Fraunhofer Institut.png}}" class="padding "><img src="{{filepath:Gold Fields Mining.png}}" class="padding "><img src="{{filepath:Hamon_Group.png}}" class="padding "><img src="{{filepath:Hoffmann Laroche.png}}" class="padding "><img src="{{filepath:HTC India.png}}" class="padding "><img src="{{filepath:KAGES.png}}" class="padding "><img src="{{filepath:Kanton Zürich.png}}" class="padding "><img src="{{filepath:Knowledge Group.png}}" class="padding "><img src="{{filepath:Liberty Pumps.png}}" class="padding "><img src="{{filepath:Northhighland Company.png}}" class="padding "><img src="{{filepath:Novo Nordisk.png}}" class="padding "><img src="{{filepath:Rabo Bank.png}}" class="padding "><img src="{{filepath:Rosen Group.png}}" class="padding "><img src="{{filepath:Scotia Bank.png}}" class="padding "><img src="{{filepath:Sitema.png}}" class="padding "><img src="{{filepath:Tata Consulting.png}}" class="padding "><img src="{{filepath:Universität Innsbruck.png}}" class="padding "><img src="{{filepath:Universität Wien.png}}" class="padding ">
</a>
</div>
</div>
</div>
</div>
</div>

<div style="">
<div class="row">
<div class="col-xs-12" style="text-align: center; margin-bottom: 10px;">
<h2 style="margin-bottom: 2em;">Are you ready for the next step with us?</h2>
<div class="col-md-4" style="text-align: center; margin-bottom: 10px;" >
<div style="position: relative; display: block; float: left; width: 100%;">
{{ParentLinksToPage|Download/Get_evaluation_copy|title=Download now}}
<div style=" max-height: 100px; display: block; margin: 0 auto;">[[File:Download100x100.png|link=Download/Get_evaluation_copy]]
</div>
<div style=" max-height: 100px; display: block; margin: 0 auto;"><h3>Software Download</h3><p>Get your evaluation copy right now.</p>
</div>
<div style=" max-height: 100px; display: block; margin: 0 auto;">{{Button|color=#FF4242|page=Download/Get_evaluation_copy|text=Download now}}
</div>
</div>
</div>
<div class="col-md-4" style="text-align: center; margin-bottom: 10px;">
<div style="position: relative; display: block; float: left; width: 100%;">
{{ParentLinksToPage|Download/Purchase_license|title=Get licenses}}
<div style=" max-height: 100px; display: block; margin: 0 auto;">[[File:Buy100x100.png|link=Download/Purchase_license]]
</div>
<div style=" max-height: 100px; display: block; margin: 0 auto;"><h3>Get licenses</h3><p>Request your license key for our software products here.</p>
</div>
<div style=" max-height: 100px; display: block; margin: 0 auto;">{{Button|color=#FF4242|page=Download/Purchase_license|text=Get licenses}}
</div>
</div>
</div>
<div class="col-md-4" style="text-align: center; margin-bottom: 10px;">
<div style="position: relative; display: block; float: left; width: 100%;">
{{ParentLinksToPage|Contact|title=Contact DIQA}}
<div style=" max-height: 100px; display: block; margin: 0 auto;">[[File:Contact100x100.png|link=Contact]]
</div>
<div style=" max-height: 100px; display: block; margin: 0 auto;"><h3>Questions?</h3><p>Contact us to discuss your specific requirements.</p>
</div>
<div style=" max-height: 100px; display: block; margin: 0 auto;">{{Button|color=#FF4242|page=Contact|text=Contact DIQA}}
</div>
</div>
</div>
</div>
</div>
</article></div>
{{Metatags
|keywords=Software Development, Microsoft, Sharepoint, machine learning, search center, terminology, terms, term hierarchy, tagging, document management
|description=Welcome at DIQA – the experts from Germany for intelligent SharePoint Apps and Machine Learning with Microsoft- and Open Source-technologies.
|en_link=
}}
[[Category:Page]][[SEO-Description::Welcome at DIQA – the experts from Germany for intelligent SharePoint Apps and Machine Learning with Microsoft- and Open Source-technologies.| ]]

Blog/Refine search results by term trees

2021-05-06T13:32:26Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2021/05/06
|Published=1
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint can be tedious. If you have a hierarchy of terms, like product groups, series and products, then it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This frustrates users who cannot leverage the structural information of the term store. DIQA's TermTree Refiner Webpart overcomes this problem. Learn in this article how to use it and what it can do for your users.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience? <big> Just follow the steps below! </big>
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, give it a name like "products"
# Create a term for each product of your company, take care to create a meaningful hierarchy of products, like product groups.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "products"
# Select "managed metadata" as type
# In the term set settings: select the termset "product" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples ===
# Open the library settings and add the new column "products" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "products" with meaningful values for a couple of documents. Take care to use leaf terms only, i.e. products, not product groups.

<big>Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Create a classic search center and add the TreeRefiner Webpart</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a classic Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Add the TreeRefiner Webpart to the results page ===
# Open the page "results.aspx" in edit mode.
# Add the "TreeRefiner" Webpart into the page.
# Open the Webpart in edit mode.
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page..
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Modify the search schema ===
# Open the Sharepoint admin center for your tenant or the central administration for SP onpremise
# Click on the "Search" section
# In the Search section: click on "Search schema"
# Click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
# Enter the name of the refinable managed property that you have selected as refiner (e.g. “RefinableString00”) into the filter and apply the filter to retrieve it in the list of refinable managed properties for strings.
# The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup window.
# In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”
# Select in the list of crawled properties the property that corresponds to your site column, e.g. "ows_taxid_products". Click on “OK” to save the setting and close the popup window.

<big>NOTE: If you cannot find a crawled property that corresponds to your site column, then you should start a full crawl which INCLUDES your library (see next step)!</big>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Refinablestring_mapping.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Verify the search results</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tree_view-collapsed.png|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T13:28:35Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2021/05/06
|Published=1
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint can be tedious. If you have a hierarchy of terms, like product groups, series and products, then it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This frustrates users who cannot leverage the structural information of the term store. DIQA's TermTree Refiner Webpart overcomes this problem. Learn in this article how to use it and what it can do for your users.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience? <big> Just follow the steps below! </big>
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, give it a name like "products"
# Create a term for each product of your company, take care to create a meaningful hierarchy of products, like product groups.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "products"
# Select "managed metadata" as type
# In the term set settings: select the termset "product" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples ===
# Open the library settings and add the new column "products" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "products" with meaningful values for a couple of documents. Take care to use leaf terms only, i.e. products, not product groups.

<big>Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Create a classic search center and add the TreeRefiner Webpart</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a classic Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Add the TreeRefiner Webpart to the results page ===
# Open the page "results.aspx" in edit mode.
# Add the "TreeRefiner" Webpart into the page.
# Open the Webpart in edit mode.
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page..
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Modify the search schema ===
# Open the Sharepoint admin center for your tenant or the central administration for SP onpremise
# Click on the "Search" section
# In the Search section: click on "Search schema"
# Click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
# Enter the name of the refinable managed property that you have selected as refiner (e.g. “RefinableString00”) into the filter and apply the filter to retrieve it in the list of refinable managed properties for strings.
# The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup window.
# In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”
# Select in the list of crawled properties the property that corresponds to your site column, e.g. "ows_taxid_products". Click on “OK” to save the setting and close the popup window.

<big>NOTE: If you cannot find a crawled property that corresponds to your site column, then you should start a full crawl which INCLUDES your library (see next step)!</big>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Refinablestring_mapping.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Verify the search results</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tree_view-collapsed.png|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T13:22:42Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2021/05/06
|Published=1
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This frustrates users who cannot leverage the structural information of the term store. DIQA's TermTree Refiner Webpart overcomes this problem. Learn in this article how to use it and what it can do for your users.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience? <big> Just follow the steps below! </big>
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, give it a name like "products"
# Create a term for each product of your company, take care to create a meaningful hierarchy of products, like product groups.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "products"
# Select "managed metadata" as type
# In the term set settings: select the termset "product" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples ===
# Open the library settings and add the new column "products" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "products" with meaningful values for a couple of documents. Take care to use leaf terms only, i.e. products, not product groups.

<big>Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Create a classic search center and add the TreeRefiner Webpart</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a classic Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Add the TreeRefiner Webpart to the results page ===
# Open the page "results.aspx" in edit mode.
# Add the "TreeRefiner" Webpart into the page.
# Open the Webpart in edit mode.
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page..
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Modify the search schema ===
# Open the Sharepoint admin center for your tenant or the central administration for SP onpremise
# Click on the "Search" section
# In the Search section: click on "Search schema"
# Click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
# Enter the name of the refinable managed property that you have selected as refiner (e.g. “RefinableString00”) into the filter and apply the filter to retrieve it in the list of refinable managed properties for strings.
# The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup window.
# In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”
# Select in the list of crawled properties the property that corresponds to your site column, e.g. "ows_taxid_products". Click on “OK” to save the setting and close the popup window.

<big>NOTE: If you cannot find a crawled property that corresponds to your site column, then you should start a full crawl which INCLUDES your library (see next step)!</big>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Refinablestring_mapping.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Verify the search results</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tree_view-collapsed.png|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T12:24:48Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2021/05/06
|Published=1
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience? <big> Just follow the steps below! </big>
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, give it a name like "products"
# Create a term for each product of your company, take care to create a meaningful hierarchy of products, like product groups.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "products"
# Select "managed metadata" as type
# In the term set settings: select the termset "product" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples ===
# Open the library settings and add the new column "products" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "products" with meaningful values for a couple of documents. Take care to use leaf terms only, i.e. products, not product groups.

<big>Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Create a classic search center and add the TreeRefiner Webpart</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a classic Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Add the TreeRefiner Webpart to the results page ===
# Open the page "results.aspx" in edit mode.
# Add the "TreeRefiner" Webpart into the page.
# Open the Webpart in edit mode.
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page..
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Modify the search schema ===
# Open the Sharepoint admin center for your tenant or the central administration for SP onpremise
# Click on the "Search" section
# In the Search section: click on "Search schema"
# Click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
# Enter the name of the refinable managed property that you have selected as refiner (e.g. “RefinableString00”) into the filter and apply the filter to retrieve it in the list of refinable managed properties for strings.
# The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup window.
# In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”
# Select in the list of crawled properties the property that corresponds to your site column, e.g. "ows_taxid_products". Click on “OK” to save the setting and close the popup window.

<big>NOTE: If you cannot find a crawled property that corresponds to your site column, then you should start a full crawl which INCLUDES your library (see next step)!</big>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Refinablestring_mapping.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Verify the search results</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tree_view-collapsed.png|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T12:23:51Z

WikiSysop:

Blog/Refine search results by term trees

2021-05-06T12:21:23Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience?
#Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]
#Create a classic search center in Sharepoint and add the TreeRefiner Webpart to it.
#Make sure that your document library uses a site column of type "Managed Property" which uses a termset in the termstore.
#Launch a full crawl.
#Modify your search schema and create a mapping to a refinable managed property, like: RefinableString00
##Open the search schema and click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
##Select the refinable managed property that you want to use as refiner (e.g. “RefinableString00”) and open it in Edit-mode.
##The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup
window. In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”. Select in the list of crawled properties the property that corresponds to your site column. Click on “OK” to save the setting and close the popup window.
## NOTE: If you cannot find a crawled property that corresponds to your site column, then your full crawl has not terminated yet.
#Return to the search center and complete the configuration of the TermTree Refiner Webpart
#Enter a search term and verify that the term tree is displayed in the webpart,
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, give it a name like "products"
# Create a term for each product of your company, take care to create a meaningful hierarchy of products, like product groups.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "products"
# Select "managed metadata" as type
# In the term set settings: select the termset "product" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples ===
# Open the library settings and add the new column "products" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "products" with meaningful values for a couple of documents. Take care to use leaf terms only, i.e. products, not product groups.

<big>Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Create a classic search center and add the TreeRefiner Webpart</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a classic Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Add the TreeRefiner Webpart to the results page ===
# Open the page "results.aspx" in edit mode.
# Add the "TreeRefiner" Webpart into the page.
# Open the Webpart in edit mode.
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page..
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Modify the search schema ===
# Open the Sharepoint admin center for your tenant or the central administration for SP onpremise
# Click on the "Search" section
# In the Search section: click on "Search schema"
# Click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
# Enter the name of the refinable managed property that you have selected as refiner (e.g. “RefinableString00”) into the filter and apply the filter to retrieve it in the list of refinable managed properties for strings.
# The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup window.
# In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”
# Select in the list of crawled properties the property that corresponds to your site column, e.g. "ows_taxid_products". Click on “OK” to save the setting and close the popup window.

<big>NOTE: If you cannot find a crawled property that corresponds to your site column, then you should start a full crawl which INCLUDES your library (see next step)!</big>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Refinablestring_mapping.PNG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Verify the search results</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

File:Refinablestring mapping.PNG

2021-05-06T12:07:38Z

WikiSysop:

File:Edit refiner.PNG

2021-05-06T11:55:59Z

WikiSysop:

Blog/Refine search results by term trees

2021-05-06T11:51:54Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience?
#Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]
#Create a classic search center in Sharepoint and add the TreeRefiner Webpart to it.
#Make sure that your document library uses a site column of type "Managed Property" which uses a termset in the termstore.
#Launch a full crawl.
#Modify your search schema and create a mapping to a refinable managed property, like: RefinableString00
##Open the search schema and click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
##Select the refinable managed property that you want to use as refiner (e.g. “RefinableString00”) and open it in Edit-mode.
##The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup
window. In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”. Select in the list of crawled properties the property that corresponds to your site column. Click on “OK” to save the setting and close the popup window.
## NOTE: If you cannot find a crawled property that corresponds to your site column, then your full crawl has not terminated yet.
#Return to the search center and complete the configuration of the TermTree Refiner Webpart
#Enter a search term and verify that the term tree is displayed in the webpart,
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, give it a name like "products"
# Create a term for each product of your company, take care to create a meaningful hierarchy of products, like product groups.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "products"
# Select "managed metadata" as type
# In the term set settings: select the termset "product" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples ===
# Open the library settings and add the new column "products" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "products" with meaningful values for a couple of documents. Take care to use leaf terms only, i.e. products, not product groups.

<big>Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T11:19:04Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience?
#Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]
#Create a classic search center in Sharepoint and add the TreeRefiner Webpart to it.
#Make sure that your document library uses a site column of type "Managed Property" which uses a termset in the termstore.
#Launch a full crawl.
#Modify your search schema and create a mapping to a refinable managed property, like: RefinableString00
##Open the search schema and click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
##Select the refinable managed property that you want to use as refiner (e.g. “RefinableString00”) and open it in Edit-mode.
##The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup
window. In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”. Select in the list of crawled properties the property that corresponds to your site column. Click on “OK” to save the setting and close the popup window.
## NOTE: If you cannot find a crawled property that corresponds to your site column, then your full crawl has not terminated yet.
#Return to the search center and complete the configuration of the TermTree Refiner Webpart
#Enter a search term and verify that the term tree is displayed in the webpart,
</p>
== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T11:17:46Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
What do you need to do to achieve this improved search experience?
#Download/install the TreeRefiner Webpart either for Sharepoint 2016, 2019 on premise or Sharepoint online: [[TreeRefiner_Webpart|TreeRefiner Webpart]]
#Create a classic search center in Sharepoint and add the TreeRefiner Webpart to it.
#Make sure that your document library uses a site column of type "Managed Property" which uses a termset in the termstore.
#Launch a full crawl.
#Modify your search schema and create a mapping to a refinable managed property, like: RefinableString00
##Open the search schema and click on the hyperlink “Managed Properties” to retrieve the list of managed properties.
##Select the refinable managed property that you want to use as refiner (e.g. “RefinableString00”) and open it in Edit-mode.
##The edit mode of the RefinableString-property contains the section “Mappings to crawled properties”. Click on the button named “Add a mapping” to open a popup
window. In the popup window, enter the string “ows_taxid” and klick on “Find” to retrieve the list of crawled properties of type “Managed Metadata”. Select in the list of crawled properties the property that corresponds to your site column. Click on “OK” to save the setting and close the popup window.
## NOTE: If you cannot find a crawled property that corresponds to your site column, then your full crawl has not terminated yet.
#Return to the search center and complete the configuration of the TermTree Refiner Webpart
#Enter a search term and verify that the term tree is displayed in the webpart,

== See the TreeRefiner Webpart in this video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Get the TermTree Refiner Webpart: [[TreeRefiner_Webpart|TreeRefiner Webpart]]

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=jvKEF-u5r84}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[TreeRefiner_Webpart|TreeRefiner Webpart]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T09:28:43Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The standard refiner hides important information like the position of a search hit in the term tree. Additionally you cannot filter for parent terms, like product groups.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''The TermTree Refiner Webpart shows the terms in their tree-context. Users can easily drill-up or drill-down in the tree to broaden or narrow the search.''
</div>
</div> 

<p>
The following steps assume that you have Sharepoint Online/Office 365 and a library that contains at least dozens of documents or scanned documents (pdf or image formats). If you are familiar with certain configuration aspects of Sharepoint then you will need 30 minutes to go them through in your tenant. If you require assistance then we are happy to help!</p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84&t=97s
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-06T08:50:04Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you have a hierarchy of terms, like product groups, series and products, then you can easily refine search results for leaf terms. But it is impossible to refine for terms that sit higher in the term tree, e.g. product groups or series. This is because the standard refinement webpart shows leaf terms, only. This frustrates your users who cannot leverage the structural information of the term store.
</p>
<p>
You can provide your users with a better search experience if you use DIQA's TermTree Refiner. This Webpart extends the standard refiner webpart and visualises the terms in the hierarchical context of the term tree. Users can select terms in the hierarchy to drill down or drill up in the search results. This webpart makes use of managed metadata. This refinement webpart has these advantages over standard SharePoint-Search:
*The terms contained in the search results are presented in their tree-context
*Users can easily drill-up or drill-down in the tree to broaden or narrow the search
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''Entering the search term "order" returns a lot of irrelevant documents (e.g. a CV) and even misses some sales order documents.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''If you provide search refiners, then the users will be able to precicely filter for all "sales order" documents, for instance.''
</div>
</div> 

<p>
The following steps assume that you have Sharepoint Online/Office 365 and a library that contains at least dozens of documents or scanned documents (pdf or image formats). If you are familiar with certain configuration aspects of Sharepoint then you will need 30 minutes to go them through in your tenant. If you require assistance then we are happy to help!</p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=jvKEF-u5r84&t=97s
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Blog/Refine search results by term trees

2021-05-05T13:10:49Z

WikiSysop:

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
</p>
<p>
You can provide your users with a better search experience if you use search refiners. Users can further refine their search result by clicking on the refiner values, e.g. to retrieve "sales orders" or "invoices", only. Before you are able to create meaningful search refiners, you have to arrange for a couple of pre-requisites which include tagging documents with tags. This guide shows you how to automatically tag documents with their type (e.g. invoice, sales order, cv, inquiry) and how to provide search refiners that contain these document types.
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/aa/Treerefiner_standardrefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''Entering the search term "order" returns a lot of irrelevant documents (e.g. a CV) and even misses some sales order documents.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/0/06/Treerefiner.PNG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/0/06/Treerefiner.PNG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/0/06/Treerefiner.PNG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''If you provide search refiners, then the users will be able to precicely filter for all "sales order" documents, for instance.''
</div>
</div> 

<p>
The following steps assume that you have Sharepoint Online/Office 365 and a library that contains at least dozens of documents or scanned documents (pdf or image formats). If you are familiar with certain configuration aspects of Sharepoint then you will need 30 minutes to go them through in your tenant. If you require assistance then we are happy to help!</p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=hMaEIa2DMNs
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

File:Treerefiner.PNG

2021-05-05T13:04:51Z

WikiSysop:

File:Treerefiner standardrefiner.PNG

2021-05-05T13:04:16Z

WikiSysop:

Blog/Refine search results by term trees

2021-05-05T11:18:54Z

WikiSysop: Created page with "{{BlogHeader |Titel=Sharepoint: Improve the search experience with the TermTree Refiner |News image=File:EasyTaggingText.png |Publication date=2020/09/01 |Published=0 |Keyword..."

{{BlogHeader
|Titel=Sharepoint: Improve the search experience with the TermTree Refiner
|News image=File:EasyTaggingText.png
|Publication date=2020/09/01
|Published=0
|Keywords=sharepoint, office 365, o365
|SEO-Description=Automatic document tagging boosts your document findability? ⇒reade more!
|Description=Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
|en_link=
|de_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">
<p>
Finding documents in Sharepoint online/Office 365 can be tedious. If you want to restrict your search to certain document types (like: reports, inquiries, CVs, sales orders, invoices) you either end up with too many irrelevant search hits or relevant documents don't show up because they don't include the search term. If you rely on Sharepoint's fulltext search capabilities only, then your users will be frustrated and spend too much time to find the right documents.
</p>
<p>
You can provide your users with a better search experience if you use search refiners. Users can further refine their search result by clicking on the refiner values, e.g. to retrieve "sales orders" or "invoices", only. Before you are able to create meaningful search refiners, you have to arrange for a couple of pre-requisites which include tagging documents with tags. This guide shows you how to automatically tag documents with their type (e.g. invoice, sales order, cv, inquiry) and how to provide search refiners that contain these document types.
</p>
<div class="row">
<div class="col-lg-6">
== Frustrating search experience without meaningful refiners: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/a/a2/Fulltextsearch3.JPG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/a/a2/Fulltextsearch3.JPG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/a/a2/Fulltextsearch3.JPG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''Entering the search term "order" returns a lot of irrelevant documents (e.g. a CV) and even misses some sales order documents.''
</div>
<div class="col-lg-6">
== Better: filter documents by type, language, etc: ==
<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/9/9f/Capture-refinement3.JPG" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/9/9f/Capture-refinement3.JPG" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/9/9f/Capture-refinement3.JPG 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
<br>
''If you provide search refiners, then the users will be able to precicely filter for all "sales order" documents, for instance.''
</div>
</div> 

<p>
The following steps assume that you have Sharepoint Online/Office 365 and a library that contains at least dozens of documents or scanned documents (pdf or image formats). If you are familiar with certain configuration aspects of Sharepoint then you will need 30 minutes to go them through in your tenant. If you require assistance then we are happy to help!</p>

== Watch the steps in the video: ==
<div>
<p>
{{#widget:YouTube
|id=hMaEIa2DMNs
}}
</p>
</div>

<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none;">
<h2>Step 1: Prepare your library</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create a termset with your document types ===
# Open the termstore manager (from the site settings)
# Create a new termset, named "document types"
# Create a term for each document type that you keep in your document library, e.g. inquiry, invoice, sales order, resume
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_termset.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Create a column for your document library that contins the document types ===
# Open the document library
# Open the library advanced settings
# Click on "create column"
# Enter the name of the new library column, e.g. "document type"
# Select "managed metadata" as type
# In the term set settings: select the termset "document type" (from the step above)
# Click on "Save" to close the form
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_column.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Manually tag a couple of documents as examples (not all!) ===
# Open the library settings and add the new column "Document types" to the default view of the library
# Open the "Quick Edit" view of the library.
# Populate the field "Document types" with meaningful values for a couple of documents per document type. It is not necessary to provide each document with a tag, but the more examples you provide, the better the results will be. You should achieve a coverage of 20% of all documents per document type (and at least 10 examples per document type).
<big>You have now prepared everything required to teach the "Easy Tagging App" about your way to tag. You can now carry on and install the Easy Tagging App and train the "Learn Tags"-predictor.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tagexample.png|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 2: Automatically tag all your documents</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Install the Easy Tagging App from the App Source (free evaluation!) ===
# Open the site settings and click on "Add an App"
# Click on "Sharepoint Store"
# In the Sharepoint Store: enter "diqa" as search term
# Click on the "Easy Tagging" card to initiate the installation.
<br><br>
:Direct link to the Microsoft App Store:
<html><a href="https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview" target="_self" title="Go to Microsoft AppSource"> ▶ Got to Microsoft AppSource</a></html>

</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Appstore.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Launch the app and grant it the requested permissions ===
# Open the site contents again where you should find the newly installed Easy Tagging App
# Click on the App and grant it the requested permissions.
# The configuration page of the app opens in a new tab.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Launch_the_app_modern.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Connect the Easy Tagging App with the IDAS service (1/2) ===
# In the configuration page of the Easy Tagging App: click on the "Predictors & Taggers" tab
# Click on the link "Click here to connect to IDAS"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Apptab.png|center|middle]]</div>
</div>

<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. Connect the Easy Tagging App with the IDAS service (2/2) ===
# In the connection dialog: select the "IDAS Evaluation Service" tab
# Click on "I accept the terms of use" tick box
# If the service status says "IDAS evaluation service is available", then click on the "connect" button. If the status says something different: click on "refresh status".
# The dialog closes and you can setup a predictor.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Connect2.png|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 5. Launch the "Learning Wizard" in your library ===
# After you have created a connection to the IDAS Evaluation service you can launch the "Learning Wizard" which will guide you through the process to learn from your examples and to tag your documents.
# Return to your library and open the "Library Settings" ribbon.
# Click on the "Learning Wizard" icon which launches the wizard in a dialog.
# Go through the three steps:
## Click on "Click to start the wizard"
## Step 1: select the language that is used in most of the documents of the library. If you documents in other languages: just select english.
## Step 1: in the field "Learn to predict tags from this managed metadata column": select the "document types" column that you created in the earlier steps
## Step 2: your library is analysed for sufficient examples. If you don't have enough examples: please add further examples before you continue with the wizard.
## Step 3: select the column which will receive the document type tags: just keep the selection.
## Step 3: click on the link "Start Learning and Tagging".
# The learning and tagging processes are running in the background.
# You can inspect the progress in the library ribbon "Predictors + Taggers"
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Start_learning_wizard.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 6. Important: re-index your document library ===
# Opent the settings of your library
# Click on "re-index document library"
# Click on "Ok" to close the form
<big>Now all your documents in the library have been provided with tags, and the search index is being updated in the background. You can now carry on and setup the search page that uses these tags.</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Library_settings.JPG|center|middle]]</div>
</div>
</p>
</div>
<h2>Step 3: Create a search center that includes the search refiners</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 1. Create an Enterprise Search Center ===
# Open the contents of your Sharepoint site and click on "subsites".
# Create a new sub site by clicking on the "New" action link.
# A form opens where you specify the new sub site.
# In the template field: select "Enterprise/Basic Search Center".
# Click on "Create" to create the new seach center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Create_search_center.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 2. Adjust the search schema: map the crawled property to a refinable managed property ===
# Open the Sharepoint admin center for your tenant.
# Click on the "Search" section
# In the Search section: click on "Search schema"
# In the "Search schema" settings: activate the tab "Crawled properties"
# Search for all crawled properties that start with the string "ows_"
# Select the crawled property that relates to your "document type"-managed property, e.g. "ows_Document_x0020_type"
# Create a mapping to the managed property "RefinableString01" (or 00, or any other number).
# Save the settings.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchschema.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 3. Add the new refiner to the search page ===
# Open the search center
# Open the search results page (named "results.aspx")
# Click on "Edit page"
# In the page edit view: open the property settings of the Refinement webpart
# Click on the button "Choose refiners"
# In the "refinement configuration" dialog: add the refinable managed propery
(from the search schema step), like: RefinableString00 (or 01 etc).
# You should see sample values that contain you document types.
# Click on "Ok" to add RefinableString00 to the refiner
# Save the modified properties of the webpart by clicking on "OK"
# Store the modified page.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Search_refiner.JPG|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== 4. verify the search results ===
# Open the search center
# Enter "*" as search string and submit the query
# Inspect the refiner values: they should include your document types
# Click on a refiner value, like "invoice", in order to restrict your search results to contain only invoices and bills.

<big>If the new refiner does not contain values then you have to wait until the Sharepoint online search engine has completed re-indexing your library. If still no values show up then you have to go back to your library settings and click on "re-index library".</big>
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Searchresults.JPG|center|middle]]</div>
</div>
</p></div></div>
==What's next?==
* Add refiners for the document language like: english, french, german, spanisch
** The Easy Tagging App has a built-in predictor that detects the language that is used in documents. You can simply use that predictor in a tagger to tag all your documents with the language. Similar to the steps in section 3 you would simply create another refiner that allows users to restrict their search results to certain languages.
* Add refiners for important words:
** The Easy Tagging App is able to identify important words from documents and store them in the termstore as a new termset. If you let the tagger tag your documents with them, then your users can use them to filter their search results.

==Questions?==
{{Emailformular
|Text=Hi DIQA! Can you give us assistance?
|Placeholder=
}}
</div></div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2">
{{Linkbox
|color=#a0b844
|heading=Watch it here:
|links={{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
}}
{{Linkbox
|color=#a0b844
|heading=related products
|links=
* [[Easy_Tagging_for_SharePoint_online|Easy Tagging App]]
}}
{{Linkbox
|color=#a0b844
|heading=more articles
|links=
* [[Blog|DIQA Blog]]
}}

</div>
</div>

Easy Tagging for SharePoint online

2021-05-03T13:26:59Z

WikiSysop:

{{Seite
|Titel=Easy Tagging App for Sharepoint online
|Kategorie=Product
|Image=EasyTaggingBannern.png
|Verlauf=
|Pfad=[[Main Page]] > Products > [[Easy_Tagging_for_SharePoint_online|Easy Tagging for SharePoint online]]
|Keywords=SharePoint, o365, office 365, auto tagging
|SEO-Description=The Easy Tagging App for SharePoint online greatly reduces the time to automatically provide document libraries with searchable metadata and to automatically process shared mailboxes.
|en_link=
}}
<div class="row">
<div class="col-xs-12 col-md-8 col-lg-9 col-xl-10">

<div class="row">
<div class="col-lg-6">
== This extension for SharePoint online analyses and forwards emails in shared mailboxes, e.g. customer requests ==
Your customers submit requests to a central Office 365 mailbox, like inquiries@yourcompany.com, where they are picked up manually. The Easy Tagging App fully automates this process: after a short teach-in phase, it analyses the incoming emails and decides to which email address to forward them. This saves your team a lot of time and reduces the processing time of incoming emails.

== Automatically provides document libraries with searchable tags.==
Tags are a pre-requisite to automatically route documents to their destination library, and to find them quicker. The App supports you in finding meaningfull tags for documents that are stored in SharePoint. It connects to an online service (IDAS Service, provided by DIQA) which analyses the documents for aspects like document language, important tags, or user created tags.
</div>
<div class="col-lg-6">

<html>
<div class="center"><div class="floatnone"><a href="/mediawiki_en/images/6/6a/Tag_a_library.png" class="image"><img alt="Tagcloud" src="/mediawiki_en/images/6/6a/Tag_a_library.png" width="100%" height="100%" style="vertical-align: middle" srcset="/mediawiki_en/images/6/6a/Tag_a_library.png 1x" data-file-width="" data-file-height=""></a></div></div>
</html>
</div>
</div>
{{Easy_Tagging_for_SharePoint_online/Kostenlose_Testversion}}
== Benefits from using the Easy Tagging App: ==
The following table lists all advantages from using the Easy Tagging App, compared to the manual extraction of tags and tagging of documents:
{| class="table_zebra_grid" align="center"
|-
|+
! scope="col" width="40%"|
! scope="col" width="30%"| SharePoint without Easy Tagging App
! scope="col" width="30%"| SharePoint with Easy Tagging App
|-
| '''Learn to classify emails, and automatically forward emails in a shared mailbox'''
| valign="bottom"|[[File:X.png|20px|Not available|link=]] <small></small>
| valign="bottom"|[[File:Ok.png|24px|Available with Easy Tagging|link=]] <small>The Easy Tagging App automatically learns to classify emails and forwards them to specific email addresses.</small>
|-
| '''Detect the language which is used in documents and find documents by their language'''
| valign="bottom"|[[File:X.png|20px|Not available|link=]] <small></small>
| valign="bottom"|[[File:Ok.png|24px|Available with Easy Tagging|link=]] <small>The Easy Tagging App automatically detects the language used in documents and tags the documents accordingly. Users can now refine documents in search results by their language.</small>
|-
| '''Automatically extract important words from documents and find documents by these words.'''
| valign="bottom"|[[File:X.png|20px|Not available|link=]] <small></small>
| valign="bottom"|[[File:Ok.png|24px|Available with Easy Tagging|link=]] <small>The Easy Tagging App automatically extracts important words in documents that help to better filter for particular documents in the search results.</small>
|-
| '''Learn how your users tag documents and apply that to new documents (or libraries).'''
| valign="bottom"|[[File:X.png|20px|Not available|link=]] <small></small>
| valign="bottom"|[[File:Ok.png|24px|Available with Easy Tagging|link=]] <small>The Easy Tagging App learns how to tag documents by examples. After it has acquired that knowledge you can direct it to tag new documents and entire libraries.</small>
|-
| '''Create a browsable knowledge base for your products'''
| valign="bottom"|[[File:X.png|20px|Not available|link=]] <small></small>
| valign="bottom"|[[File:Ok.png|24px|Available with Easy Tagging|link=]] <small>The Easy Tagging App tags documents with product names and synonyms automatically, that can be used to filter search results.</small>
|-
| '''Tag documents automatically per schedule.'''
| valign="bottom"|[[File:X.png|20px|Not available|link=]] <small></small>
| valign="bottom"|[[File:Ok.png|24px|Available with Easy Tagging|link=]] <small>You can create taggers in the Easy Tagging App which tag documents contained in libraries per a schedule, e.g. hourly, nightly, or a concrete date.</small>
|}
<div id="accordionwrapper" width="100%" style="">
<div class="spinner" style="display: block; min-height: 300px;">
<div class="bounce1"></div>
<div class="bounce2"></div>
<div class="bounce3"></div>
</div>
<div id="accordion" width="100%" style="display: none; min-height: 300px;">
<h2>Watch the video</h2>
<div>
<p>
{{#widget:YouTube
|id=8_ss16-t2B0
}}
</p>
</div>
<h2>News about the product</h2> 
<div>
<p>
{{NewsItem
|Titel=New feature: Automatically create a browsable knowledge base of your products
|News image=File:EasyTaggingText.png
|Publication date=2021/05/01
|Published=1
|print=print
|Description=The new "Find terms"-predictor tags all documents with occurences of terms and synonyms in a termset. Just create a termset that includes your company's product names, groups and their synonyms and let the Easy Tagging App automatically tag your libraries of marketing materials, product manuals etc. Your users will be able to browse for product documents in the search center.
}}
Watch it here in this video:
{{#widget:YouTube
|width=50%
|height=50%
|id=mX0lC5hcWA8}}
</p>
<p>
{{NewsItem
|Titel=New feature: Classify and forward emails with the "Email dispatcher"
|News image=File:EasyTaggingText.png
|Publication date=2021/04/05
|Published=1
|print=print
|Description=The new "Email Dispatcher" learns how to classify emails and automatically forwards emails in a shared mailbox to specific email addresses. This reduces the time needed to monitor and process shared mailboxes, like support@yourcompany.com, or inquiries@yourdepartment.com.
}}
Watch it here in this video:
{{#widget:YouTube
|width=50%
|height=50%
|id=1G9apnEyH9Q}}
</p><p>
{{NewsItem
|Titel=New feature: Learning Wizard
|News image=File:EasyTaggingText.png
|Publication date=2020/11/04
|Published=1
|print=print
|Description=The "Learning Wizard" makes learning from your example documents really easy: it guides you through three steps and at the end your documents are automatically tagged!
}}
Watch it here in this video:
{{#widget:YouTube
|width=50%
|height=50%
|id=hMaEIa2DMNs}}

</p>
<p>
{{NewsItem
|Titel=New product: Easy Tagging App for Sharepoint online
|News image=File:EasyTaggingText.png
|Publication date=2020/06/23
|Published=1
|print=print
|Description=DIQA has launched the new product "Easy Tagging App for SharePoint online" to help companies to make their Sharepoint documents better accessible: reduced effort to provide documents with meaningful tags.
}}
</p>
</div>
<h2>Features + installation</h2>
<div>
<p>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify; ">
=== Automatically tags entire libraries ===
Launch the automatic tagging process for all documents in a library (or a subset) in the "Tag documents"-dialog. Inspect the tagging progress and check the tagging report after the process has completed.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify; >[[File:Tag_a_library.PNG|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Assisted manual tagging ===
Open the "Tag document"-dialog to provide individual documents with tags and review the recommended tags for each managed metadata column. Each tag recommendation comes with a confidence level or explanation.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Tagdocument expl.png|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Manage taggers for libraries ===
You can assign taggers to individual libraries, which automatically tag documents contained in that library. Taggers run according to a schedule (e.g. each full hour, day, week etc) or can be launched manually. You specify for each tagger where it retrieves tagging recommendations from, i.e. built-in predictors to detected the document language, to extract important terms and to learn from user generated tags.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Managetaggers.png|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Use tags in refinement filters in search pages ===
You can easily extend the search refiners on your search pages in order to use the newly created tags to refine your search results, e.g. to find documents which use a particular language, or use particular important terms. You can also refine for tags that have been generated as if a user would have created them. This helps users to be able to find documents much quicker.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Searchrefiner.png|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== The Learning Wizard ===
The Learning Wizard combines all features into one easy to understand tool: learn from a library column and automatically tag documents. Watch it here in this video:
</div>
<div class="col-md-6 col-md-border funktionen " style="text-align: justify;>
{{#widget:YouTube
|width=100%
|height=100%
|id=hMaEIa2DMNs}}
</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Manage predictors ===
Predictors are intelligent assistants, that are optimised to analyse documents for particular aspects, e.g. the document language, important terms or to learn from user generated tags. The Easy Tagging App provides a dialog where you adopt predictors for your particular situation and monitor their performance when they are trained (to learn user generated tags).
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Predictors.png|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Built-in machine learning capabilities ===
State-of-the-art machine learning algorithms are capable of learning from the way your libraries are tagged, and to reflect this acquired knowledge to automatically tag new documents similarly. The Easy Tagging App let's you inspect the "success rate" of your predictor during training and to tweak parameters to achieve optimal prediction rates for new documents.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:performance.png|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Automatic email forwarding ===
Create a shared mailbox in office 365, like inquiries@yourcompany.com. Store typical emails in a newly created library, and teach-in a "Easy Tagging"-predictor. In the "Easy Tagging" configuration page: create a new "Email dispatcher" and enter target email addresses, and enter the address of the shared mailbox, e.g. inquiries@yourcompany.com. The Email dispatcher is now processing automatically incoming emails and forwards them according to the classification.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Maildispatcher.JPG|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Tag all occurences of terms and labels in a termset ===
The new "Find terms"-predictor tags all documents with occurences of terms and synonyms in a termset. Just create a termset that includes your company's product names, groups and their synonyms and let the Easy Tagging App automatically tag your libraries of marketing materials, product manuals etc. Your users will be able to browse for product documents in the search center.
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Findterms.PNG|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Easy evaluation (no credit card needed) ===
You can immediately evaluate the Easy Tagging App for free for an unlimited time for upto 150 documents per library NOW. Just open the tab "Predictors and Taggers" and follow the guide which explains how to connect to the IDAS Evaluation Service in 2 steps!
</div>
<div class="col-md-6 col-md-border funktionen imageExpand" style="text-align: justify;>[[File:Eval.png|x300px|center|middle]]</div>
</div>
<div class="row funktionen-row">
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;">
=== Analyses office documents, pdf, scans and emails===
The Easy Tagging App is able to extract text and information from Microsoft Office file formats word, excel, txt, pdf and text contained in document scans, like png, and emails.
</div>
<div class="col-md-6 col-md-border funktionen" style="text-align: justify;></div>
</div>
<div class="row funktionen-row">
<div class="col-md-12 col-md-border funktionen" style="text-align: justify;">
=== Installation ===
# Get the "Easy Tagging App" for Sharepoint online/Office 365 from Microsoft App Source: [https://appsource.microsoft.com/en-us/product/office/WA200000136?tab=Overview open]
# Follow the installation instructions from Microsoft
# Open the Easy Tagging App in your Sharepoint site and follow the virtual assistant which guides you through the evaluation process.

The App is currently not available for Sharepoint onpremise.
</div>

</div>
</p>
</div>
<h2>Evaluate for free</h2>
{{Easy_Tagging_for_SharePoint_online/Kostenlose_Testversion}}

<h2>Get your commercial license</h2>
<div>
<p>
{{LizenzFormTermExtractor
|productname=Easy Tagging App for SharePoint online
|licensepage=MediaWiki:Lizenz_TermExtractor
|nextpage=Download/thank_you
}}</p>
</div>

<h2>User manual</h2>
<div>
<p>{{#ask:[[Category:Manual]][[hasRelatedProduct::{{FULLPAGENAME}}]]|format=ul}}</p>
</div>
</div>
</div>

</div>
<div class="hideSM col-md-4 col-lg-3 col-xl-2 stickyColumn">
{{Linkbox
|color=#a0b844
|align=left
|heading=Links
|links=
{{ButtonOpenTab|solid=solid|expandsection=Evaluate for free|text=Evaluate for free}}<br>
{{ButtonOpenTab|solid=solid|expandsection=Get your commercial license|text=Get your commercial license}}<br>
{{ButtonOpenTab|solid=solid|expandsection=Features + installation|text=All features}}<br>
{{ButtonOpenTab|solid=solid|expandsection=News about the product|text=News about the product}}
}}
{{Linkbox
|color=#a0b844
|heading=Video
|align=center
|links=
{{#widget:YouTube
|width=100%
|height=100%
|id=8_ss16-t2B0}}
{{ButtonOpenTab|fontsize=small|expandsection=Watch the video|text=Watch the video}}}}
{{Ansprechpartner|hansch}}
</div>
</div>