# Target Timeline

(by pavel, last updated: sep 2013)

## Kinds of timeline items

The Timeline (formerly known as History) list should show:

* internal OMA events (Activity objects)
* tweets
* RSS items
* mentions (related to a project)
* outreach CRM messages (in future)

## Initial idea

Add a drop down to the right of the history section when looking at a target that allows you to view the RSS/Twitter feed of the target. Fetch it through the browser rather than via the servers, no processing needed.

Screenshow:

<https://www.evernote.com/shard/s1/sh/3354fe90-3aed-47bd-8206-8c041136fbe4/478a8e4b92d3a42491e091cb7a17e9a7>

## Implementation details

### Realtime fetching of tweets and RSS items

The idea is that rather than store tweets and RSS items persistently (in mongo or PG), retrieve them in realtime and just cache for tens of minutes. Each time a user opens the show page for a target, the application fetches data in real-time and caches found items.

There is also an idea to not use server-side logic at all for the RSS/tweets retrieval and do it solely on the client side in a browser using JavaScript.

### RSS feed URLs

There is no information about available RSS feed endpoints in the application database at the moment. There is at least two opportunities to enhance data:

* for each existing and newly created targets try to infer RSS endpoint (if the associated entity is created using URL)
* try to infer RSS endpoint for ALL actual entities in the database


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://omalab.gitbook.io/guide/engineering-wiki/legacy-and-deprecated/target-timeline.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
