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

Bulk Well Documents Upload Audit #172

Open
3 tasks
fergmac opened this issue Nov 7, 2024 · 0 comments
Open
3 tasks

Bulk Well Documents Upload Audit #172

fergmac opened this issue Nov 7, 2024 · 0 comments
Labels

Comments

@fergmac
Copy link
Collaborator

fergmac commented Nov 7, 2024

Describe the task
Look into usage and document types in production for the bulk well document upload.

Email from Su following our team demo meeting on Tuesday October 29th regarding more context on how users are using the document storage in production.

"I asked around and it is likely no one is aware of the “bulk well documents upload” completed in GWELLS. We can only guess it might be done by the contractors a while ago. In our understanding, the well documents can be private or public. We are curious who did the bulk upload and what types of the documents (consultant report, pumping test report, etc.) had been bulk uploaded (as you mentioned, they were all set as private during the bulk upload) ."

further message from SO:

"The Aquifer Dashboard Team doesn't want any changes so far (please keep both public and private functions for bulk upload of well document) but they are curious:

  • who did the bulk upload of documents?

  • when?

  • and what kind of documents were uploaded as private only?

  • So far no one is aware of or remember this"

Purpose
Gain more context on use of document storage and whether we need to continue to maintain the current buckets.

Acceptance Criteria

  • first
  • second
  • third

Additional context

  • Add any other context about the task here.
  • Or here
@fergmac fergmac added the spike label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant