Skip to content

Comparable Modules and Scripts out there #21

@davidverweij

Description

@davidverweij

Just as an exercise, I searched for comparable .csv to .docx packages on GitHub. I think their approaches might be educational to see how we fair, and if we need to adopt some approaches. Most repositories I found were little, or not at all, documented, or were clearly for personal and one-off use, a few I found interesting:

  • csv-fill-docx: a .js approach, which is heavily based on docxtemplater (or docxtpl for Python. This Docxtemplater allows something similar to our dependency on docx-mailmerge, but with custom fields in Word - more readable and editable by end-users. Possibly worth-while checking out for Python (if any exists).
  • gendoc does something similar as csv-fill-docx, and uses docxtemplater, but requires a .json file to be edited as input rather than all via the CLI. It thereby allows multiple 'batches' to be executed with different .csv and .docx files, which might increase workflow on a larger scale.
  • doc-csv, in Python, looks a tad more complicated, but adds a timestamp to the output folder - allowing multiple to exists, even when done in a batch (although it doesn't include milliseconds).
  • csv2docx has the same name, but creates the output .docx from scratch - rather than based on (mailmerge) fields. In particular, the .csv needs to be formatted in a specific way, see also their test case. This did make me think, our repo should clearly communicate the use of mailmerge field. In addition, I presume these mailmerge fields will remain to exists for a while - but it is worth noting this is another dependency - unlike docxtemplater that has their own fields using text, instead of fields (e.g. {%name})
  • csv2docx another identical named repo as ours, but using a node.js approach. Again, docxtemplater is used. Documentation on this repo is not there.

This is only the result of a quick search by me on GitHub, but I thought it is good to keep an eye on what is already done and/or can be done. For now, I'd say we are on the right track and should focus on the rigour and easy of use of our script as is, then we can explore how to go next. At the same time, I am all for making sure this software does one thing and does it well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionGeneral discussion about the repo, functionanility of the code or other topics related to this repo.documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions