Nemcio/SCM-Manager
1
0
Fork 0
mirror of https://github.com/scm-manager/scm-manager.git synced 2025-11-10 07:25:44 +01:00
Code Issues Packages Projects Releases Activity
Files
9458514129532d247357fceb9f738dc81a9a43de
SCM-Manager/scm-ui/ui-api/src/help/search/syntax.de.ts

78 lines
4.1 KiB
TypeScript
Raw Normal View History

Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
/*
Change to GNU Affero General Public License v3.0
2024-09-24 09:42:07 +02:00
* Copyright (c) 2020 - present Cloudogu GmbH
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
*
Change to GNU Affero General Public License v3.0
2024-09-24 09:42:07 +02:00
* This program is free software: you can redistribute it and/or modify it under
* the terms of the GNU Affero General Public License as published by the Free
* Software Foundation, version 3.
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
*
Change to GNU Affero General Public License v3.0
2024-09-24 09:42:07 +02:00
* This program is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
* FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
* details.
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
*
Change to GNU Affero General Public License v3.0
2024-09-24 09:42:07 +02:00
* You should have received a copy of the GNU Affero General Public License
* along with this program. If not, see https://www.gnu.org/licenses/.
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
*/
Change to GNU Affero General Public License v3.0
2024-09-24 09:42:07 +02:00
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
export default `## Modifikatoren
Hinweis: Sie können keine Wildcards als erstes Zeichen einer Suche verwenden.
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
|Definition|Beispiel|
|----------|--------|
|? - Einzelzeichen-Wildcard|"Ultimate?Repo" - findet z.B. \`Ultimate-Repo\`, \`Ultimate Repo\`, \`Ultimate+Repo\`|
|* - mehrstelliger Platzhalter|"Ultimat*y" - findet z.B. \`Ultimate Repository\`, \`Ultimates-Spezial-Repository\`, \`Ultimate\`|
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
### Bereiche
Bereichsabfragen ermöglichen den Abgleich von Dokumenten, deren Feldwerte zwischen der unteren und der oberen Grenze liegen, die in der Bereichsabfrage angegeben sind. Bereichsabfragen können die obere und untere Grenze einschließen oder ausschließen. Die Sortierung erfolgt lexikografisch.
Bereiche sind nicht auf numerische Felder beschränkt.
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
|Definition|Beispiel|
|----------|--------|
|[ … TO … ] - inklusiver Bereich|"creationDate:[1609459200000 TO 1612137600000]" – findet z.B. Repositories, die zwischen dem 01.01.2021 und dem 01.02.2021 angelegt wurden|
|{… TO …} - ausschließender Bereich|"name:{Aida TO Carmen}" – findet Namen zwischen Aida und Carmen, jedoch ohne die beiden Namen einzuschließen|
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
## Boosten
Mit dem Boosting können Sie die Relevanz eines Dokuments steuern, indem Sie seinen Term verstärken.
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
|Definition|Beispiel|
|----------|--------|
|Begriff^Zahl|"ultimate^2 repository" – erhöht die Relevanz von \`ultimate\`|
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
Standardmäßig ist der Boost-Faktor 1. Obwohl der Boost-Faktor positiv sein muss, kann er kleiner als 1 sein (z. B. 0,2)
Standardmäßig werden Repository-Namen um 1,5 und Namespace-Namen um 1,25 geboostet.
## Boolesche Operatoren
Hinweis: Logische Operatoren müssen in Großbuchstaben eingegeben werden (z. B. „AND").
Fix encoding in global search (#2116) Using plus symbol in global search led to a space in the query parameter of the URL. We now encode the query string properly in global search and additionally fixed the expert search documentation.
2022-09-14 08:05:31 +02:00
|Operator|Definition|Beispiel|
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
|--------|----------|--------|
|AND|Beide Terme müssen enthalten sein|"Ultimate AND Repository" – findet z.B. \`Ultimate Repository\`, \`Ultimate Special Repository\`|
|OR|Mindestens einer der Terme muss enthalten sein|"Ultimate OR Repository" – findet z.B. \`Ultimate Repository\`, \`Ultimate User\`, \`Special Repository\`|
|NOT|Der nachfolgende Term darf nicht enthalten sein, „!" kann alternativ verwendet werden|"Ultimate NOT Repository" – findet z.B. \`Ultimate user\`, nicht jedoch z.B. \`Ultimate Repository\`|
|–|Schließt den folgenden Term von der Suche aus|"Ultimate Repository -Special" – findet z.B. \`Ultimate Repository\`, schließt z.B. \`Ultimate Special Repository\` aus|
|+|Der folgende Term muss enthalten sein|"Ultimate +Repository" – findet z.B. \`my Repository\`, \`Ultimate Repository\`|
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
## Gruppieren
Die Suche unterstützt die Verwendung von Klammern zur Gruppierung von Begriffen, um Teilabfragen zu bilden. Dies kann sehr nützlich sein, wenn Sie die boolesche Logik für eine Abfrage steuern möchten.
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
|Definition|Beispiel|
|----------|--------|
|() – Terme zwischen den Klammern werden gruppiert|"(Ultimate OR my) AND Repository" – findet z.B. \`Ultimate Repository\`, \`my Repository\`, schließt z.B. Super Repository. Entweder "Ultimate" oder "My" müssen im Ergebnis existieren, "Repository" muss immer enthalten sein|
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
## Phrasen
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
Eine Phrase ist eine Gruppe von Begriffen in einer bestimmten Reihenfolge. Falls man nach einer bestimmten Phrase suchen will, dann kann der \`"\`-Operator genutzt werden.
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
|Definition|Beispiel|
|----------|--------|
|"" - Begriffe innerhalb der Anführungszeichen werden als Phrase gesucht|"Ultimate Repository" – findet \`Ultimate Repository\` aber nicht \`Repository Ultimate\`, \`Ultimate\` oder \`Repository\`|
Add additional help to quick search and an advanced search documentation page (#1757) Co-authored-by: Sebastian Sdorra <sebastian.sdorra@cloudogu.com>
2021-08-09 12:07:28 +02:00
Fix exact search Previously a query was only parsed by lucene as it is, if the query contained a colon (:) or a wildcard character (*). With this, every query gets parsed as it is, as long as there is one operator contained inside the query (colon, quotation marks, logical operators, ...). These are called "expert queries". All other queries are still processed as "simple queries" where every part of the query is extended with a wildcard operator. Addtionally the user is now getting feedback for every search, if the query is a simple query or an expert query. The syntax documentation got also extended with the quotation mark operator and the definition of the two query types. Co-authored-by: René Pfeuffer<rene.pfeuffer@cloudogu.com>
2024-05-14 11:45:10 +02:00
`;
Reference in New Issue Copy Permalink