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

Grant signals in the Investments message #65

Open
beingkk opened this issue Nov 8, 2024 · 0 comments · May be fixed by #75
Open

Grant signals in the Investments message #65

beingkk opened this issue Nov 8, 2024 · 0 comments · May be fixed by #75
Assignees

Comments

@beingkk
Copy link
Contributor

beingkk commented Nov 8, 2024

We should add grants data to the Investments slack message

This is related to these features from the roadmap:

Research grants integration: Add Gateway to Research grants to the Slack message, including project title, organisations, funding amount, and start date. Note that this will also need an enrichment of topic and mission labels (we can go with keyword labelling for now - reuse it from Hansard enrichment)

Crunchbase grant funding: Add non-UKRI grants from Crunchbase as well (for UK companies)

There could be a section called "Grants" after the "New funding rounds" section where we add this information.

At the moment, the UKRI data is collected using this DAG. We could add another task to this DAG that gets executed after the collection task - the new task would compare the new and previous data and could store a table with the new projects?

Then this is the DAG that compiles the investments message. So it could pick up the new projects table up and incorporate that data into the message (+ also find other grant data from the new Crunchbase dataset).
Note that the investments message is presently coupled with the Crunchbase data collection and enrichment.

If this sounds a bit complicated, can start with Crunchbase grant funding data, and then add GtR.

For testing we should be using our discovery test Slack space, which I can share privately.

@shabrf shabrf linked a pull request Jan 29, 2025 that will close this issue
@shabrf shabrf self-assigned this Jan 29, 2025
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

Successfully merging a pull request may close this issue.

3 participants