New features of v6.6 not available
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Dear Dataverse developers. we updated our test server to 6.6 and could not find some of the new features - like linking ORCID from user profile, or adding Version notes to published datasets. Some features seem to be partially available only.
What steps does it take to reproduce the issue?
- Update Dataverse to version 6.6 (build 1829-192cdc4). (from v. 6.5 build 1682-d9cc5eb)
- Test features expected in this release:
- Prompt for version notes during dataset publishing.
- Ability to link user profiles to ORCID.
-
When does this issue occur?
After updating the Dataverse installation to version 6.6. -
Which page(s) does it occur on?
- Dataset publishing workflow
- User profile settings
- What happens?
- "Version Notes" column appears on the published dataset page.
- However, users are never prompted to add version notes during the publishing process.
- Also, the expected feature to link user profiles to ORCID is not visible.
Other features might also be missing. We are still working through the update on our test system.
-
To whom does it occur (all users, curators, superusers)?
All users. -
What did you expect to happen?
- Users would be prompted to add version notes during dataset publishing.
- Option to link user accounts to ORCID would be available.
Which version of Dataverse are you using?
v. 6.6 build 1829-192cdc4
Any related open or closed issues to this bug report?
None known at this time. Investigation ongoing.
Screenshots:
ORCID row is missing
Notes column available, but never filled
Are you thinking about creating a pull request for this issue?
Not at this time. We are still determining whether the issue is related to the upgrade process or a bug in the release. Maybe the features have to be enabled separately?
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
Start by reproducing the upgrade from Dataverse 6.5 to 6.6 build 1829-192cdc4, then check the dataset publishing workflow and user profile settings pages mentioned in the report. Done means determining whether Version Notes and ORCID linking require configuration or identifying the release issue that prevents both features from appearing or working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100