diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3feeea9..4f406a3 100644 --- a/CONTRIBUTING.md +++ b/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/QCkit/). +> If you want to ask a question, we assume that you have read the available [Documentation](https://doi-nps.github.io/QCkit/). -Before you ask a question, it is best to search for existing [Issues](https://github.com/nationalparkservice/QCkit/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/QCkit/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/QCkit/issues/new/choose). +- Open an [Issue](https://github.com/doi-nps/QCkit/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/QCkit/). 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/QCkit/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-npservice.github.io/QCkit/). 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/ndoi-nps/QCkit/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) @@ -75,7 +75,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform 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/QCkit/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/QCkit/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/QCkit/) carefully and find out if the functionality is already covered, maybe by an individual configuration. -- Perform a [search](https://github.com/nationalparkservice/QCkit/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/QCkit/) carefully and find out if the functionality is already covered, maybe by an individual configuration. +- Perform a [search](https://github.com/doi-nps/QCkit/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/QCkit/issues). +Enhancement suggestions are tracked as [GitHub issues](https://github.com/doi-nps/QCkit/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. diff --git a/DESCRIPTION b/DESCRIPTION index ed43a27..2ce7372 100644 --- a/DESCRIPTION +++ b/DESCRIPTION @@ -13,9 +13,6 @@ Authors@R: c( email = "judd_patterson@nps.gov", role = "aut", comment = c(ORCID = "0000-0002-0951-7917")), - person(given = "Joe", - family = "DeVivo", - role = "aut"), person(given = "Issac", family = "Quevedo", role = "aut", @@ -73,7 +70,7 @@ Suggests: wk, tidyr VignetteBuilder: knitr -URL: https://github.com/nationalparkservice/QCkit/, https://nationalparkservice.github.io/QCkit/ -BugReports: https://nationalparkservice.github.io/QCkit/ +URL: https://github.com/doi-nps/QCkit/, https://doi-nps.github.io/QCkit/ +BugReports: https://doi-nps.github.io/QCkit/ Config/testthat/edition: 3 Roxygen: list(markdown = TRUE) diff --git a/NEWS.md b/NEWS.md index 5882a1f..b23f650 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,4 +1,7 @@ # QCkit v1.2.1 +## 2026-04-22 + * Update URLs and documentation; add code.json file inpreparation for DGEC migration. + ## 2026-02-26 * update `get_elevation` to handle unpredictable API responses for invalid lat/long values. * update unit tests to pass using DataStore v8 API diff --git a/README.Rmd b/README.Rmd index 6e741a2..e3b9666 100644 --- a/README.Rmd +++ b/README.Rmd @@ -14,8 +14,8 @@ knitr::opts_chunk$set( ``` [![Lifecycle: experimental](https://img.shields.io/badge/lifecycle-experimental-orange.svg)](https://www.tidyverse.org/lifecycle/#experimental) -[![CodeFactor](https://www.codefactor.io/repository/github/roblbaker/qckit/badge)](https://www.codefactor.io/repository/github/roblbaker/qckit) -[![R-CMD-check](https://github.com/nationalparkservice/QCkit/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/nationalparkservice/QCkit/actions/workflows/R-CMD-check.yaml) +[![CodeFactor](https://www.codefactor.io/repository/github/rdoi-nps/qckit/badge)](https://www.codefactor.io/repository/github/doi-nps/qckit) +[![R-CMD-check](https://github.com/doi-nps/QCkit/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/doi-nps/QCkit/actions/workflows/R-CMD-check.yaml) # QCkit @@ -26,21 +26,21 @@ Functions are typically user generated and so may not have been thoroughly teste If you would like to contribute useful functions please initiate a pull request. -Please request enhancements and bug fixes through [Issues](https://github.com/nationalparkservice/QCkit/issues). +Please request enhancements and bug fixes through [Issues](https://github.com/doi-nps/QCkit/issues). # Installation Stand-alone installation: ``` r -# install.packages("devtools") -devtools::install_github("nationalparkservice/QCkit") +# install.packages("remotes") +remotes::install_github("doi-nps/QCkit") library(QCkit) ``` -QCkit is also part of the [NPSdataverse](https://nationalparkservice.github.io/NPSdataverse/) and can be installed along with the other components of NPSdataverse: +QCkit is also part of the [NPSdataverse](https://doi-nps.github.io/NPSdataverse/) and can be installed along with the other components of NPSdataverse: ```r -# install.packages("devtools") -devtools::install_github("nationalparkservice/NPSdataverse") +# install.packages("remotes") +remotes::install_github("doi-nps/NPSdataverse") library(NPSdataverse) ``` diff --git a/README.md b/README.md index b665053..2485326 100644 --- a/README.md +++ b/README.md @@ -4,8 +4,8 @@ [![Lifecycle: experimental](https://img.shields.io/badge/lifecycle-experimental-orange.svg)](https://www.tidyverse.org/lifecycle/#experimental) -[![CodeFactor](https://www.codefactor.io/repository/github/roblbaker/qckit/badge)](https://www.codefactor.io/repository/github/roblbaker/qckit) -[![R-CMD-check](https://github.com/nationalparkservice/QCkit/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/nationalparkservice/QCkit/actions/workflows/R-CMD-check.yaml) +[![CodeFactor](https://www.codefactor.io/repository/github/doi-nps/qckit/badge)](https://www.codefactor.io/repository/github/doi-nps/qckit) +[![R-CMD-check](https://github.com/doi-nps/QCkit/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/doi-nps/QCkit/actions/workflows/R-CMD-check.yaml) # QCkit @@ -25,24 +25,24 @@ If you would like to contribute useful functions please initiate a pull request. Please request enhancements and bug fixes through -[Issues](https://github.com/nationalparkservice/QCkit/issues). +[Issues](https://github.com/doi-nps/QCkit/issues). # Installation Stand-alone installation: ``` r -# install.packages("devtools") -devtools::install_github("nationalparkservice/QCkit") +# install.packages("remotes") +remotes::install_github("doi-nps/QCkit") library(QCkit) ``` QCkit is also part of the -[NPSdataverse](https://nationalparkservice.github.io/NPSdataverse/) and +[NPSdataverse](https://doi-nps.github.io/NPSdataverse/) and can be installed along with the other components of NPSdataverse: ``` r -# install.packages("devtools") -devtools::install_github("nationalparkservice/NPSdataverse") +# install.packages("remotes") +remotes::install_github("doi-nps/NPSdataverse") library(NPSdataverse) ``` diff --git a/_pkgdown.yml b/_pkgdown.yml index 7e96239..6e47a7f 100644 --- a/_pkgdown.yml +++ b/_pkgdown.yml @@ -1,4 +1,4 @@ -url: https://nationalparkservice.github.io/QCkit/ +url: https://doi-nps.github.io/QCkit/ template: bootstrap: 5 diff --git a/code.json b/code.json new file mode 100644 index 0000000..041231c --- /dev/null +++ b/code.json @@ -0,0 +1,46 @@ +[ + { + "name": "QCkit", + "organization": "NATIONAL PARK SERVICE", + "description": "NPS Inventory and Monitoring Quality Control Toolkit.", + "version": "1.2.0", + "status": "ongoing development", + "permissions": { + "usageType": "openSource", + "licenses": [ + { + "name": "Public Domain, CC0-1.0", + "URL": "https://github.com/DOI-NPS/QCkit" + } + ] + }, + "homepageURL": "https://github.com/DOI-NPS/QCkit", + "downloadURL": "https://github.com/DOI-NPS/QCkit", + "disclaimerURL": "hhtps://github.com/DOI-NPS/QCkit/blob/main/LICENSE", + "repositoryURL": "https://github.com/DOI-NPS/QCkit", + "vcs": "git", + "laborHours": 1, + "tags": [ + "NRSS", + "IMD", + "data-science", + "quality-control", + "r", + "rstats", + "r-package", + "darwin-core", + "data-quality", + "npsdataverse" + ], + "languages": [ + "R" + ], + "contact": { + "name": "Robert Baker", + "email": "robert_baker@nps.gov" + }, + "date": { + "metadataLastUpdated": "2026-04-22" + } + } +] diff --git a/docs/CONTRIBUTING.html b/docs/CONTRIBUTING.html index f77e2f9..858fd50 100644 --- a/docs/CONTRIBUTING.html +++ b/docs/CONTRIBUTING.html @@ -25,7 +25,7 @@
  • Changelog
    • @@ -35,7 +35,7 @@

    Contributing to CONTRIBUTING.md

    - Source: CONTRIBUTING.md + Source: CONTRIBUTING.md
    @@ -60,11 +60,11 @@

    Table of Contents

    I Have a Question

    -

    If you want to ask a question, we assume that you have read the available Documentation.

    +

    If you want to ask a question, we assume that you have read the available Documentation.

    -

    Before you ask a question, it is best to search for existing 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 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.
      • +
      • Open an Issue.
      • Provide as much context as you can about what you’re running into.
      • Provide project and platform versions , depending on what seems relevant.

      We will then take care of the issue as soon as possible.

      @@ -81,8 +81,8 @@

      Reporting BugsBefore Submitting a Bug Report

      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. If you are looking for support, you might want to check this section).
        • -
      • 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.
        • +
      • 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. If you are looking for support, you might want to check this section).
        • +
      • 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.
      • 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)
        • @@ -97,7 +97,7 @@

        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 .

        We use GitHub issues to track bugs and errors. If you run into an issue with the project:

        -
        • Open an Issue. (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. (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 for a great run down on how to create reproducible examples.
          • Provide the information you collected in the previous section.
            • @@ -113,14 +113,14 @@

            Suggesting Enhancements

            Before Submitting an Enhancement

            • Make sure that you are using the latest version.
              • -
            • Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
              • -
            • Perform a search 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 carefully and find out if the functionality is already covered, maybe by an individual configuration.
              • +
            • Perform a search 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.

    +

    Enhancement suggestions are tracked as GitHub issues.

    diff --git a/docs/LICENSE-text.html b/docs/LICENSE-text.html index 8e98b91..9c40fa5 100644 --- a/docs/LICENSE-text.html +++ b/docs/LICENSE-text.html @@ -25,7 +25,7 @@
  • Changelog
    • @@ -46,7 +46,7 @@

    License