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 name field to Acquisition panel #185

Open
1 task
Tracked by #184
cmeyer opened this issue Apr 28, 2024 · 0 comments
Open
1 task
Tracked by #184

Add name field to Acquisition panel #185

cmeyer opened this issue Apr 28, 2024 · 0 comments
Labels
audience - user affects users effort - day a day or less impact - critical has no practical workaround and prevents regular use reach - large affects many users weekly

Comments

@cmeyer
Copy link
Collaborator

cmeyer commented Apr 28, 2024

This is part of the project to improve naming of acquisition results, which is part of a larger project to better be able organize data once it has been acquired. Currently items are named generic names like "Sequence HAADF" and multiple acquisitions result in data items with the same name, which is problematic for users.

Dialog should look something like this:

image

The acquisition name should be stored in both an acquisition object and data-item-specific metadata.

Tasks

Preview Give feedback
  1. 0 of 2
    audience - user effort - few weeks impact - critical reach - all skill - acquisition skill level - expert
@cmeyer cmeyer added audience - user affects users effort - day a day or less impact - critical has no practical workaround and prevents regular use reach - large affects many users weekly priority - very high automated priority tag labels Apr 28, 2024
@cmeyer cmeyer removed the priority - very high automated priority tag label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
audience - user affects users effort - day a day or less impact - critical has no practical workaround and prevents regular use reach - large affects many users weekly
Projects
None yet
Development

No branches or pull requests

1 participant