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

Strengthen the curation communication pipeline through notifications #621

Open
1 of 3 tasks
bishwaspraveen opened this issue Feb 21, 2024 · 0 comments
Open
1 of 3 tasks
Assignees

Comments

@bishwaspraveen
Copy link
Contributor

bishwaspraveen commented Feb 21, 2024

Description

Communication in the curation process has been hard to keep up on our project. So, to solve this, there is a need to automate this communication process throughout the communication pipeline. There are three major steps to be executed :

  • When the curators decide to bring in a new collection, they explore a website and make notes about it. They bring in the notes and create a collection on the webapp with basic info about the collection. This has to be notified to the collection engineering personnel. There is a need to automate this process.
  • When the collection engineer works on the source and is done, he gets on the webapp, imports the urls into the webapp using the dev server API endpoint and at this point the curator needs to be told that the source is ready for curation. Here comes another need to automate this process.
  • When the curator is done curating, they mark the source as curated and now the source is ready to go into test. The dev team needs to be communicated about this. This is another process that can be automated.

Tasks

Preview Give feedback
  1. bishwaspraveen
  2. bishwaspraveen
@bishwaspraveen bishwaspraveen self-assigned this Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant