codes2jabref: Create Custom Name Entry Type for Jabref

Description Usage Arguments Examples

Description

Creates a custom entry type template that can be imported into Jabref to ensure consistency in entry field names across coders

Usage

1
2
3
  codes2jabref(required_field = NULL,
    optional_field = NULL, file = NULL,
    custom_name = "META", lazy = TRUE)

Arguments

required_field

Character vecor of items to put in the required field (it is suggested the user use only one field and leave the optional field blank).

optional_field

Character vector of items to include in the optional field.

file

A path or a character string naming the file to print to (if does not end in .bib or .txt and lazy = TRUE a .bib will be added to the path name).

custom_name

The name given to the JabRef custom entry type (default is META).

lazy

logical. If TRUE and file does not end in .bib or .txt and lazy = TRUE a .bib will be added to the path name.

Examples

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
codes2jabref(
    required_field = c("study", "author", "n.obs", "type"),
    optional_field = c("corr.mat", "reliabilities"),
    file = NULL,
    custom_name = "META_STUDY"
)
## Not run: 
codes2jabref(
    required_field = c("study", "author", "n.obs", "type"),
    optional_field = c("corr.mat", "reliabilities"),
    file = "meta_study",
    custom_name = "META_STUDY"
)

## End(Not run)

trinker/metaDAT documentation built on May 31, 2019, 8:52 p.m.