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

Collections v0.2 - assets, ownership change, processing flow #16

Open
6 tasks
tzarebczan opened this issue Jun 14, 2024 · 0 comments
Open
6 tasks

Collections v0.2 - assets, ownership change, processing flow #16

tzarebczan opened this issue Jun 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@tzarebczan
Copy link
Contributor

tzarebczan commented Jun 14, 2024

  • Add asset ids to collection (related: Collections registry - use SQLite  #15).
  • Support sorting of asset ids inside a collection and registry side too (maybe not needed on reg?)
  • Support ownership change. Keep Creator so we know who originally created it if we need to, but also support returning/showing of Owner (just use process owner or a new field?)

Processing Flow

  • Profile process should be responsible for spawning a collection process - profile process should have a handler to do this (one less message to create a collection)
  • Collection should be responsible for adding itself to the registry (done via client today. Use message between collection and collection registry.
  • Updates to collections should flow from the profile (similar to how we update assets) - both for metadata + adding/removing/editing
@tzarebczan tzarebczan added the enhancement New feature or request label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant