Decide whether report venue type (journal, preprint, conference, thesis) is recorded in the data

Abierto
  • ¿Algo no está bien?
#147 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
html
Área
data

Línea de trabajo

Start by reading the matching flora-explorer issue 40 and the proposal/preprint-venues branch mentioned in the issue. The open question is which venue types and publication rules to adopt, including who will curate unknowns; agree on those decisions before estimating an implementation. Done means the project has chosen an option and documented the vocabulary, rules, and ownership.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Raised by the FLoRA Explorer usability review of 21 October 2026. A matching issue is open in flora-explorer: https://github.com/forrtproject/flora-explorer/issues/40.

Question

Should a report's venue type (journal, repository/preprint, conference output, thesis, unknown) be recorded in the FLoRA/FReD data, or derived by each downstream tool?

The data currently has only free-text journal_r / journal_o, doi_r and url_r. FLoRA Explorer's Publication Type tab infers the venue type from keywords in journal_r. The inference gets a lot wrong:

  • Most preprints are classified as "Unknown venue". 284 replication pairs have no venue type. At least 238 of them have a repository DOI or URL:

    • osf.io URLs: 158
    • PsyArXiv DOIs: 41
    • OSF DOIs: 11
    • bioRxiv/medRxiv: 11
    • SSRN: 6
    • Research Square: 3
    • SocArXiv, Preprints.org, PeerJ Preprints, HAL: 7

    Only 39 pairs are recognised as preprints.

  • "Proceedings" is treated as a conference. This sends Proceedings of the National Academy of Sciences (25 pairs) and Academy of Management Proceedings (4) to "Conference output".

  • Venue names alone are ambiguous. 140 pairs with a named journal also have an OSF URL. A Zenodo deposit is recorded under a lab name ("Clearer Thinking"), and a PsychArchives deposit under "Leibniz Institute for Psychology (ZPID)".

  • Later publication is ignored. A preprint that has since been published is still classified as a preprint.

Options

  1. Curated field in the data. Add venue_type_r (and possibly venue_type_o) with a fixed vocabulary, set at entry or validation. It is the most accurate option and serves every consumer the same way, but it needs coder time and a backfill.
  2. Derived field at ingestion. flora-validation computes venue_type_r from DOI prefix, URL host and venue name using shared, documented rules, and flags uncertain rows for curation. The rules are maintained once, and FLoRA Explorer simply reads the field.
  3. Leave it to each tool. This is the status quo. FLoRA Explorer would keep its own rules; branch proposal/preprint-venues in flora-explorer has a deterministic DOI/URL/name version with tests, which reduces Unknown from 284 to 46.

Option 2, with manual overrides, looks like the best balance. It needs agreement on:

  • the vocabulary: is "repository/preprint" one category, or are registrations and data deposits separate?
  • the rules for preprints that were later published: record the version actually linked, or the latest version?
  • who curates the remaining unknowns.
Lenguaje dominante
HTML
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de forrtproject/fred-data

Todos los issues de forrtproject/fred-data

Issues similares

Más issues de Data Engineering

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.