Questions & Answers

Byleron Bibliometrics is a browser-based workspace for importing bibliographic records, documenting search decisions, cleaning evidence, running bibliometric analyses, and preparing traceable figures, tables, and reporting text.

Link to this answer

Work from left to right: record the search protocol, import and audit records, resolve cleaning decisions, run analyses, add selected evidence to Results, and export the publication package.

What to do

1. Create a project and record the research question.
2. Save a versioned search protocol before analysis.
3. Import records, review data quality, duplicates, eligibility, and integrity checks.
4. Generate only the analyses supported by the available metadata.
5. Review and add publication-ready items to Results.

Link to this answer

They establish the scope, databases, search fields, query, date limits, and retrieval date used to assemble the evidence base. Saved versions make later changes visible instead of silently overwriting the original plan.

Link to this answer

Project records and decisions are stored in the WordPress installation used by the workspace. Access therefore depends on the site administrator’s hosting, backup, account, and security configuration.

Link to this answer

The workspace accepts Web of Science or OpenAlex tagged text, structured TXT or CSV tables, Scopus CSV, BibTeX or BibLaTeX, RIS, PubMed XML, Crossref JSON, and OpenAlex JSON.

Link to this answer

Yes. Import multiple source files into the same project, preserve their source provenance, and resolve duplicate candidates before analysis. Database coverage and export settings should still be reported as part of the search method.

Link to this answer

Dataset readiness summarizes whether fields required by each method are present after cleaning. A method may be ready, limited, or unavailable depending on coverage of years, citations, keywords, references, affiliations, countries, and other metadata.

Link to this answer

Check the original database export settings and file format first. Then review the import audit and normalized-record export to identify whether the problem came from the source data, field mapping, or normalization.

What to do

1. Keep the original export unchanged.
2. Compare a few affected records with the source database.
3. Re-export with complete bibliographic information and cited references when required.

Link to this answer

Exact identifiers can support automatic matches, while uncertain similarities remain review candidates. You can merge a pair, keep it separate, or return it for review, with the decision retained in the audit trail.

Link to this answer

Eligibility filters apply deterministic limits to explicit metadata such as publication year, language, normalized document type, source database, DOI presence, or year presence. Preview the counts before saving an immutable filter version.

Link to this answer

Yes. A record-level override is reversible and requires a rationale. The effective decision and PRISMA counts update while the original rule-based decision remains preserved.

Link to this answer

The workspace checks exact DOI and PubMed identifiers against a time-stamped Crossref Retraction Watch dataset and also inspects explicit integrity flags in imported metadata. Detected records require researcher review.

Link to this answer

Versioning records the exact normalization state used by an analysis. Changes create a new rule version so earlier runs can still be interpreted against the rules that produced them.

Link to this answer

Available methods include descriptive publication and source profiles, citation and productivity indicators, keyword and thematic structures, co-authorship and geographic collaboration, bibliographic coupling, co-citation, comparisons, longitudinal change, and robustness or uncertainty checks when the required fields exist.

Link to this answer

The cleaned evidence base may lack a required field or have insufficient coverage. For example, reference-based networks require cited-reference data, and geographic collaboration requires usable affiliation or country information.

Link to this answer

Interpret nodes, edges, weights, clusters, thresholds, and the displayed-versus-complete network boundary together. A visual cluster is an algorithmic grouping under the recorded settings, not automatically a substantive theory or research theme.

Link to this answer

Rerun after importing new records, changing cleaning or eligibility decisions, saving a new normalization rule version, or intentionally changing method parameters. A rerun creates new analytical evidence rather than editing a frozen result.

Link to this answer

Results Builder collects selected figures, tables, validated insights, audit records, and Methods evidence into a manuscript-oriented reporting layer. Added analytical evidence is frozen so later wording edits do not alter the underlying calculation.

Link to this answer

Yes. Analysis outputs provide figure and evidence downloads where applicable, while Results Builder assembles selected items for manuscript export. Vector SVG is preferred when the journal accepts it; PNG and CSV provide image and tabular alternatives.

Link to this answer

AI reporting is checked against the item’s locked evidence. Text containing unsupported quantities or claims is rejected so fluent wording cannot introduce numbers that were not produced by the calculation.

Link to this answer

Review every statement for numerical accuracy, methodological fit, unsupported causal language, overgeneralization, and consistency with the displayed evidence. Follow the target journal and institution’s AI disclosure requirements.

Link to this answer

The manuscript export is blocked when publication-readiness checks identify missing foundations, such as an unrecorded research question or an unsaved search-protocol version. The audit appendix remains available while these items are corrected.

Link to this answer

A .bibproject.zip archive preserves the project record, protocol versions, imports, normalized records, cleaning and integrity decisions, rule versions, analysis runs, reporting revisions, AI attempts, and export history needed for supported round-trip import.

Link to this answer

Use Import project and choose a valid file ending in .bibproject.zip. The importer validates the archive before restoring its supported project tables rather than treating it as a bibliographic source file.

Link to this answer

Use manuscript DOCX for selected publication content, the audit appendix for decision history, normalized-record CSV for the cleaned evidence base, the reproducibility manifest for technical provenance, and the complete project archive for restoration or transfer.

Link to this answer

Keep the project open, copy the exact message, and retry once after confirming the required fields and connection. If the problem persists, note the action, project area, browser, approximate dataset size, and plugin version for support.

What to do

1. Do not repeatedly click while a request is still processing.
2. Check whether another project action completed before refreshing.
3. Export a complete project archive if that function remains available.

Link to this answer