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

Local Instance should have more types of data (stars, reading log counts) #10153

Open
mekarpeles opened this issue Dec 17, 2024 · 3 comments
Open
Labels
Lead: @jimchamp Issues overseen by Jim (Front-end Lead, BookNotes) [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Response Issues which require feedback from lead Priority: 3 Issues that we can consider at our leisure. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]

Comments

@mekarpeles
Copy link
Member

mekarpeles commented Dec 17, 2024

Proposal

The desired outcome is that either the default developer instance data dump be extended to include a set of data (reading log entries, community review tags, star ratings, lists) or that a script be created that randomly generates some of this seed data, such that the default admin user on the dev instance (on the initial docker up)

Justification

Allows more community members to contribute

Today, when one launches a local developer instance, to the best of my knowledge, the database doesn't include key data like:

  • reading log entries
  • community reviews/tags
  • star ratings
  • lists
    that may make it easy for contributors to work on Open Library issues.

Breakdown

This could use/extend copydocs

Related files

Stakeholders


Instructions for Contributors

Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.

@mekarpeles mekarpeles added Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Good First Issue Easy issue. Good for newcomers. [managed] Needs: Detail Submitter needs to provide more detail for this issue to be assessed (see comments). [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Lead: @jimchamp Issues overseen by Jim (Front-end Lead, BookNotes) [managed] labels Dec 17, 2024
@phoenix7815
Copy link

Hey @mekarpeles , Can I take up this issue?

@github-actions github-actions bot added the Needs: Response Issues which require feedback from lead label Dec 18, 2024
@prasad14070
Copy link

Hello @mekarpeles , I would like to contribute in this issue can you please assign me this.

@jimchamp jimchamp removed the Good First Issue Easy issue. Good for newcomers. [managed] label Dec 22, 2024
@jimchamp
Copy link
Collaborator

jimchamp commented Dec 22, 2024

Removing Good First Issue Easy issue. Good for newcomers. [managed] until this issue is broken down. I cannot assign a contributor to this issue until I understand a bit more about what we're trying to achieve.

@mekarpeles mekarpeles removed Needs: Response Issues which require feedback from lead Needs: Detail Submitter needs to provide more detail for this issue to be assessed (see comments). [managed] labels Dec 22, 2024
@jimchamp jimchamp added the Needs: Response Issues which require feedback from lead label Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @jimchamp Issues overseen by Jim (Front-end Lead, BookNotes) [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Response Issues which require feedback from lead Priority: 3 Issues that we can consider at our leisure. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]
Projects
None yet
Development

No branches or pull requests

4 participants