Documentation doesn't explicitly state that counter-processor doesn't collect sub-dataverses
Open
Nobody has claimed this yet.
Feature: Admin Guide
Feature: Metrics + Reports
Type: Bug
User Role: Sysadmin
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
This is minor but would help to add to documentation (up to 4.20).
The documentation for counter-processor probably should state that as-is it doesn't collect sub-dataverses or file-level DOIs. I was directed to a script (https://github.com/IQSS/dataverse/pull/6785/files) that takes care of this but I'm not sure how public that is.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the counter-processor documentation covering versions up to 4.20, then review the files changed in pull request 6785. Done means the documentation explicitly states that counter-processor does not collect sub-dataverses or file-level DOIs and clarifies whether the referenced script is publicly available.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100