NEWS

---

metacore 0.1.3 (2024-05-02)

• Add get_keys function which returns the dataset keys for a given dataset #102
• Fix issues with select_dataset(simplify = TRUE) #97

metacore 0.1.2 (2023-03-02)

• Update to resolve issues from the dplyr updates

metacore 0.1.1 (2022-12-07)

• Add variable cross checks to check consistent use of label, type, and format
• Add is_metacore() function to check if it is a metacore object
• #64 Resolve issue so define and spec readers work when value levels are empty

metacore 0.1.0 (2022-10-04)

• Updates for latest version of {tidyselect}
• Move from XML to xml2 for define.xml processing
• Correct issue with warning on ds_var$core
• Correct bug with not reading the derivation of predecessor and assigned variables correctly

metacore 0.0.6

• Correct typos
• Limits origin value/make all origins lower case

metacore 0.0.5

• #47 Improve yn_to_tf() to be more robust in parsing yes/no columns

metacore 0.0.4 (2022-03-31)

• Adds a supp table to store the idvar and qeval information
• Adds sig_digcolumn to the value_spec table

metacore 0.0.3 (2022-02-14)

• Fixes bugs found in the get_control_term function and improves error messages for get_control_term
• Improves internal naming consistency by renaming define_to_MetaCore to define_to_metacore
• Adds quiet option to readers, to allow users to optionally ignore the reader warnings
• Creates new example metacore object that is an .rda so much faster to read in
• Fixes issue with select dataset when variables are duplicated

metacore 0.0.1

This fixes the following issues:

• #16 the metacore function now accepts any empty datasets and creates an empty dataset with the correct column names and types
• #10 yn function checks for logicals and returns them
• #11 updated function description to make this clearer
• #12 updated regex so to "[F|f]ormat" so it can accept lower case
• #14 added supp_flag to ds_vars (on a side note we did a really good job with this it was super easy to change and only required a few edits)
• #15 modified create_tbl so if there are two potential matches in the same dataset and one is an exact match it uses that

Additionally, it adds the get_control_term function to get pull out the control term for a given variable.