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

Resolve case of shared file use in multiple Dandisets #995

Open
samuelbray32 opened this issue Jun 3, 2024 · 1 comment
Open

Resolve case of shared file use in multiple Dandisets #995

samuelbray32 opened this issue Jun 3, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request infrastructure Unix, MySQL, etc. settings/issues impacting users

Comments

@samuelbray32
Copy link
Collaborator

  • Currently, the dandi export process creates a unique Dandi upload for each raw and analysis file in its dataset. (see Dandi export and read #956)
  • This would create redundant entries in the Dandi database if files are re-used between projects.

Potential fixes:

  • Investigate dandi methods for linking to files between dandisets
  • If not, redundant uploads are required. Resolve DandiPath.fetch_file_from_dandi() case where multiple versions of the file are present
@samuelbray32 samuelbray32 added enhancement New feature or request infrastructure Unix, MySQL, etc. settings/issues impacting users labels Jun 3, 2024
@samuelbray32 samuelbray32 self-assigned this Jun 3, 2024
@samuelbray32
Copy link
Collaborator Author

Notes:

  • The DandiPath table can have multiple entries with the same filename secondary key. would not create error on our end
  • Dandi might have issue uploading a file with same object id as one on their server
  • Instead, could copy the dandi information for that file to the new export key in DandiPath

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request infrastructure Unix, MySQL, etc. settings/issues impacting users
Projects
None yet
Development

No branches or pull requests

1 participant