Fundamentals
Research Data Management
FAIR Data Principles
Metadata
Ontologies
Data Sharing
Data Publications
Data Management Plan
Version Control & Git
Public Data Repositories
Persistent Identifiers
Implementation within DataPLANT
Annotated Research Context
User Journey
ARC Commander
QuickStart
QuickStart (experts)
Swate
QuickStart
Walk-through
Best Practices For Data Annotation
DataHUB
DataPLAN
ARC Commander Manual
Setup
Installing Dependencies
Configure Git
Installing the ARC Commander
Windows
MacOS
Linux
DataHUB Access
Before we start
Central Functions
Initialize
Clone
Connect
Synchronize
Configure
Branch
ISA Metadata Functions
ISA Metadata
Investigation
Study
Assay
Update
Export
Swate Manual
Setup
Installing Swate
Browser
Desktop, via installer (beta-stage)
Desktop, manually (recommended)
MacOS
Organization-wide
Core Features
Annotation tables
Building blocks
Building Block Types
Adding a Building Block
Using Units with Building Blocks
Filling cells with ontology terms
Advanced Term Search
Templates
Contribute Templates
File Picker
Expert Features
ISA-JSON
Frequently Asked Questions
Teaching Materials
DataPLANT Overview
Big Picture
ARC structure
ARC Demo
last updated at 2022-09-21
Advanced term search is accessible on multiple occasions, but is functionally the same.
How to use
When using the advanced term search there are four options to further define what you are looking for.
- Term name keywords: Uses Apache Lucene query parser syntax on the term names.
- Term definition keywords: Uses Apache Lucene query parser syntax on the term definitions.
- Ontology dropdown: Search for the above keywords in only one specific ontology.
- Keep obsolete terms: To show obsolete terms in search results or not.
Apache Lucene query parser syntax
You can find in depth information on this topic on the source documentation from Apache Lucene.
Common use cases might include:
- Simple Search. Example
instrument model
specifies that the result MUST contain instrument
OR model
.
+
operator. Example +instrument model
specifies that the result MUST contain instrument
and MAY contain model
-
/NOT
operator. Example instrument model NOT SCIEX
/instrument model -SCIEX
specifies that the result MUST contain instrument
OR model
and MUST NOT contain SCIEX
.
""
grouping. Example "instrument model"
specifies that the result MUST contain instrument model
.
DataPLANT Support
Besides these technical solutions, DataPLANT supports you with community-engaged data stewardship. For further assistance, feel free to reach out via our
helpdesk
or by contacting us
directly
.