Look into file path/name inconsistencies

[bella-tassone]

I have marked all possible inconsistencies in the Google Drive Mentions sheet in red. This includes places where outdated files may be used, as well as outdated paths. I'm a little reluctant to make the changes in the repositories myself without confirmation, so if someone could take a second look I'd really appreciate it!

The sheet has all the information, but repositories that may have concerns specifically include:

• fb_2020, includes files pacss_ads_080421.csv, fix_pdid.csv, party_clf_entity_fb_118m.csv and race_of_focus.csv (incorrect file paths).
• entity_linking, file fb_2020_adid.csv doesn't seem to be in drive.
• ad_level_party_classifier, uses outdated file names and paths including fb_2022/fb_2022_adid_var1.csv.gz, google_2022/google2022_adidlevel_text.csv and google_2022/google2022_adidlevel.csv.
• attack_like, uses outdated paths for files fb_2020_118m_adid_text.csv.gz, fb2020_118m_dedup_encodings.csv and fb2020_140m_dedup_encodings.csv.
• ad_tone, uses a different path for file FECIDs_onTV_thru110320.dta.

Reach out to me if there are any questions or concerns, and thank you for the help!

[atlasharry]

Hi Bella, for " ad_tone, uses a different path for file FECIDs_onTV_thru110320.dta." I think the path mentioned in the sheet "Data/2020/tv_2020/FECIDs_onTV_thru110320.dta" indicates the its path in the Google Drive. But indeed, this path is different in the code: sponsor_to_fecid <- read_dta("../data/tv_sponsor_to_fecid/FECIDs_onTV_thru110320.dta")

[a-jacewicz]

Hi Bella, I believe I've fixed the issues in the ad-level-party-classifiers repo as part of what I was doing this week! Let me know if I'm missing something/that doesn't seem correct to you.

[SebastianZimmeck]

Currently, the file paths for fb_2020 may need fixing, but this is currently not a priority because the fb_2020 repo is not part of what was promised to the NSF.

entity_linking is another 2020 repo that will not be published. So, not a priority either.

party_classifier is fixed.

attack_like will be addressed by @furkmak and @Meiqingx. Related to the issue we discussed in meeting January 18, 2024.

ad_tone is clarified.

[SebastianZimmeck]

There is nothing new here. @atlasharry and @a-jacewicz are taking care of this.

[SebastianZimmeck]

@atlasharry and @a-jacewicz is there anything left to do here? If not, can you close this issue?

[atlasharry]

I think we are all good for this issue!