http://epidocumentation.pbwiki.com/ authoring documentation of EpiDoc concepts, tools, and guidelines. en http://epidocumentation.pbwiki.com/feedlogo.gif http://pbwiki.com/ PBwiki 1.3.8 support@pbwiki.com http://epidocumentation.pbwiki.com/XwalkCoreWorkFlow email.hidden@example.com (Gabriel) Gabriel edited XwalkCoreWorkFlow (generated)
a stylesheet that acts upon HGV.xml (the database dump) to create epidocHGV.xml
on epigraphis epigraphic text field) field, translation)
epidocHGV.xml
(generated)
...an XML file containing the key value pairs in the form of variables needed for import into EpiDoc XML
hgvkv2epidoc.xml
(local file)
a template template defining the placement of key values into EpiDoc XML (context + variables)
kv2epidoc.xsl
(core xWalker script)
...
.sidebar_v2 { display: none; }
]]> Sun, 18 May 2008 17:45:35 +0000 mod http://epidocumentation.pbwiki.com/XwalkCoreWorkFlow email.hidden@example.com (Gabriel) Gabriel edited XwalkCoreWorkFlow (generated)
...
****hgvkv2epidoc.xml
(local file)
a template
.sidebar_v2 { display: none; }
]]> Sun, 18 May 2008 17:22:37 +0000 mod http://epidocumentation.pbwiki.com/XwalkCoreWorkFlow email.hidden@example.com (Gabriel) Gabriel edited XwalkCoreWorkFlow (generated)
a stylesheet that acts upon HGV.xml (the database dump) to create epidocHGV.xml
at this stage a runner.sh may also be generated if Transcode, CHET-C, or other processes also need to be run (e.g. on epigraphis text field)
epidocHGV.xml
(generated)
...
****
.sidebar_v2 { display: none; }
]]> Sun, 18 May 2008 17:10:12 +0000 mod http://epidocumentation.pbwiki.com/XwalkCoreWorkFlow email.hidden@example.com (Gabriel) Gabriel added XwalkCoreWorkFlow ! Crosswalker Core Tool Workflow

(See CrossWalker page for more detailed specs and files)



!!! In diagram above:

* crosswalker.xsl and kv2epidoc.xsl are the core CrossWalker scripts
* hgv2kv.xml and hgvkv2epidoc.xml are local, user-defined files (for \"hgv\" substitute name of local project/schema)
* HGV.xml is the input file
* all other files are generated by the process and therefore should not need hand-editing at any stage

!!!The elements:

# **hgv2kv.xml**
## (local file)
## defines the key value pairs (data fields or elements) that are to be exported from the source database/schema
## may include element definitions, copy or combine instructions, or XSLT 2.0 templates
# **crosswalker.xsl**
## (core xWalker script)
## a stylesheet that acts upon hgv2kv.xml and creates hgv2kv.xsl
# **hgv2kv.xsl**
## (generated)
## a stylesheet that ac]]> Sun, 18 May 2008 17:00:15 +0000 add http://epidocumentation.pbwiki.com/XwalkCoreWorkFlow email.hidden@example.com (Gabriel) Gabriel renamed hgv-crosswalker-1.jpg hgv-crosswalker.jpg ]]> Sun, 18 May 2008 16:42:36 +0000 mvf http://epidocumentation.pbwiki.com/f/hgv-crosswalker-1.jpg email.hidden@example.com (Gabriel) Gabriel uploaded hgv-crosswalker-1.jpg]]> Sun, 18 May 2008 16:42:30 +0000 upl http://epidocumentation.pbwiki.com/CrossWalker email.hidden@example.com (Gabriel) Gabriel edited CrossWalker An XSL transform interacts with the crosswalk file to produce a separate, custom XSL transformation file that can then be used to create EpiDoc documents from the database format and vice versa. Data may be replicated and combined from one or more elements in the source file to a single field (or element) in the output. Multiple source locations (indicated with XPath expressions) and hard-coded default values (if the XPath fails) may be specified. String replacements, value substitutions (for, e.g., vocabulary conversions) and user-supplied XSL transformations may be performed on the data by supplying the appropriate information in the crosswalk file.
This tool is still under preliminary development, although most features for production of CSV are fully implemented, and the December 2006 EpiDoc sprint resulted in much of the functionality for the EDR to EpiDoc process being drafted.
Hgv2EpiDocCrossWalkCrosswalker tool core workflow
HGV to EpiDoc Crosswalk
EpiDoc to CSV Cross]]> Sun, 18 May 2008 16:28:33 +0000 mod http://epidocumentation.pbwiki.com/Hgv2EpiDocCrossWalk email.hidden@example.com (Gabriel) Gabriel edited Hgv2EpiDocCrossWalk]]> Sun, 18 May 2008 16:23:11 +0000 mod http://epidocumentation.pbwiki.com/Hgv2EpiDocCrossWalk email.hidden@example.com (Gabriel) Gabriel added Hgv2EpiDocCrossWalk ! Crosswalk modules for HGV metadata to ~EpiDoc

