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

Social Media Integration #101

Open
sunnymui opened this issue Feb 21, 2020 · 0 comments
Open

Social Media Integration #101

sunnymui opened this issue Feb 21, 2020 · 0 comments

Comments

@sunnymui
Copy link
Contributor

Social media integration allows a disaster post to be automatically shared through all relevant communication channels, increasing the reach of a notification. This is especially important in a time sensitive emergency.

Feature Background

From the City of San Jose's Request for Proposals document on their disaster response challenges:

We are open to different options to improve the translation process with the City’s social media channels during emergencies. Currently during emergency events, communications get sent to bilingual staff to translate and are then copied and distributed into the City’s social media channels. The City uses Hootsuite to manage social media content, but not necessarily during these types of events due to the live and rapidly-evolving nature of the information. A solution would allow us to more effectively translate, distribute, and analyze emergency content in social media channels.

Priority Integrations

  • Hootsuite

Instead of separately maintaining all the different social media API integrations, we can focus on the Hootsuite API which is a social media dashboard/publishing platform that can publish on every social network.

We'll probably want our built in social integrations later though, so admins aren't locked into using Hootsuite as their social media management tool.

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

1 participant