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

Tutorial notebook demo database #936

Open
samuelbray32 opened this issue Apr 18, 2024 · 1 comment
Open

Tutorial notebook demo database #936

samuelbray32 opened this issue Apr 18, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@samuelbray32
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

  • When developers make changes to a tutorial notebook it sometimes requires re-running cells with updated functions, etc. to get update output displayed.
  • However, if a user in the database has deleted entries for the tutorial animal in order to re-run the tutorials, the needed database entries may be missing
  • This requires going back and r-running earlier notebooks to repopulate the tables.

Describe the solution you'd like
A shared development database that maintains just the tutorial animal(s) to make sure their entries remain available

@samuelbray32 samuelbray32 added the enhancement New feature or request label Apr 18, 2024
@CBroz1
Copy link
Member

CBroz1 commented Apr 18, 2024

Would cautious delete help? Can we restrict the deletion of tutorial entries to admin-only?

@edeno edeno added the documentation Improvements or additions to documentation label Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants