2025 June 17
Evolving the preprint evaluation world with Sciety
This post is based on an interview with Sciety team at eLife.
Our query engine operates by evaluating several logic rules in order. Each rule focuses on certain fields in the query, with the first rule processing the entire query. If any rule returns a single DOI as its output, this DOI is taken as the result for the query, and rule processing terminates.
In an XML query you can exercise some control over how the query engine works by using the match
attribute that is available on many query elements.
match=""
) tells the query engine that this field is not optional and must be present, and matched, for a DOI match to occur.match=""
(which means not optional and not fuzzy). Using exact
is not compatible with optional
, or fuzzy
.<author match="null"/>
Multiple values may be assigned (as in match="optional fuzzy"
). Typical uses include:
match="fuzzy"
- instructs the query engine to apply its fuzzy comparison logic for this fieldmatch="optional fuzzy"
- a rule may drop the field altogether or use fuzzy matchingmatch="exact"
- field must be matched and no fuzzy matching is allowedmatch=""
- same as match="exact"