dscpsyl / ucsb-ivcrc-treasury-funding-request-tool Goto Github PK

0.0 0.0 0.0 556 KB

An internal CLI written in Python for the treasurer of UCSB AS IVCRC to help with workflow and automation that complies with UCSB AS Legal Code.

License: GNU General Public License v3.0

Python 89.57% HTML 10.43%

ucsb-ivcrc-treasury-funding-request-tool's Introduction

Hi there 👋 Please don't mind the construction. WIP.

[but also a little personlied gif]

I'm currently workign on...
I’m available for...
Ask me about...
How to reach me...
Know about my experiences...

[Connect with me icon and links]

[my tools]

ucsb-ivcrc-treasury-funding-request-tool's People

Contributors

Watchers

ucsb-ivcrc-treasury-funding-request-tool's Issues

Better CLI

Currently, the code is a botch job created over months of sporadic sessions that somehow works. We need to rewrite the code from the ground up. Before handling the internals, it is easier to deal with the CLI. Rewrite the CLI to be cleaner and with better modules for better practices and security. We also need to add user input validation. Below are some modules that could be used instead of the default logging system currently in place.

Binary file when uploading the slack

When the file extension is missing, it seems like slack thinks it is a binary file. Make sure the file extension is there before any pdf uploads to slack.

Docusign API Intergraiton

Add Docusign integration for signatures so we do not have to keep using google docs.

Refactor bot code

Currently, it is janky and in a single file but it works somehow. Refactor it to be proper

Feature Ideas After Fluxx

Currently, the committee is transitioning to a new grant management system. Below are som ideas in place that helps with automation using the old manual system. Wait until after the integration to review these ideas and see if they are still needed.

Auto-get info from the email submission form that is received after a request is sent in.
Track the budget pdf document in the database so the user does not need to input it later on.
- Idea of how to do that: Create a new field in the db with the path to the budget file. Create a hash of the file and get the first 8 characters and use this as the file name. (Because of limitations of the pypdf method being used, we need to make sure the budget is a pdf before storing it permanently.) Create a new folder in env (check if there is one, if not create it) to store these files.
Email replies for requestor interaction should be in the same thread, not separate emails. See about following the Gmail API standard to allow in-tread replies even when there are other replies outside of the program's expectations.
Auto snooze emails so that the user does not have to.

Meeting minutes download error in requisitionPre

Because we downloaded the meeting minutes in newEntry, highlighted it, and uploaded it again as a docx. It will not export as Google only support pdf exports of docs files. We might have to convert it to a docs file in newEntry before storing the file ID to fix this.

Track Budget

Should be able to input a pdf of a budget to store and reuse later

Add a tabled option

Create a tabled template to send to requestors so that we can streamline this from time to time when we need it.

ClickUp Integration

ClickUp API integration to create tasks for publicity and history when a new funding request is being made.

https://clickup.com/api/

Rewrite and Overhaul

As stated in #1, we must rewrite this application for better standards and practices. This should be completed only after everything else is settled and we are happy with how it currently works. The backend does not really affect how the application function so this is the least priority until something else comes up. Rewriting the code will also help us give better expandability in the future.