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

Request for easy accessibility to the reports folder located in Local Program files #3

Open
ceprecia opened this issue Jan 10, 2024 · 1 comment
Assignees

Comments

@ceprecia
Copy link

Is your feature request related to a problem? Please describe.
Currently the reports folder is only accessible through the file explorer after the program is quit. Navigating through each folder may not be intuitive for our testing administrators who are not tech savvy and may need to pull up an old report if it is not otherwise saved before closing.

Describe the solution you'd like
Our test administrators would find it helpful if there was a menu option when starting the program that redirects them to the reports folder or a within program explorer that can filter reports (i.g. client name, report number, date, etc.)

Describe alternatives you've considered
A simple redirect or shortcut to the reports folder may also be sufficient.

Thank you
Cris
UCSF NAIL Lab

@MichaelWoodc
Copy link
Collaborator

Hi Cris,

Thank you for joining the discussion and your request! This is something we've been pondering for a while. We previously had some reservations with making the reports too easy to access without a password / encryption. I believed that there would possibly be an issue with exporting encryption enabled software, as it's regulated by the EAR. However, we've been doing research, and I have been reading that much open source software is exempt from these export restrictions, and we're working on adding a button somewhere with password protection. This creates the possibility that someone could forget their password and lose all of the data, but otherwise it seems the way to go.

In any event, thank you for your input, we look forward to implementing these improvements, and in the meantime, feel free to reach out with any further suggestions, bug reports, or questions you may have.

Regards,
Michael

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