(See also http://epidocdukepapy.pbwiki.com/HGVMetadataXSLTConverter)

* IDP project created a one-off crosswalk script in XSLT 2.0 (2008-Feb/Apr)
** Moving one record in HGV.fp8 into one ~EpiDoc XML file
** Mapping each HGV metadata record to one+ DDbDP text
* Revisited code and workflow for EDR crosswalk (2008-May) (see image below)
** Core Crosswalker code (crosswalker.xsl, kv2epidoc.xsl)
*** To upgrade from eXSLT to XSLT 2.0
*** Test and iterate, requiring...
** Local Crosswalker modules (hgv2kv.xml, hgvkv2epidoc.xml)
*** hgv2kv.xml (Key Value definitions) will contain XSLT snippets from IDP
*** hgvkv2epidoc.xml (~EpiDoc template) will largely come from HGV EpiDoc template created by JC/GB in 2008-Feb
*** ...


]]> Sun, 18 May 2008 16:22:22 +0000 add http://epidocumentation.pbwiki.com/Hgv2EpiDocCrossWalk email.hidden@example.com (Gabriel) Gabriel renamed crosswalker.jpg hgv-crosswalker.jpg ]]> Sun, 18 May 2008 16:21:25 +0000 mvf http://epidocumentation.pbwiki.com/f/crosswalker.jpg email.hidden@example.com (Gabriel) Gabriel uploaded crosswalker.jpg]]> Sun, 18 May 2008 16:21:09 +0000 upl http://epidocumentation.pbwiki.com/CrossWalker email.hidden@example.com (Gabriel) Gabriel edited CrossWalker An XSL transform interacts with the crosswalk file to produce a separate, custom XSL transformation file that can then be used to create EpiDoc documents from the database format and vice versa. Data may be replicated and combined from one or more elements in the source file to a single field (or element) in the output. Multiple source locations (indicated with XPath expressions) and hard-coded default values (if the XPath fails) may be specified. String replacements, value substitutions (for, e.g., vocabulary conversions) and user-supplied XSL transformations may be performed on the data by supplying the appropriate information in the crosswalk file.
This tool is still under preliminary development, although most features for production of CSV are fully implemented, and the December 2006 EpiDoc sprint resulted in much of the functionality for the EDR to EpiDoc process being drafted.
Hgv2EpiDocCrossWalk
EpiDoc to CSV Crosswalk
EDR Crosswalk Workflow
]]> Sun, 18 May 2008 15:59:22 +0000 mod http://epidocumentation.pbwiki.com/EdrXwalkWorkflow email.hidden@example.com (GB) GB edited EdrXwalkWorkflow You should now have a collection of EpiDoc documents (one per inscription) in the current folder.
NOTE: the kv2epidoc.xsl file uses XSLT Extensions which are only compatible with the the libxslt processor xsltproc. Specifically the function that allows multiple output documents works only in xsltproc.
(Diagram below sketched in 2008-MAY)
]]> Fri, 16 May 2008 23:00:45 +0000 mod http://epidocumentation.pbwiki.com/EdrXwalkWorkflow email.hidden@example.com (Anonymous) Anonymous edited EdrXwalkWorkflow]]> Fri, 16 May 2008 22:58:27 +0000 mod http://epidocumentation.pbwiki.com/f/edr-crosswalker.jpg email.hidden@example.com (Anonymous) Anonymous uploaded edr-crosswalker.jpg]]> Fri, 16 May 2008 22:55:41 +0000 upl http://epidocumentation.pbwiki.com/UpdatingTheDevDTDOnline email.hidden@example.com (Tom Elliott) Tom Elliott added UpdatingTheDevDTDOnline * cd to the dtd directory under your svn checkout

$ scp tei-epidoc.dtd {username}@{devmachine}:tei-epidoc.dtd
$ ssh {username}@{devmachine}
$ cp tei-epidoc.dtd /var/www/html/epidoc/dtd/dev/
]]> Wed, 30 Apr 2008 21:42:22 +0000 add http://epidocumentation.pbwiki.com/AdminHowTos email.hidden@example.com (Tom Elliott) Tom Elliott edited AdminHowTos BackingUpCVS
BackingUpSVN
GeneratingStaticGuidelinesGeneratingStaticGuidelines (also how to update the online copy)
UpdatingTheDevDTDOnline
UpdatingTheWebPage
]]> Wed, 30 Apr 2008 21:41:00 +0000 mod http://epidocumentation.pbwiki.com/GeneratingStaticGuidelines email.hidden@example.com (Tom Elliott) Tom Elliott edited GeneratingStaticGuidelines customize a copy of staticgl.sh.example to reflect realities on your local filesystem, rename it staticgl.sh, put it somewhere in your PATH and make it executeable
customize a copy of config.xml.example to reflect realities on your local filesystem, rename it config.xml and save it into the same directory as the static generation code (i.e., staticgen)
{username}@{devserver}:gl.zip$ ssh {username}@{devserver}$ unzip gl.zip -d /var/www/html/epidoc/gl/dev/
]]> Wed, 30 Apr 2008 21:35:42 +0000 mod http://epidocumentation.pbwiki.com/GeneratingStaticGuidelines email.hidden@example.com (Tom Elliott) Tom Elliott added GeneratingStaticGuidelines Generating Static EpiDoc Guidelines

* cd into the staticgen subdirectory under guidelines in your svn checkout tree
* customize a copy of staticgl.sh.example to reflect realities on your local filesystem, rename it staticgl.sh, put it somewhere in your PATH and make it executeable
* customize a copy of config.xml.example to reflect realities on your local filesystem, rename it config.xml and save it into the same directory as the static generation code (i.e., staticgen)

$ staticgl.sh
$ cd {output-dir-from-shell-script}
$ zip gl.zip *
$ scp gl.zip {username}@{devserver}:gl.zip
$ unzip gl.zip -d /var/www/html/epidoc/gl/dev/
]]> Wed, 30 Apr 2008 21:18:58 +0000 add http://epidocumentation.pbwiki.com/AdminHowTos email.hidden@example.com (Tom Elliott) Tom Elliott edited AdminHowTos BackingUpCVS
BackingUpSVN
GeneratingStaticGuidelines
UpdatingTheWebPage
]]> Wed, 30 Apr 2008 20:47:24 +0000 mod