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

Identify MVP Use Cases #32

Closed
tpendragon opened this issue Apr 21, 2017 · 2 comments
Closed

Identify MVP Use Cases #32

tpendragon opened this issue Apr 21, 2017 · 2 comments

Comments

@tpendragon
Copy link
Collaborator

tpendragon commented Apr 21, 2017

What features in an example repository which, when fulfilled, mean this is a viable pattern for Hydra (and/or Hyrax)?

Ideas I'd like feedback on:

  1. Collections
  2. Access controls
  3. File upload/download
  4. Derivative generation
    1. Storage of derivatives in any of the multiple backends.
  5. Re-ordering of membered resources
  6. Custom work types.
    1. I don't think we need to write a generator, but a set of steps to add a new one which could be programmatic.
  7. Load a pre-existing AF model from Hyrax into a Valkyrie model.
    1. This would be the ideal migration strategy - in that there's no data migration.
@tpendragon
Copy link
Collaborator Author

NOIDs are probably a use case too?

@tpendragon
Copy link
Collaborator Author

  1. Display all of "my" objects.

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

No branches or pull requests

1 participant