Documentation: update URLs and metadata associated with DGEC migration

Author: RobLBaker

CONTRIBUTING.md

@@ -30,13 +30,13 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 
 ## I Have a Question
 
-> If you want to ask a question, we assume that you have read the available [Documentation](https://nationalparkservice.github.io/DPchecker/).
+> If you want to ask a question, we assume that you have read the available [Documentation](https://doi-nps.github.io/DPchecker/).
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/nationalparkservice/DPchecker/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
+Before you ask a question, it is best to search for existing [Issues](https://github.com/doi-nps/DPchecker/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/nationalparkservice/DPchecker/issues/new/choose).
+- Open an [Issue](https://github.com/doi-nps/DPchecker/issues/new/choose).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions , depending on what seems relevant.
 
@@ -57,8 +57,8 @@ We will then take care of the issue as soon as possible.
 A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
 
 - Make sure that you are using the latest version.
-- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://nationalparkservice.github.io/DPchecker/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/nationalparkservice/DPchecker/issues/new/choose).
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://doi-nps.github.io/DPchecker/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/doi-nps/DPchecker/issues/new/choose).
 - Also make sure to search the internet to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
 - Stack trace (Traceback)
@@ -70,12 +70,12 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 #### How Do I Submit a Good Bug Report?
 
-> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to robert_baker@nps.gov.
+> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to [robert_baker@nps.gov](mailto:robert_baker@nps.gov).
 
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-- Open an [Issue](https://github.com/nationalparkservice/DPchecker/issues/new/choose). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Open an [Issue](https://github.com/doi-nps/DPchecker/issues/new/choose). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
 - Explain the behavior you would expect and the actual behavior.
 - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case. See [https://gist.github.com/hadley/270442](https://gist.github.com/hadley/270442) for a great run down on how to create reproducible examples.
 - Provide the information you collected in the previous section.
@@ -94,15 +94,15 @@ This section guides you through submitting an enhancement **including completely
 #### Before Submitting an Enhancement
 
 - Make sure that you are using the latest version.
-- Read the [documentation](https://nationalparkservice.github.io/DPchecker/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/nationalparkservice/DPchecker/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Read the [documentation](https://doi-nps.github.io/DPchecker/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Perform a [search](https://github.com/doi-nps/DPchecker/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library or package.
 - Please consult with the developers if you would like to create an add-on package. Maybe we can help!
 
 
 #### How Do I Submit a Good Enhancement Suggestion?
 
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/nationalparkservice/DPchecker/issues).
+Enhancement suggestions are tracked as [GitHub issues](https://github.com/doi-nps/DPchecker/issues).
 
 - Use a **clear and descriptive title** for the issue to identify the suggestion.
 - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.

DESCRIPTION

@@ -35,7 +35,7 @@ Imports:
     EMLeditor,
     lifecycle
 Remotes: 
-    https://github.com/nationalparkservice/QCkit,
-    https://github.com/nationalparkservice/EMLeditor
-URL: https://github.com/nationalparkservice/DPchecker, https://nationalparkservice.github.io/DPchecker/
-BugReports: https://github.com/nationalparkservice/DPchecker/issues
+    https://github.com/doi-nps/QCkit,
+    https://github.com/doi-nps/EMLeditor
+URL: https://github.com/doi-nps/DPchecker, https://doi-nps.github.io/DPchecker/
+BugReports: https://github.com/doi-nps/DPchecker/issues

NEWS.md

@@ -1,4 +1,7 @@
 # DPchecker 1.1.1
+## 2026-04-22
+  * Documentation (URLs mostly) and metadata (code.json added) updates in preparationfor migration to DGEC.
+  
 ## 2025-07-11
   * Fix bug in `test_datatable_urls_doi()` and `test_datatable_url_attributes()`
   * Fix bug in `test_dp_abstract()`

README.md

@@ -1,7 +1,7 @@
 <!-- badges: start -->
 [![Lifecycle: experimental](https://img.shields.io/badge/lifecycle-experimental-orange.svg)](https://lifecycle.r-lib.org/articles/stages.html#experimental)
-[![CodeFactor](https://www.codefactor.io/repository/github/roblbaker/dpchecker/badge)](https://www.codefactor.io/repository/github/roblbaker/dpchecker)
-[![R-CMD-check](https://github.com/nationalparkservice/DPchecker/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/nationalparkservice/DPchecker/actions/workflows/R-CMD-check.yaml)
+[![CodeFactor](https://www.codefactor.io/repository/github/doi-nps/dpchecker/badge)](https://www.codefactor.io/repository/github/doi-nps/dpchecker)
+[![R-CMD-check](https://github.com/doi-nps/DPchecker/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/doi-nps/DPchecker/actions/workflows/R-CMD-check.yaml)
 <!-- badges: end -->
 
 
@@ -19,7 +19,10 @@ You can install the development version of DPchecker from
 
 ``` r
 # install.packages("pak")
-pak::pkg_install("nationalparkservice/DPchecker")
+pak::pkg_install("doi-nps/DPchecker")
+# alternatively:
+# install.packages("remotes")
+remotes::install_github("doi-nps/DPchecker")
 ```
 
 ## Examples:

code.json

@@ -0,0 +1,50 @@
+[
+  {
+    "name": "DPchecker",
+    "organization": "NATIONAL PARK SERVICE",
+    "description": "Allows the user (and reviewer) to check a data package and test whether it meets the congruence standards set forth by NPS for upload to DataStore as a datapackage.",
+    "version": "1.1.0",
+    "status": "ongoing development",
+    "permissions": {
+      "usageType": "openSource",
+      "licenses": [
+        {
+          "name": "Public Domain, CC0-1.0",
+          "URL": "https://github.com/DOI-NPS/DPchecker"
+        }
+      ]
+    },
+    "homepageURL": "https://github.com/DOI-NPS/DPchecker",
+    "downloadURL": "https://github.com/DOI-NPS/DPchecker",
+    "disclaimerURL": "hhtps://github.com/DOI-NPS/DPchecker/blob/main/LICENSE",
+    "repositoryURL": "https://github.com/DOI-NPS/DPchecker",
+    "vcs": "git",
+    "laborHours": 1,
+    "tags": [
+      "NRSS",
+      "IMD",
+      "r",
+      "schema",
+      "open",
+      "accessible",
+      "open-data",
+      "nps",
+      "reusable",
+      "datastore",
+      "eml",
+      "findable",
+      "interoperable",
+      "national-park-service"
+    ],
+    "languages": [
+      "R"
+    ],
+    "contact": {
+      "name": "Robert Baker",
+      "email": "robert_baker@nps.gov"
+    },
+    "date": {
+      "metadataLastUpdated": "2026-04-22"
+    }
+  }
+]

vignettes/DPchecker.Rmd

@@ -18,11 +18,11 @@ knitr::opts_chunk$set(
 
 # Install DP checker
 
-You can install [DPchecker](https://nationalparkservice.github.io/DPchecker/) as part of the [NPSdataverse](https://nationalparkservice.github.io/NPSdataverse/) using: 
+You can install [DPchecker](https://doi-nps.github.io/DPchecker/) as part of the [NPSdataverse](https://doi-nps.github.io/NPSdataverse/) using: 
 
 ```{r verse_install, eval=FALSE}
-install.packages("devtools")
-devtools::install_github("nationalparkservice/NPSdataverse")
+install.packages("remotes")
+remotes::install_github("doi-nps/NPSdataverse")
 library(NPSdataverse)
 ```
 
@@ -112,7 +112,7 @@ These tests ensure that the EML elements necessary for DataStore to properly ext
 * All dataTables listed in metadata have a unique file description ([`test_file_descript()`](../reference/test_file_descript.html))
 * Metadata contains a valid CUI code ([`test_cui_dissemination()`](../reference/test_cui_dissemination.html))
 * Metadata contains a valid license name ([`test_license()`](../reference/test_license.html))
-* Metadata contains an Intellectual Rights statement ([`test_int_rights()`](../reference/test_int_rights.html)
+* Metadata contains an Intellectual Rights statement ([`test_int_rights()`](../reference/test_int_rights.html))
 * All attributes listed in metadata have attribute definitions ([`test_attribute_defs()`](../reference/test_attribute_defs.html))
 * All attributes listed in metadata have storage types associated with them ([`test_storage_type()`](../reference/test_storage_type.html))
 * All attribute storage types are valid values ([`test_storage_type()`](../reference/test_storage_type.html))
@@ -140,4 +140,4 @@ These functions check to make sure the values and fields in the metadata file ac
 ## Data and Metadata Compliance
 These functions check the data and metadata files for compliance. Please resolve any errors before uploading your data. 
 
-* Data files do not contain any email addresses that constitute personally identifiable information (PII) ([`test_pii_data_emails()`](../reference/test_pii_data.html)
+* Data files do not contain any email addresses that constitute personally identifiable information (PII) ([`test_pii_data_emails()`](../reference/test_pii_data.html))