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

Standardize development/seeding data set #557

Closed
alepbloyd opened this issue Jul 30, 2024 · 1 comment · Fixed by #563
Closed

Standardize development/seeding data set #557

alepbloyd opened this issue Jul 30, 2024 · 1 comment · Fixed by #563
Milestone

Comments

@alepbloyd
Copy link
Contributor

Standardize the development/seeded data set, goal of making the development environment more consistent for everyone.

The data should include:

  • Users
    • Admin
    • Content Admin
    • Authenticated (GW, non-admin)
  • Works
    • Visibility options
      • Public
      • Private
      • Authenticated (visible to logged in GW users)
    • With attachments
      • PDFs
      • Images (JPEG?)
      • Any other file types that we accept for deposit? I believe this is on the site somewhere.
    • Other considerations
      • Range of 'created at' times for works.
  • Collections with works added to them
  • Anything else?

We currently have this functionality spread between a few rake tasks and a seeds file. I think either option is fine, as long as we just pick which one to stick with and combine this functionality into. Because the prep_new_prod task already handles creating a new empty version, I'm thinking we could go with the seeds file option for this - open to other preferences though.

@alepbloyd alepbloyd added this to the 2.1.1 milestone Jul 30, 2024
@dolsysmith
Copy link
Contributor

dolsysmith commented Jul 30, 2024

I'd suggest creating works in different admin sets: GwEtd, GwWork.

Also, adding data to the non-required metadata fields to make sure we can test the display of those, etc.

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.

2 participants