From 7092ba8a8704033094b4e1e3b6420c0bc1a2314a Mon Sep 17 00:00:00 2001
From: Rob Baker If you would like to contribute code please make the adjustments and issue a pull request. The development team will review your code prior to merging and pull request. Before issuing a pull request make sure: 1) You have added a description of any changes made to the changelog in NEWS.md 2) If you have added a function, make sure you also include unit tests that cover the function. If you have changed a function, make sure the unit tests still pass. 3) If you have added or changed a function, make sure that the package loads using If you would like to contribute code please make the adjustments and issue a pull request. The development team will review your code prior to merging and pull request. Before issuing a pull request make sure: 1) You have added a description of any changes made to the changelog in NEWS.md 2) If you have added a function, make sure you also include unit tests that cover the function. If you have changed a function, make sure the unit tests still pass. 3) If you have added or changed a function, make sure that the package loads using How Do I Submit a Good En
Your First Code Contribution
-devtools::load_all(). 2) You have updated any necessary documentation using devtools::document() 3) You have updated the associated web pages using pkgdown::build_site_github_pages() 4) You have checked that there are no errors or warnings when the package is built using devtools::check().devtools::load_all(). 2) You have updated any necessary documentation using devtools::document() 3) You have updated the associated web pages using pkgdown::build_site_github_pages() 4) You have checked that there are no errors or warnings when the package is built using devtools::check().Softwareinstall.packages(c("remotes", "tidyverse"))
#the NPSdataverse includes EMLassemblyline, EMLeditor, and several other useful packages:
-remotes::install_github("doi-nps/NPSdataverse")
+remotes::install_github("doi-nps/NPSdataverse")
library(tidyverse)
library(NPSdataverse)
Install and Load R Packages
+remotes::install_github("doi-nps/NPSdataverse")
#install packages
install.packages(c("remotes", "tidyverse"))
-remotes::install_github("doi-nps/NPSdataverse")
# When loading packages, you may be advised to update to more recent versions
# of dependent packages. Most of these updates likely are not critical.
@@ -277,8 +277,8 @@ Temporal information
-
startdate <- ymd("2010-01-26")
-enddate <- ymd("2013-01-04")startdate <- ymd("2010-01-26")
+enddate <- ymd("2013-01-04")
FUNCTION 1 - Core Metadata Infor
using
EMLeditor::set_int_rights(). There is no need to edit
this .txt file.
-
EMLassemblyline::template_core_metadata(path = working_folder,
+EMLassemblyline::template_core_metadata(path = working_folder,
license = "CC0") # that '0' is a zero!FUNCTION 2 - Data Table Attributes
-
EMLassemblyline::template_table_attributes(path = working_folder,
+EMLassemblyline::template_table_attributes(path = working_folder,
data.table = data_files,
write.file = TRUE)FUNCTION 3 - Data Table Ca
these files already exist from a previous run, they are not
overwritten.
-EMLassemblyline::template_categorical_variables(path = working_folder,
+EMLassemblyline::template_categorical_variables(path = working_folder,
data.path = working_folder,
write.file = TRUE)
-EMLassemblyline::template_geographic_coverage(path = working_folder,
+EMLassemblyline::template_geographic_coverage(path = working_folder,
data.path = working_folder,
data.table = data_coordinates_table,
lat.col = data_latitude,
@@ -404,7 +404,7 @@ FUNCTION 5 - Taxonomic Coverage
-EMLassemblyline::template_taxonomic_coverage(path = working_folder,
+EMLassemblyline::template_taxonomic_coverage(path = working_folder,
data.path = working_folder,
taxa.table = data_taxa_tables,
taxa.col = data_taxa_fields,
@@ -423,7 +423,7 @@ Create an EML object
-my_metadata <- EMLassemblyline::make_eml(path = working_folder,
+my_metadata <- EMLassemblyline::make_eml(path = working_folder,
dataset.title = package_title,
data.table = data_files,
data.table.name = data_names,
@@ -440,7 +440,7 @@ Check for EML validity
This is a good point to pause and test whether your EML is valid.
-EML::eml_validate(my_metadata)
+EML::eml_validate(my_metadata)
if your EML is valid you should see the following (admittedly
cryptic) result:
# [1] TRUE
@@ -656,7 +656,7 @@ Validate your EML
-EML::eml_validate(my_metadata)
EML::eml_validate(my_metadata)
if your EML is valid you should see the following (admittedly crypitic):
# [1] TRUE
@@ -674,7 +674,7 @@ Write your EML to an xml file
-EML::write_eml(my_metadata, "mymetadatafilename_metadata.xml")
+EML::write_eml(my_metadata, "mymetadatafilename_metadata.xml")
# This assumes that you have written your metadata to an .xml file and that the .xml file is in the current working directory.
-DPchecker::run_congruence_checks(check_metadata_only = TRUE)
+DPchecker::run_congruence_checks(check_metadata_only = TRUE)
# If you .xml file with metadata is in a different directory, you will have to specify that:
# DPchecker::run_congruence_checks("C:/Users/<yourusername>/Documents/my_data_package", check_metadata_only = TRUE)
# this assumes that the data package is the working directory
-DPchecker::run_congruence_checks()
+DPchecker::run_congruence_checks()
# if your data package is somewhere else, specify that:
# DPchecker::run_congruence_checks("C:/Users/<yourusername>/Documents/my_data_package")
# install.packages("pak")
-pak::pkg_install("doi-nps/EMLeditor")
+pak::pkg_install("doi-nps/EMLeditor")
# alternatively:
-remotes::install_github("doi-nps/eMLeditor")To install all the packages in the NPSdataverse (including EMLeditor):
-pak::pkg_install("doi-nps/NPSdataverse")
+pak::pkg_install("doi-nps/NPSdataverse")
#alternatively:
-remotes::install_github("doi-nps/NPSdataverse")Maintainer: Robert Baker robert_baker@nps.gov (ORCID)
-Authors:
Judd Patterson Judd_Patterson@nps.gov (ORCID)
Authors:
Robert Baker robert_baker@nps.gov (ORCID)
Judd Patterson Judd_Patterson@nps.gov (ORCID)
Other contributors: