VITALISE D2.4 Standard Version 3
Bibliographic record
Abstract
Although Living Labs have emerged as resilient research and innovation infrastructures and have proved to be a “key” to the integration of research and innovation processes in real-life settings, they still fail to provide and function according to unified and harmonized processes that are easily accessible and exploitable by academic and industry researchers. Towards this end, VITALISE aims to create the first Harmonization guidelines for Living Labs that will facilitate the access of researchers to the provided infrastructures. This document presents the work performed for the Harmonization of the way Living Labs work for the third semester of VITALISE. Taking as a starting point the work performed for the Standard v0.1 and the Standard v.02, VITALISE conducted several Harmonization activities with consortium partners and external stakeholders in order to create the Standard v0.3 presented in this document. Standard v0.1 included the state of the art information about Living Labs in the VITALISE consortium and was the first deliverable that set up the structure of the VITALISE Standards. Standard v0.2 included activities for the production and dissemination of a wiki page that included the Standard v0.1 and work was also done towards updating the parts of the Standard that describe the data and technologies used in living labs, using a Delphi study method and collected the first set of terms for the living lab lexicon. Moreover, during the second semester, the Harmonization Board was established and a meeting with the Harmonization Body took place as well. The implemented activities for the current deliverable included the preparation of two templates for the co-creation sessions performed during the Joint Research Activities (JRAs). Also, for the current update of the Standard, it was conducted a session for updating the devices and technologies taxonomy (Delphi study), some meetings and sessions devoted to the services and procedures categorization, as well as some meetings and activities for collecting and reaching a preliminary consensus upon the terms of the living lab lexicon. In addition, during this third semester, took place the 2nd plenary meeting of the project in Helsinki, as well as the 2nd Harmonization Body meeting. The final Section of this document presents the Standard v0.3 that will be also published in the living lab harmonization wiki page.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.017 | 0.059 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.006 | 0.004 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.014 | 0.007 |
| Open science | 0.005 | 0.007 |
| Research integrity | 0.006 | 0.005 |
| Insufficient payload (model declined to judge) | 0.078 | 0.125 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".