Elysia Tools
Navigation
Workflow Playbook
Turn pasted or exported text into a repeatable list by defining line boundaries, normalizing whitespace, removing duplicates, filtering entries, and choosing an explicit order.
Hubs
Text cleanup becomes difficult to audit when the original paste disappears. Save the raw input first, count its lines or delimited parts, and write down the intended output: a compact list, a sectioned document, or a list ready for import. A line that is empty, padded, or differently cased is not automatically disposable; its meaning comes from the destination.
For a normal compact list, split the input, normalize repeated spaces and tabs, trim line edges, and remove blank rows. If blank rows separate groups, keep them or produce a second compact copy instead of destroying the structure. After that, run global deduplication with keep-first. Decide case sensitivity before the run: lowercasing for comparison can identify Alpha and alpha as duplicates, but it should not be confused with rewriting the displayed value.
Apply the filter after cleanup so the pattern sees the representation that will be delivered. Use a saved pattern or regex, decide whether empty rows may match, and check the filtered count. If source order represents priority, chronology, or editorial ranking, stop here and deliver the filtered order. Otherwise sort with text-basic-sorter using alphabetical, numerical, or length mode. Keep sorting non-random and record the direction; do not enable a second, hidden deduplication or trim pass.
Unexpectedly missing entries usually come from case-insensitive matching, trimming that changed the comparison key, a filter pattern that was too broad, or a blank-line option that removed section markers. Unexpected reordering usually comes from sorting when the source order mattered. Compare the raw and final line counts, inspect the first retained copy of each duplicate group, and repeat the run with the same saved options before accepting the list.
Workflow playbook
Run text-splitter in line mode for ordinary pasted lists or choose a custom delimiter for packed entries. Keep the raw source and note the resulting line or part count; use preserveEmpty only when empty positions are meaningful.
Use whitespace-normalizer to convert repeated spaces or tabs and trim line edges when those changes are allowed. Then use text-empty-lines-remover for a compact list, or retain a separate structured version when blank lines mark sections.
Use advanced-duplicate-line-remover with global detection and keep-first. Set caseSensitive according to the data contract; after normalization, leave trimLines off if the displayed line itself must be preserved, and keep the removal statistics for review.
Use text-line-filter with a contains, exact, prefix, suffix, regex, format, or not-empty rule. Set case sensitivity and empty-line matching deliberately, and save the pattern so another run cannot silently select a different subset.
Use text-splitter with line mode for one-item-per-line input. Use a custom delimiter for comma-, semicolon-, or marker-separated input, and keep empty parts only when their positions represent real sections or fields.
Use whitespace-normalizer to convert repeated spaces or tabs and trim line edges when those differences are noise. Use text-empty-lines-remover only for compact output; preserve or separately archive blank lines when they divide sections.
Use advanced-duplicate-line-remover in global mode with keep-first for a stable list. Choose case-sensitive matching for identifiers where case matters, and case-insensitive matching only when capitalization is presentation noise; do not confuse similar-looking lines with exact matches.
Skip reordering when source order carries priority or chronology. Otherwise use text-basic-sorter with a recorded alphabetical, numerical, or length order, and leave random shuffle disabled because it cannot provide a reproducible result.
If order is not meaningful, use text-basic-sorter with alphabetical, numerical, or length sorting and a recorded direction. Keep removeDuplicates and trimLines off because those policies were already decided; do not use shuffle. If source order matters, retain the filtered output instead.