Compound Objects
(Difference between revisions)
| Line 17: | Line 17: | ||
|- | |- | ||
|Repository | |Repository | ||
| + | |- | ||
| + | |Title | ||
| + | |State highway system of North Carolina | ||
| + | |- | ||
| + | |date_published_numeric | ||
| + | |1936 | ||
| + | |- | ||
| + | |Date Published | ||
| + | |1936 | ||
| + | |- | ||
| + | |content_date_numeric | ||
| + | |1936 | ||
| + | |- | ||
| + | |Date Depicted | ||
| + | |1936 | ||
|North Carolina State Archives | |North Carolina State Archives | ||
|} | |} | ||
Revision as of 10:37, 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 | |
| Repository | ||
| Title | State highway system of North Carolina | |
| date_published_numeric | 1936 | |
| Date Published | 1936 | |
| content_date_numeric | 1936 | |
| Date Depicted | 1936 | North Carolina State Archives |
