Elysia Tools
Navigation
Workflow Playbook
Move structured data between XML, CSV, Excel, JSON, and text, merge compatible XML documents, extract selected paths, and verify the result before delivery.
Hubs
Treat the source format and the XML shape as a contract, not as two files that happen to look similar. Record the delimiter and header behavior for CSV, the worksheet and header row for Excel, the array or object root for JSON, and the line or delimiter rule for text. Then name the XML root element, repeated record element, field paths, attributes, encoding, and namespace URI/prefix pairs.
Use xml-path-extractor on the first conversion result. Test the root path, a repeated record path, and several known values. A namespace-qualified document needs a deliberate prefix binding; an empty XPath result is a signal to correct the context or namespace. Before xml-merger, compare the root and namespaces of every input and write down what happens to duplicate identifiers, missing fields, and conflicting values.
Use xml-to-csv or xml-to-json only after the structure is understood. Pay attention to repeated nodes, attributes, empty values, and flattening because a readable export can still lose meaning. Convert or inspect a representative output again, compare record counts and key values with the mapping contract, and keep any loss or coercion in the delivery notes.
For the sitemap branch, start with the approved canonical URL list. Generate the sitemap with sitemap-generator, then inspect its namespace, loc values, and URL count. This proves that the artifact matches the supplied list; it does not prove that every URL is reachable or indexed.
Workflow playbook
Choose the converter that matches the source, then record delimiter and headers, worksheet selection, JSON array/object shape, or text parsing rules. Set the intended XML root and record elements before accepting the first output.
Run XPath extraction on the converted XML using the declared namespace URI and prefix. Check the root, repeated record path, and at least three representative values; an empty or ambiguous path is a mapping failure, not a valid result.
Compare root elements and namespace declarations before combining files. Configure the merger for the compatible root and namespace behavior, apply the agreed duplicate and missing-field policy outside any option the tool does not express, and preserve the merged file for review.
Convert the reviewed XML to CSV or JSON with the selected record path and flattening assumptions. Check how repeated nodes, attributes, empty values, and namespaces are represented before handing the export to a downstream system.
Use the CSV or Excel converter for rows and worksheets, the JSON converter for objects or arrays, and the text converter for delimiter-based or line-oriented data. Do not infer a row or object mapping without recording it first.
If the document declares a namespace, use its URI with an explicit prefix in the path and test a known node. If the path returns no values, stop and correct the namespace or context instead of treating an empty result as success.
Choose append, replacement, rejection, or a manual review rule for duplicate keys and missing fields before merging. The root element and namespace must also be compatible; a merge output is not automatically deduplicated.
Read back representative exported values and counts, then compare them with the mapping record. If the branch produces a sitemap, generate it only from the approved canonical URL list and inspect the sitemap namespace, loc values, and count before delivery.