So far I can generate a valid plguin file that follows the EPF XML schema
(1.5). The generator takes a directory with a bunch of xhtml files (saved
in Microsoft Word) within its subdirectories.
Using the document metadata (File - Properties from within Word), the
filename or nearest folder location the generator creates appropriate
metadata for each such document for use in EPF (used fx to decide what
kind of Method Element to generate!).
Now I am starting to work on a similar approach for defining Custom
Categories (and later Configuration views) using the Word functionality of
"sub documents", so that EPF can reflect and reuse "the MS Word way" of
creating views from various external documents.
Elements in "Standard categories" can link to the Content Elements using a
simple document for each Category Element with hyperlinks referencing the
Content Elements (in the order needed). These will then also be reflected
in EPF.
All this should standardize and facilitate greatly import of external
content into the EPF proces, to avoid the manual effort currently
required, with the inherent limitations and potential for human error.
I also envision a way to check the XML import file against a similar
snapshot XML ekport file of the plugin to be exported and flag to the user
any merge conflicts (or allow "latest date" to override?). Perhaps GUI
enabled!?