Skip to content

Commit

Permalink
Update readme
Browse files Browse the repository at this point in the history
  • Loading branch information
RobLBaker committed Feb 13, 2024
1 parent 6279874 commit 7e17ad7
Showing 1 changed file with 6 additions and 10 deletions.
16 changes: 6 additions & 10 deletions README.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ knitr::opts_chunk$set(

## Overview

The goal of EMLeditor is to edit EML-formatted xml files. Specifically, EMLeditor provides many functions that will be useful to the U.S. National Park Service when generating metadata for statistical data packages uploaded to DataStore. NPS affiliation is assumed as default. However, some of the functions for viewing and editing metadata may be useful to people outside the NPS.
The goal of EMLeditor is to edit EML-formatted xml files. Specifically, EMLeditor provides many functions that will be useful to the U.S. National Park Service when generating metadata for statistical data packages uploaded to DataStore. NPS affiliation is assumed as default. However, the functions for viewing and editing metadata may be useful to people outside the NPS.

## Installation and updates

Expand All @@ -46,11 +46,11 @@ devtools::install_github("nationalparkservice/NPSdataverse")

EMLeditor comes with a template Rmarkdown script that you can edit to generate a fully fledged EML document. The script includes and accompanying documentation includes information on:

1) Generating an initial EML document using the R/EMLassemblyline package functions
2) Adding in NPS specific and DataStore specific EML elements using the R/EMLeditor package functions
3) Checking the EML document to make sure it is schema-valid and passes all the necessary tests for uploading to DataStore
4) Generating a draft data package reference on DataStore and incorporating DOIs into the metadata
5) Uploading a completed data package to DataStore
1) Generating an initial EML document using the R/EMLassemblyline package functions
2) Adding in NPS specific and DataStore specific EML elements using the R/EMLeditor package functions
3) Generating a draft data package reference on DataStore and incorporating DOIs into the metadata
4) Checking the EML document to make sure it is schema-valid and passes all the necessary tests for uploading to DataStore (using the `run_congruence_checks()` function from the [DPchecker](https://nationalparkservice.github.io/DPchecker/) package)
5) Uploading a completed data package to DataStore

Please *DO NOT ACTIVATE* the DataStore reference: prior to activation, data packages need to be reviewed via a yet-to-be-created process.

Expand All @@ -63,7 +63,3 @@ To access the EML creation script from within EMLeditor, install (or update) the
If you use EMLeditor functions to alter your metadata (e.g. "set" class functions) they will also silently add the National Park Service as a publisher (including location, [ROR id](https://ror.org/), etc) to your metadata unless you set NPS=FALSE. If you leave the default setting as NPS=TRUE, EMLeditor will also assume the data package is being created "by or for the NPS" and add that information to the metadata.

EMLeditor will also add information about the version of EMLeditor you used to edit your metadata (for instance if you used "set" class functions).




0 comments on commit 7e17ad7

Please sign in to comment.