Changes

The meat, the actual response or 'target' data generated by Umlaut. These responses are grouped by ServiceTypeValues. A given ServiceTypeValue identifies a certain type of service, like full text, or library holdings. The list of possible ServiceTypeValues in a default Umlaut installation can be found atin the relevant Umlaut distribution data file [http://umlaut.rubyforge.org/svn/trunk/db/orig_fixed_data/service_type_values.yml service_type_values.yml] The <responses> block contains 0 or more <type_group> blocks. Each type_group has a name attribute identifiying the ServiceTypeValue, also provides you with user-displayable label for this type, and tells you if all services that generate this type are complete or not: {noformat}<type_group name="abstract"><display_name>Abstract</display_name><display_name_plural>Abstracts</display_name_plural><complete>true</complete>{noformat} Each type_group will have one or more <response> blocks in it. A <response> represents an individual piece of data generated by umlaut. The trick here is that individual elements inside <response> can very between differnet service types, or even between different