[evergreen-outreach] Content Queue

[Olivia Scully]

Hello everyone - I'm new to this group, but looking forward to working with
you all! Just a super quick intro so I'm not hijacking the thread: My name
is Olivia, and I'm the Help Desk Coordinator at Bibliomation in Connecticut.

I have some experience with exactly this sort of thing, so I hope you don't
mind me diving right in here!

A content queue really does help keep everything centralized, ensure steady
flow of content, avoid duplicate efforts... I love it.

As far as tools go:

I used to use *Hootsuite* <https://www.hootsuite.com>, which is another
social media scheduler - but it also used to be free. Now it looks like
they have no free options, BUT they do offer a nonprofit discount
<https://www.hootsuite.com/about/hootgiving>!

*Canva Pro* (if that's something we have access to?) also has a social
media scheduler now, but I haven't explored it. However, I am told it's
dead simple to use and great for collaborative efforts.

In my previous job, we used *Airtable* <https://airtable.com> for
collecting, scheduling (but not automating), and tracking who did what. It
was very flexible and included comms beyond social media (e.g. email
newsletter, press releases, flyers, etc). Airtable uses a freemium model,
and also offers a nonprofit discount
<https://support.airtable.com/docs/nonprofit-and-educational-plans-faqs> for
paid plans. On the other hand, this approach may be overkill to start with.

So with all that in mind, I agree: a *Google* *Doc* (or perhaps a Google
*spreadsheet*, to keep everything organized) would be a great place to
start.

Happy to help set something up, whichever direction we go in!

Olivia



--
Olivia Scully (she/her)
Help Desk Coordinator
Bibliomation, Inc.
oscully at biblio.org
(203) 577-4070 x113

On Wed, May 3, 2023, 10:44 PM Jennifer Weston via evergreen-outreach <
evergreen-outreach at list.evergreen-ils.org> wrote:

> I love this idea!  It prevents the rush-to-get-content-published routine
> and would allow for easy reuse of content.  Keeping a schedule of published
> content would be beneficial. We could start with a Google doc and folders
> for images to test out the idea.
>
> I haven't used any Social Media Scheduling tools (apart from Tweetdeck)
> but I have heard good things about SocialBee <https://socialbee.com/>. It
> does have a subscription fee, as most would, so we may need to talk to TEP
> Board if we decide on a more formal tool in the future.
>
> Thanks,
> Jennifer
>
> ---
>
> Jennifer Weston, MLIS
>
> Senior Product and Education Specialist
>
> Equinox Open Library Initiative
>
> jennifer.weston at equinoxOLI.org <jennifer.weston at equinoxoli.org>
>
> *https://equinoxOLI.org <https://equinoxoli.org/>*
>
> phone:  877-OPEN-ILS (673-6457)
>
> direct:   770-709-5574
>
>
> On Wed, May 3, 2023 at 9:35 PM Rogan Hamby via evergreen-outreach <
> evergreen-outreach at list.evergreen-ils.org> wrote:
>
>> There is something I would like to pull us together as a hive mind for. I
>> am proposing that we start a content queue. I think this would be
>> invaluable for Kathryn doing social media and a new press release writer so
>> that they can focus on those tasks rather than pulling content from others.
>>
>> Whatever we use would need to support text and images as well as allow
>> contributions from the wider Evergreen community.  The simplest solution is
>> something like a Google Doc though additional features would be nice.  I
>> admit I am not familiar with specialized tools for this but perhaps others
>> have ideas?
>>
>>
>>
>>
>> Rogan Hamby (he/him/his), MLIS
>>
>> Data and Project Analyst
>>
>> Equinox Open Library Initiative
>>
>> rogan.hamby at equinoxOLI.org
>>
>> www.equinoxOLI.org
>>
>>
>> _______________________________________________
>> evergreen-outreach mailing list
>> evergreen-outreach at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-outreach
>>
> _______________________________________________
> evergreen-outreach mailing list
> evergreen-outreach at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-outreach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-outreach/attachments/20230503/edc5e854/attachment.htm>