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

Feat(FM): Listing Duplicated Files #861

Open
williamputraintan opened this issue Feb 14, 2025 · 3 comments
Open

Feat(FM): Listing Duplicated Files #861

williamputraintan opened this issue Feb 14, 2025 · 3 comments
Labels
filemanager an issue relating to the filemanager

Comments

@williamputraintan
Copy link
Member

There might be cases where files are the same but located in different locations. This could be due to a moving process or different storage tiers. Perhaps having a flag in the API to indicate only files in the best storage tier should be shown when this happens.

@williamputraintan williamputraintan added the filemanager an issue relating to the filemanager label Feb 14, 2025
@mmalenic
Copy link
Member

mmalenic commented Feb 14, 2025

If querying by portalRunId or ingestId multiple results can be returned for identical files, and I guess that's what's happening in the UI?

Also, by best, would that mean preferencing Standard or instantly retrievable classes over DeepArchive or classes that need a restore first? There is an ?isAccessible=True flag which was introduced recently with #851. Could that solve the issue?

@williamputraintan
Copy link
Member Author

It's not an issue yet, just thinking about the possibility of happening, as during moving files between buckets (copy and delete), then 2 identical files may be listed. Perhaps it is a very small window that the user just needs to refresh and duplicated files are gone. Not sure if we will have any duplicated objects between buckets again where the only difference is just the storage tier, but if it does I am just wondering if we could de-duplicate by listing the preferred tier over the other.

There were cases of duplicated filenames, but it turns out that duplication is due to the workflow having the same file in multiple directories.

Standard or instantly retrievable classes over DeepArchive or classes that need a restore first?

Yes, I think standard or Instant Retrieval is preferred.

?isAccessible=True flag

Thanks for this, the UI should make use of it.

@williamputraintan
Copy link
Member Author

I am happy to close this issue for now if it doesn't make sense as we don't have a strong use case yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filemanager an issue relating to the filemanager
Projects
None yet
Development

No branches or pull requests

2 participants