-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Granularity levels, verification and Quality Control #195
Comments
I'm adding the specifications for each level and further descriptions |
@myrmoteras please check it out |
It would also be really useful to have this tags findable through the TB Stats |
Sure thing ... once they are defined and we start assigning them, that is ... beforehand, there's preciously little sense in adding a bunch of empty stats fields. |
Completely agree, and that's why we are here discussing them :) |
@flsimoes let's define the granularity levels, and let's have 3- 5 "gold standard" publications where we can show this, and which include the variation of treatments, ie
|
We're currently gathering examples |
example papers:
|
We need to flesh out a few things, such as difference between automatic and manual bibRef parsing and level of detail of matCit parsing. |
Annotations for level 4, covering treatments, NOT tables yet.see also Agosti et al, 2022 for further explanation of the annotations.
Nesting of the annotationsThe tags have specific positions in a treatment.
|
@flsimoes can you please make sure that these examples are all high level and checked - so they work as examples. |
We'll make sure of that |
All high-level now |
TaxPub - level-1 |
From Patrick Ruch "The document granularity is one of the subject of BioHackathon n26 that we are organizing; therefore I am cc-ing to Alexandre and Julien for respectively the Elixir BioHackathon, which is currently going on, and the BioC format used in SIBiLS and displayed in Pam's module. Let's add it to the agenda of thursday !" |
We need to define what we understand as Granularity, Verification and Quality Control, and what levels to assign to it.
EDIT: QC and Verification are dropped. We'll focus on general granularity + a QCd/Not-QCd tag
Granularity
The level of processing applied to a given document. This is the level to which the batch (or an individual extraction) goes to.
At the moment, processing through batch currently does not enable any partial processing, meaning it activates all the treatment, treatmentCitation, and materialsCitation macros. In order to apply the levels below we would need to implement elements that enables the template creator to signal at what point a batch process should stop.
(DEPRECATED)
Quality Control
The amount of verification and parsing Plazi applies to a given document. This QC level system is a translation of what we currently dub "Granularity levels"
Verification
The level to which a document has been fully checked by an user. The inspiration for this model is iNaturalist
The text was updated successfully, but these errors were encountered: