Latest revision as of 09:56, 22 June 2009

Compound Objects in CONTENTdm

Multi-page maps, called "compound objects" in CONTENTdm, pose a structural challenge in transitioning to a new system. In the data exported from CONTENTdm, compound object metadata is listed in separate rows: one for the object metadata, and then as many rows as necessary for the page metadata. The structure of the compound object is defined in a small XML file with the extension .cpd in CONTENTdm.

Guidelines for Creating Compound Objects

All descriptive metadata should go into the object metadata record. Even if multiple pages need to be described separately, this should be done in the abstract field in teh object metadata record.

The object metadata record and the pages should have the same map_id (this is important).

There should be no image metadata in the object metadata record.

Use simple titles for pages, usually just "Page 1" and "Page 2" or "Front" and "Back".

Image metadata, including the raw_scan_filename, path, and technical metadata, should be in the page metadata record.

The image_sort_order field will define the sort order for the compound objects when the records are exported from CONTENTdm -- these should be in multiples of 10.

This is the color version of the 1936 edition of the state highway map. Shows highways coded by surface type (hard surface, gravel-topsoil, earth, and unimproved). Also shows the Blue Ridge Parkway (Under Construction) , ferries, and parks and national forests. Relief shown pictorially. The back of the map has several color illustrations and photographs, including a panorama of the Blue Ridge Parkway, and scenic shots from around the state.