Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Content Layout Guide
Anatomy of a Curatescape Story
Curatescape projects differ from typical Omeka projects in that the Item record – Omeka’s central unit of content – is used to catalog a specialized Story, rather than, say, an archival photograph or document. Curatescape stories may, of course, include archival photographs and other documents (including audio, video, etc.), but – unlike in a typical Omeka project, such as a digital archive – these files are not the primary content, but rather a component of the textual story. Most often, files are used to complement the story, serving as photographic evidence, illustrating an interpretive perspective, and/or simply adding visual interest. Metadata for each file is stored in a separate File record, which exists within the larger Item record but has its own metadata record. The Story itself is stored at the Item level, with content divided into structured fields and sections within the entry form, including Dublin Core fields, custom Curatescape Story (Item Type) fields, Tags, and plugin-generated fields, such as the Map section. Below is an illustration of how each structured field is translated for display on the public webpage.