Compound Objects
(Difference between revisions)
m |
|||
| Line 9: | Line 9: | ||
====Sample Compound Object==== | ====Sample Compound Object==== | ||
| − | The 1936 ''[[http://dc.lib.unc.edu/u?/ncmaps,760 State Highway Map of North Carolina]]'' contains two sides, front and back | + | The 1936 ''[[http://dc.lib.unc.edu/u?/ncmaps,760 State Highway Map of North Carolina]]'' contains two sides, front and back. |
| − | + | {| | |
| + | |- | ||
| + | |map_id | ||
| + | |MC_150_1936nb | ||
| + | |} | ||
Revision as of 10:34, 19 December 2008
Main Page > Compound Objects
Compound Objects in django
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.
Sample Compound Object
The 1936 [State Highway Map of North Carolina] contains two sides, front and back.
| map_id | MC_150_1936nb |
