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 naming and path options for compressed files #26

Open
felix-r opened this issue Feb 9, 2022 · 2 comments
Open

Add naming and path options for compressed files #26

felix-r opened this issue Feb 9, 2022 · 2 comments

Comments

@felix-r
Copy link

felix-r commented Feb 9, 2022

Currently all compressed files are output into a folder selected by the user and given unique names. After a day of measuring many samples, sorting out the files and cleaning up the folders becomes quite tedious when compressed files are output that way. It would be good if the users could have the following options to compress the data:

  • override original files and preserve folder structure
  • keep original files, preserve folder structure and create new unique file names
  • keep original files, output all files in selected folder and create new unique file names

Unique names could include the following information:

  • at least measurement number (in style M001 - M999, currently it's M1, M2, ...) + unique file hash
  • date
  • flow rate or reservoir tag
  • operator name
  • sample name
@paulmueller
Copy link
Member

How would I get the "operator name" programmatically? Is it the current user name (this might end up being e.g. "labadmin")?

@felix-r
Copy link
Author

felix-r commented Feb 9, 2022

This is not really meta data right now, I was thinking that in our naming scheme for a measurement folder, the operator name is always included: yyyymmdd_operator_project. But it should not be grabbed from there. If nobody else wants this included in DCKit, you don't need to add it.

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