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.

Sign up for GitHub

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

Jump to bottom

[Dashboard] Add some text explaining where the data came from #35

Closed
Tracked by #17
xmcai2016 opened this issue Sep 15, 2023 · 2 comments
Closed
Tracked by #17

[Dashboard] Add some text explaining where the data came from #35

xmcai2016 opened this issue Sep 15, 2023 · 2 comments
Assignees
@10d9e @stephen-pl

Comments

@xmcai2016
Copy link

xmcai2016 commented Sep 15, 2023 •
edited
Loading

Add some text on https://retrievalbot-dashboard.vercel.app/ to explain that the data came from retrieval bot instances run by PL, FF, Slingshot etc.
@xmcai2016 xmcai2016 converted this from a draft issue Sep 15, 2023
@xmcai2016 xmcai2016 mentioned this issue Sep 15, 2023
Open
@10d9e 10d9e self-assigned this Sep 22, 2023
@10d9e 10d9e mentioned this issue Sep 22, 2023
Closed
@10d9e
Copy link

10d9e commented Sep 22, 2023

moved to data-preservation-programs/retrievalbot-dashboard#12

@xmcai2016
Copy link
Author

great progress @jlogelin! Let's add a few more to the list: the data came from retrieval bot instances run by PL, FF, Slingshot, Gravity Assist, New Web Group, Triton, etc.

@github-project-automation github-project-automation bot moved this from 🍇 Backlog to 🚢 Done in ActionArena Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@10d9e 10d9e

@stephen-pl stephen-pl

Labels
None yet
Projects
ActionArena
Status: 🚢 Done
Milestone
No milestone
Development

When branches are created from issues, their pull requests are automatically linked.

35-dashboard-add-some-text-explaining-where-the-data-came-from data-preservation-programs/RetrievalBot
3 participants
@10d9e @xmcai2016 @stephen-pl