Move the processor modules and scripts, CSS code, and template to the caesarea-data repo

[wlpotter]

These are currently housed in srophe-xQueries repo. The post processor and related scripts should be moved over, and documented clearly

Should also move the CSS for the template over, but this will require a related batch change to update the link associations in the data records

[wlpotter]

Here are the current locations, declared namespaces, and other relevant information about the xQuery modules and scripts that would need to be migrated.

XQuery modules:

• /srophe-xQueries/Caesarea-Data-Entry-Phase2/cmproc.xqm
  • namespace: http://wlpotter.github.io/ns/cmproc
  • uses http://wlpotter.github.io/ns/cm/config
  • should change all the namespaces to follow this format: https://caesarea-maritima.org/caesarea-data/ns/cmproc
• /srophe-xQueries/Caesarea-Data-Entry-Phase2/config.xqm
  • namespace: http://wlpotter.github.io/ns/cm/config

XQuery scripts (this is just the most relevant sub-set, I believe)

• /srophe-xQueries/Caesarea-Data-Entry-Phase2/testimonia-postprocessing-script.xq
  • uses config and cmproc modules
  • this is the main driver script for processing newly drafted records
• /srophe-xQueries/Caesarea-Data-Entry-Phase2/create-or-update-abstract.xq
  • useful standalone script for re-creating the record abstract from the profileDesc/creation data and tagged place names
  • uses config and cmproc modules
• /srophe-xQueries/Caesarea-Data-Entry-Phase2/update-publication-and-copyright-date-based-on-revisionDesc.xq
  • this functionality should be merged into the post-processor, in which case this script does not need to be migrated
• /srophe-xQueries/Caesarea-Data-Entry-Phase2/ingest-record-edits.xq
  • this script is not currently reliable, but will be important for the pipeline that allows editing of existing records via the CSS form. This script should work like a post-processor for existing data
• /srophe-xQueries/Caesarea-Data-Entry-Phase2/string-sort/add-testimonia-sort-value.xq
  • uses config and my own xquery sort utility module: https://github.com/wlpotter/xquery-utility-modules/blob/main/sort.xqm
  • this is a crucial script for adding string sort support for testimonia, and needs to be run separately from the post-processor
  • it should be updated to only run on work-groups when there have been changes to the testimonia in that group
  • a helpful script, in the same directory, process-testimonia-sort-value-errors.xq allows users to manually provide the correct sort order for work groups that the string sort script could not parse.

The CSS files and README.md file should be migrated as well. Migrating the CSS will require a separate issue for updating the associations in current data, and in the data template.

The README.md file should be updated to reflect current practices.