You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: NEWS.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,14 @@
1
1
# DPchecker 1.1.0 (under development)
2
2
## 2025-04-23
3
3
* Remove `test_public_points()` function. DataStore previously made GPS coordinates public, even when data files were restricted-access, so this function was written to alert users of that fact. DataStore now applies the same access rules to GPS coordinates and data files, so this check is no longer needed.
4
-
* Remove dependency on `arcticdatautils` package.
5
-
4
+
6
5
# DPchecker 1.0.1
6
+
## 2025-04-16
7
+
* remove arcticdatautils as a dependency and replace functionality with equivalent functions from EMLeditor to reduce the total number of package dependencies.
8
+
9
+
## 2025-04-01
10
+
* fix bug that caused `test_datatable_urls_doi` to produce unexpected errors when checking metadata generated from ezEML.
11
+
7
12
## 2025-03-25
8
13
* fix bug that caused several functions to fail to detect certain .csv files
cli::cli_abort(c("x"="One or more data files lack URLs. Could not test whether URLs are properly formatted or correspond to the corect DOI. Use {.fn EMLeditor::set_data_urls} to add them."))
cli::cli_warn(c("!"="Metadata URL for the data table {.var {tbl_name}} is incorrectly formatted. Use {.fn EMLeditor::set_data_urls} to update the URLs."))
# Check if temporal coverage info is complete. Throw a warning if it's missing entirely and an error if it's only partially complete.
828
840
# The logic being that maybe there's a scenario where temporal coverage isn't relevant to the dataset at all, but if it has date/time info, it has to have both a start and end.
# Check if temporal coverage info is complete. Throw a warning if it's missing entirely and an error if it's only partially complete.
987
1000
# The logic being that maybe there's a scenario where temporal coverage isn't relevant to the dataset at all, but if it has date/time info, it has to have both a start and end.
0 commit comments