Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Notifications] Failed fetch jobs #1560

Closed
CGillen opened this issue Mar 18, 2021 · 1 comment · Fixed by #3189
Closed

[Notifications] Failed fetch jobs #1560

CGillen opened this issue Mar 18, 2021 · 1 comment · Fixed by #3189
Assignees
Labels
Communications Enhancement Features Issues related to building and enhancing features Notifications Issues related to communications from OD2 to patrons etc. Priority - High Issues that should be prioritized ahead of others - early timing in the project Ready for Development The issue has passed review from teams and is ready to be worked on

Comments

@CGillen
Copy link
Contributor

CGillen commented Mar 18, 2021

Descriptive summary

This run of tickets is based on the discussion in #230.

  • Failed Fetch Jobs
    • An email should be sent to the depositor of the work
    • Explore the option of digesting all of these to the head of metadeities
    • Emails should come in batches at the beginning or end of the day

When a work has controlled metadata and the URI fails to resolve, a notification is sent to depositor of the work. We want those emails to come in batches at the beginning or end of the day. Head of metadeities should get a digest of these failed fetches as well; start with daily and see if we need to back off to weekly.

Expected behavior

Failed metadata fetch errors notify depositor and digest to head of metadeities

Related work

#230

Accessibility Concerns

None

@CGillen CGillen added Notifications Issues related to communications from OD2 to patrons etc. Communications Features Issues related to building and enhancing features Ready for Development The issue has passed review from teams and is ready to be worked on labels Mar 18, 2021
@CGillen CGillen added the Priority - High Issues that should be prioritized ahead of others - early timing in the project label Aug 12, 2022
@lamtu1 lamtu1 self-assigned this Oct 24, 2024
@shieldsb shieldsb moved this to In Progress in Enhancement Workcycle 7 Dec 19, 2024
@lamtu1 lamtu1 moved this from In Progress to Ready in Enhancement Workcycle 7 Jan 8, 2025
@lamtu1 lamtu1 moved this from Ready to In Progress in Enhancement Workcycle 7 Jan 13, 2025
@lamtu1 lamtu1 moved this from In Progress to QA in Enhancement Workcycle 7 Feb 14, 2025
@lamtu1
Copy link
Contributor

lamtu1 commented Feb 14, 2025

QA: Same as ticket #1562 (Need dev to QA this)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Communications Enhancement Features Issues related to building and enhancing features Notifications Issues related to communications from OD2 to patrons etc. Priority - High Issues that should be prioritized ahead of others - early timing in the project Ready for Development The issue has passed review from teams and is ready to be worked on
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

3 participants