Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
docs: Reorganise the main menu and the data menu (#807)
* docs: Update menu + fix broken links * docs: Delete feature 'navigation.sections' * docs: Clean up * docs: Merge data content * docs: Fix typo * chore(work-on-data): fix typo Co-authored-by: flaurens <flavie.laurens@unibas.ch> Co-authored-by: mdelez <60604010+mdelez@users.noreply.github.com>
- Loading branch information
1 parent
57e3ccf
commit f8ef81d
Showing
6 changed files
with
408 additions
and
414 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Search results | ||
|
||
<!-- ### Simple list --> | ||
The results of the search are displayed in an organized list<!--with a small preview-->. You can select one result at a time to get more information. | ||
|
||
*Search result 1: Simple list of results, similar to Google's list of results.* | ||
|
||
⚠ | ||
It is not possible to sort or order by criteria when searching with the full-text search, use the advanced search or the expert search instead to get back sorted results. | ||
<!-- | ||
--- | ||
### Grid list: Lighttable | ||
⚠ *NOT YET IMPLEMENTED* | ||
The results of the search are displayed in a grid list with a big preview. You can select one result at a time to get more information. | ||
*Search result 2: A preview list where the results are presented in tiles.* | ||
--- | ||
### Table: Excel-like view | ||
⚠ *NOT YET IMPLEMENTED* | ||
The search results are displayed in a table with the option to sort them. This layout is enabled when the search has been performed with **only one resource type**. | ||
Each column of the table corresponds to one metadata. | ||
*Search result 3: An Excel-like table view to edit multiple resources at once.* | ||
--> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,105 @@ | ||
# Search and browse | ||
|
||
DSP-APP offers the possibility for the user to search in 3 different ways: **full-text** search, **advanced** search, and **expert** search (Gravsearch query). The search bar is always available in the header of each page, whether logged in or out. | ||
|
||
 | ||
|
||
## Full-text search | ||
|
||
The full-text search performs queries including one or more terms or phrases and returns data that matches the search conditions. By default, the search is performed in all projects stored in DSP. However, it is possible to filter by project using the "Filter by project" menu on the left side of the search bar. | ||
|
||
*<https://admin.dasch.swiss> - Search 1: Full-text search* | ||
|
||
When clicking on the search bar, the search history panel is displayed. The last **10** searches are registered. It is also possible to clear the search history list (*Clear list* button at the bottom of the panel or the *x* at the end of each line). | ||
|
||
*Search history list is accessible for the full-text search from any webpage.* | ||
|
||
Special syntax: | ||
|
||
- question mark? can be used as a wildcard symbol for a single character. | ||
- asterisk* can be used as a wildcard symbol for zero, one, or multiple characters. | ||
- "quotation marks" searches for the whole pattern. | ||
|
||
--- | ||
|
||
## Advanced search | ||
|
||
 | ||
|
||
The advanced search allows the creation of complex queries using a form. | ||
The form creates a string representing a Gravsearch (SPARQL) query to be sent to DSP-API. | ||
|
||
A query consists of the following elements: | ||
|
||
- selection of the data model | ||
- selection of a resource class belonging to the selected data model (optional) | ||
- specification of properties, comparison operators, and values (optional). | ||
|
||
Although the selection of a resource or a property or both are optional, either a resource class has to be selected or at least one property has to be specified, otherwise, the query is not considered valid and cannot be submitted. | ||
|
||
*<https://admin.dasch.swiss> - Search 2: Advanced search offers many filter combinations and is a powerful search tool.* | ||
|
||
### Comparison Operators | ||
|
||
Depending on the value type of the chosen property, | ||
one or more of the following comparison operators can be selected: | ||
|
||
- `is equal to`: value equality: same number, exact same string, an overlap of date periods, same target resource. | ||
- `is not equal to`: value inequality: not same number, not exact same string, no overlap of date periods, not same target resource. | ||
- `is greater than`: value comparison: number is greater than search value, date period begins after search value. | ||
- `is greater than or equal to` value equality/value comparison: number is equal to or greater than search value, an overlap of date periods or date period begins after search value. | ||
- `is less than`: value comparison: number is less than search value, date period ends before search value. | ||
- `is less than or equal to`: value equality/value comparison: number is equal to or less than search value, an overlap of date periods or date period ends before search value. | ||
- `exists`: value for the given property exists. | ||
- `is like`: search value is contained in a text using the SPARQL [REGEX](https://www.w3.org/TR/sparql11-query/#func-regex) function (supports regular expressions). | ||
- `matches`: | ||
- text property: search value matches the text ([Lucene Query Parser Syntax](https://docs-api.dasch.swiss/08-lucene/lucene-query-parser-syntax/)). | ||
- linking property: matches the specified linked resource. | ||
|
||
### Search Examples | ||
|
||
#### is like (regular Expressions) | ||
|
||
The `is like` operator lets the user search for texts that are *like* the search value via the support of regular expressions | ||
In this example, all books are found whose title contains "Narrenschiff" followed by a space and some other characters like "(lat.)" or "(dt.)". | ||
|
||
For general information about regular expressions, see this [interactive tutorial](https://regexone.com). | ||
|
||
 | ||
|
||
#### matches (Lucene Parser Syntax) | ||
|
||
Used with a text property, the `matches` operator lets the user search for texts that *match* the search value, | ||
supporting [Lucene Query Parser Syntax](https://docs-api.dasch.swiss/08-lucene/lucene-query-parser-syntax/). | ||
In this example, all persons are found whose names contain "Ja" and "ob" with a character in between (represented by the wildcard "?"). | ||
This search finds "Jacob" as well as "Jakob". | ||
|
||
**Note the difference between regular expressions and Lucene parser syntax!** | ||
|
||
 | ||
|
||
#### matches (specifying a Linked Resource) | ||
|
||
Used with a linking property, the `matches` operator lets the user search for a linked resource that matches the specified properties. | ||
In this example, the user writes a query looking for all letters that have an author that: | ||
|
||
1. was born after January 1st, 1650 | ||
1. whose family name is "Bernoulli" | ||
|
||
This is different from the "is equal to" operator that lets the user specify a certain person (selected from a list). | ||
|
||
 | ||
|
||
--- | ||
|
||
## Expert search | ||
|
||
 | ||
|
||
The expert search can be more powerful than the advanced search, but requires knowing how to use the query language Gravsearch (based on SparQL and developed by the DaSCH team). With Gravsearch, expert users can build searches by combining text-related criteria with any other criteria. | ||
|
||
**For example**: you could search for a page in a manuscript that contains a certain element and also mentions a person, who lived in the same country as another person, who is the author of another author. | ||
|
||
*<https://admin.dasch.swiss> - Search 3: Expert search is a text area in which you can create Gravsearch queries. Here is the default example you can find in the app.* | ||
|
||
To learn Gravsearch, go to the DSP-API documentation [→ Gravsearch](https://docs-api.dasch.swiss/03-apis/api-v2/query-language/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Data management | ||
|
||
Once your [data model](https://docs.dasch.swiss/latest/DSP-APP/user-guide/project/#data-model) is ready, you're able to add data. The DSP-APP offers several possibilities to add data, whether you are starting from scratch or importing data from another program. | ||
|
||
## Start from scratch | ||
|
||
When a project starts from scratch, you will enter and generate new data directly in the DSP-APP itself. Generating new data can be done one by one with a form at the moment: | ||
|
||
- Upload files, e.g., an audio file, photography, a video, or a document | ||
- Augment the metadata | ||
|
||
### Create new resource instances | ||
|
||
You can create a new resource instance using the "create new resource" form: | ||
|
||
*There is a button to open the create new resource form in the main header.* | ||
|
||
**Step1:** Select the project you want to work with (if you are part of several ones), select the ontology (if the project has several ones), and then select the resource class you want to create a new instance. Click on Next. | ||
|
||
*Step 1: Create a new resource instance e.g. a new audio file.* | ||
|
||
**Step2:** Fill in the form and upload the file if requested (depending on the type of resource). Please, note that the required fields are marked with an asterisk `*` after the property label. Click on `Save` to create the new resource instance. To go back to Step 1, click on `Back`. If you cannot click on `Save`, it means that a required field has not been filled in. | ||
|
||
*Step2: Create a new resource instance e.g. a new audio file in MP3 format.* | ||
|
||
N.B.: Please, note that the image, video, and audio files must be in one of the required file types supported by the database. The supported types are listed in the upload section of the form. |
Oops, something went wrong.