The preregr vignettes are themselves RMarkdown files. Therefore, the human-readable (pre-)registrations shown there as an example also caused the corresponding JSON to be embedded in those vignettes.

This command imports this information from the preregr Pkgdown website:

importedExample <-
  preregr::import_from_html("https://r-packages.gitlab.io/preregr/articles/specifying_prereg_content.html");

We can then show the result:

importedExample;
#> 
#> ── (Pre)registration specification ─────────────────────────────────────────────
#>  Form: Inclusive Systematic Review Registration Form
#>  65 fields (3 completed, 62 empty)

Or knit it into this vignette (which will then again also embed it as JSON, which can be imported again, etc):

preregr::prereg_knit_item_content(
  importedExample,
  section="metadata"
);

Inclusive Systematic Review Registration Form

Section: Metadata

Target discipline
target_discipline
Unspecified
Title
title
Example Study
Author(s) / contributor(s)
authors
Littlebottom, C., Dibbler, C., & Aching, T.
Tasks and roles
tasks_and_roles
Unspecified

Initializing a new (pre)registration with the for used by an imported (pre)registration

It is also possible to initialize a new preregistration, using the form that was saved along with the preregistered content:

freshPrereg <-
  preregr::prereg_initialize(
    importedExample
  );

This yields an empty preregistration specification:

freshPrereg;


[36m──
[39m 
[1m(Pre)registration specification
[22m 
[36m─────────────────────────────────────────────
[39m

[36mℹ
[39m 
[36mForm: 
[39mInclusive Systematic Review Registration Form

[36mℹ
[39m 65 fields (0 completed, 65 empty)

This way, it’s easy to initialize a preregistration based on the form used by somebody else.