Aggregator

one component of IDPSoftware

Aggregator is a collection of code and support data elements that are used to bring together EpiDoc content from the DDBDP and the HGV.

Second-generation aggregator

At present (October 2009), the only Aggregator code is legacy from the IDP1 period at King's, and it has never been made to function properly in the new server context. Moreover, some things have changed. This code now needs to be extracted, examined and modified or replaced to accommodate the following new factors:

  • New server environment
  • Rely on new mapping files output by second-generation MapMaker, plus revised HGV meta XML output by second-generation HGVCrossswalker?, as well as DDB XML and Translation XML files to produce aggregated XML
  • EpiDoc P5 as opposed to P4

For context and desired basic functionality, see TopLevelDataFlow. The basic functionality of the legacy version is outlined in this dataflow diagram:

jpg of aggregator data flow

Locations of these files and directories:

The various mapping files, and how they were created for the legacy process, are documented in the AggregatorMappingDoc.

Related Tickets

#76
sketch out and understand the mapping/aggregation process and dependencies
#99
Empty metadata divs in aggregated xml
#145
port legacy aggregator functions
#265
Aggregator should copy all revision histories
#272
Xwalking and Aggregation Tooling matrix
#327
Update Aggregation Code
#328
Add APIS EpiDoc XML to Aggregated XML
#330
Automate Map-making and Aggregation

Attachments