BEST PRACTICE: Why Localist Doesn’t Purge Data

In this article you’ll find:
  • Where do we store our data?
  • Why don’t we purge data?
  • Adding a “Past Event” Disclaimer
  • Related Articles

Where do we store our data?

Everything is hosted in the cloud and is available to you at any time. There is no limit and your platform’s performance will not be negatively effected by the amount of data being stored.

Why don’t we purge data?

Besides storage not being a factor, there are two main reasons why we don’t purge data:

  1. It creates an archive for your organization. This is helpful for admins who want to recreate event listings or users who are curious about past events.
  2. It is a huge boost for SEO.
Here’s how these things work together:  Someone searches “Clemson University 5k race” in Google. If there aren’t any future events matching that search, past events will still appear in the search results which will drive traffic to the calendar (increased SEO). Now since the past event is archived, it was picked up by the search engine allowing a user to learn that there was a “Race for the Cure 5k” in October of 2013 so there could be one the next October. Both reasons go hand in hand.
That being said, this does only apply to outside searches. If a user searches for a past event in the calendar search box next to the login links they will be met with a message stating that no events were found and with a prompt to “search past events.”

Adding a “Past Event” Disclaimer

This can be done by using your platform’s Theme Editor.

If you don’t have an active custom HTML theme:

  1. From the Admin Dashboard go to Settings > Appearance
  2. Select the +Add Theme button
  3. Enter a name and keep the Copy From set to Default and save
  4. Back on the Appearance landing page, select your new theme’s name
  5. On edit theme page you will see a list of files on the right hand side. Select the file _event_item under Shared Among Multiple Views.
  6. In between lines 46/47, add {% if event_item.is_past %}<font color= “red”>This is a past event.</font>{% endif %}
  7. Select the blue Save Changes button then hit Preview in the blue bar. Preview will take you to your calendar homepage so you can see the change.
  8. Go back to your new theme and select the file Page Shell under Events.
  9. On line 52, add {% if event.is_past %}<font color= “red”>This is a past event.</font>{% endif %}  (If you are using the Default Legacy theme, then add this code on line 88)
  10. Select the blue Save Changes button.
  11. Once you’ve confirmed that the change is correct, select Activate in the blue bar on the edit theme page. (Back on the appearance landing page you’ll see the new theme listed as active as well).

If you  do  have a custom HTML theme active:

  1. Navigate via Settings > Appearance
  2. Select the name of the theme you wish to edit.
  3. On edit theme page you will see a list of files on the right hand side. Select the file _event_item under Shared Among Multiple Views.
  4. In between lines 46/47, add {% if event_item.is_past %}<font color= “red”>This is a past event.</font>{% endif %}
  5. Select the blue Save Changes button.
  6. Next, select the file Page Shell under Events.
  7. On line 52, add {% if event.is_past %}<font color= “red”>This is a past event.</font>{% endif %}.If you are using the Default Legacy theme, then add this code on line 88.
  8. Select the blue Save Changes button.

Note: This will not change the overall theming/SILK/CSS that is already in place.  Activating this theme will only apply the new change to the file you modified, so in this case, the only thing changing will be the text added to past event listings and/or landing pages.


Related Articles