New package: Datasets v0.2.5

[JuliaRegistrator]

• Registering package: Datasets
• Repository: https://github.com/awi-esc/Datasets.jl
• Created by: @perrette
• Version: v0.2.5
• Commit: 841dc4fcf3d74aeec41120ab1459dc31a29efa93
• Git reference: HEAD
• Description: Keep track of datasets used in a project

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• The registry consistency tests failed
• Repo URL does not end with /name.jl.git, where name is the package name
• I was not able to install the package (i.e. Pkg.add("Datasets") failed). See the AutoMerge logs for details.
• I was not able to load the package (i.e. import Datasets failed). See the AutoMerge logs for details.
• Package name matches existing package name DataSets up-to-case.
• Package name similar to 6 existing packages.
  1. Similar to RDatasets. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1.
  2. Similar to DataDeps. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  3. Similar to DatasetsCF. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to MDDatasets. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  5. Similar to NCDatasets. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  6. Similar to MLDatasets. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

See #132410 (comment) about the package name.

[goerz]

Closing in favor of #132412