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

Add a selector for "Original-only" dandisets (along with draft-only and empty) #1909

Open
yarikoptic opened this issue Mar 27, 2024 · 2 comments
Labels
UX Affects usability of the system

Comments

@yarikoptic
Copy link
Member

As we will eventually get more of "derived" dandisets (as composition or containing derived data) it would be useful to be able to subselect them.

image

@yarikoptic yarikoptic added the UX Affects usability of the system label Mar 27, 2024
@satra
Copy link
Member

satra commented Mar 27, 2024

@yarikoptic - i think this may require a few components:

  • blob timestamp in relation to asset creation time
  • provenance in asset metadata (this is why having search + copy functionality in the service would be better than the gist i wrote).
  • eventually derivatives of data and not just copy of data (perhaps through services like dendro).

@yarikoptic
Copy link
Member Author

I thought to base it on some entry in dandiset metadata which would establish relationship isDerivedFrom from other dandisets and then we consider that one derived. On per asset level would be too tough probably

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX Affects usability of the system
Projects
None yet
Development

No branches or pull requests

2 participants