Notifications: Customer use case may need subscription model for notifications.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Christine discussed a use case for notifications that may require a subscription model:
A world-wide research team with 200+ members working iteratively on datasets. There are two teams, one is a data collector, producing new versions of datasets. The other, the researcher/analyzers, selectively uses the dataset versions depending on how much or how interesting the new versions are, based on a qualitative description of the changes and potential recommendation put in the version notes by the collectors.
Email notification is most important since the analyzers are not likely to be logging into dataverse and checking. Having the version notes or some user created message in the email is important.
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
The issue describes a notification and subscription use case but names no files, tests, or entry points. Clarify the subscription model, email behavior, and version-note requirements before identifying implementation work and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100