Live-Blog Chronology Sorter
Sort timestamped live-blog entries in a caller-selected chronological direction.
Description
Chronology sorting orders supplied live-blog records by their timestamps.
Chronology sorting orders supplied live-blog records by their timestamps. The text following the first pipe is preserved as part of the record.1
Sort timestamped live-blog entries in a caller-selected chronological direction.
When to use Live-Blog Chronology Sorter
Use this tool to sort timestamped live-blog entries in a caller-selected chronological direction.
Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
How to use Live-Blog Chronology Sorter and understand its results
- Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
- Enter entries, order using the field table and calculation rules, then run the tool.
- Read sortedEntries, entryCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| entries | Live-blog entries | list of string | Required |
| order | Sort order | string; one of "oldest-first", "newest-first" | Required |
Enter timestamp|text records and newest-first flag. Require a pipe and a parseable timestamp; text can be empty or include more pipes. Return original records sorted in the selected direction and count; an empty list is allowed.
order by parsed timestamp; ties preserve input order Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| sortedEntries | Sorted entries | list of string |
| entryCount | Entry count | integer; minimum: 0 |
{
"input": {
"entries": [
"2025-01-01T12:30:00Z|Update B",
"2025-01-01T12:00:00Z|Update A"
],
"order": "oldest-first"
},
"output": {
"sortedEntries": [
"2025-01-01T12:00:00Z|Update A",
"2025-01-01T12:30:00Z|Update B"
],
"entryCount": 2
}
}Limitations and assumptions
No event chronology is verified and no timestamps are corrected. Use explicit offsets for unambiguous times.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Document Entity Date Sorter: Parse compact document records, sort them by dateline, and collect unique named entities. For a complementary task, use Live-Blog Staleness: Measure live-blog update age against a supplied staleness threshold.
References
-
Live-Blog Chronology Sorter — tool.io
Similar or alternative tools
- Document Entity Date Sorter
Parse compact document records, sort them by dateline, and collect unique named entities.
- Live-Blog Staleness
Measure live-blog update age against a supplied staleness threshold.