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

Data Pipeline Flexibility with Special Characters #406

Closed
andrewpapale opened this issue Oct 18, 2022 · 2 comments
Closed

Data Pipeline Flexibility with Special Characters #406

andrewpapale opened this issue Oct 18, 2022 · 2 comments

Comments

@andrewpapale
Copy link

Hi DAX Team,

I think this is a feature request, happy to code it myself with some pointers from the team. We have scan data on XNAT that contains special characters in the folder names ">". We pull this data from XNAT to our server and then we are backing it up on SharePoint, which does not allow this character in files/folders. Therefore, to achieve backup from our server, I need to rename folders with ">" on our server. No problem, then it syncs to SharePoint just fine.

However, DAX is too smart, it thinks those folders with no ">" have not been downloaded and is now re-downloading all our data so we now have two copies of our data on our server. I would basically like to know how to partial string match with DAX in order to take into account the change in character. Thank you for your time.

@baxpr
Copy link
Member

baxpr commented Nov 4, 2022

This is with Xnatdownload, yes? The download resume feature of Xnatdownload is a best-effort to save time but is not intended to be super versatile. Filtering like that would have to be implemented from the ground up, and as a practical matter I doubt we'll ever get to it ourselves.

Best I can think of for a workaround is to code up something that will tweak the filenames in the download_report.csv to match the filename changes you are making on disk. That's pretty fussy unfortunately.

@baxpr
Copy link
Member

baxpr commented Mar 14, 2023

Closing issue, "won't fix". But always open to discuss

@baxpr baxpr closed this as completed Mar 14, 2023
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

2 participants