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

Update Gdrive_upload_methods.py to upload to proper city #38

Open
krammy19 opened this issue Aug 13, 2021 · 1 comment
Open

Update Gdrive_upload_methods.py to upload to proper city #38

krammy19 opened this issue Aug 13, 2021 · 1 comment
Assignees

Comments

@krammy19
Copy link
Collaborator

krammy19 commented Aug 13, 2021

The Gdrive_upload_methods currently uploads only to the "San Jose" folder on our Google Drive. We'd like to update it to instead take a {city} string and upload to the matching folder name.

@dntrply
Copy link
Collaborator

dntrply commented Aug 26, 2021

It is possible to find the folder by city name (rather than the hard coded 'San Jose').

However - it seems the name of the city provided when invoking the python code - example 'sanjose' in the invocation below:
Legistar_Selenium.py sanjose "This Week" "City Council - Study Session"
is not the same as the name of the city on Google Drive (where the csv is uploaded)
In this instance - the name of the city is 'San Jose'

We either need mapping code that maps the city name as used in the invocation with the city name in Google Drive; else, the name of the city in Google Drive should be the same characters as used in the invocation. For the latter approach, there should be a folder 'san jose' under the 'Cities' folder

If indeed the folders under 'Cities' should be the name of the city, then we would need a mapping function. The mapping function would need to ensure how each city is represented in Legistar. For instance, Sunnyvale seems to be registered as 'sunnyvaleca'

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