Oracle® Universal Content Management 10g Release 4 (10.1.4) |
![]() Contents |
![]() Index |
![]() Previous |
![]() Next |
Site Studio Designer Guide > Understanding Site Studio W... > Site Asset Storage
All files associated with a Site Studio Web site are stored and managed using Oracle Content Server. A number of custom metadata fields specific to Site Studio are used to specify where and how the files are used.
Site Studio Metadata Fields on Content Information Page of Site Asset
Site Studio uses the following metadata fields for all site-related files:
Web Site Object Type: Specifies the type of file for the Web site (for example, "Data File," Stylesheet," "Region Template," and "Placeholder Definition").
Web Sites: Lists the Web site(s) that the file is associated with. This means that the file can be used on the listed site(s), although it is not necessary. A file may be associated with multiple Web sites, which means it can be reused between sites. This makes multi-site management more efficient.
Exclude From Lists: Lists the Web site(s) for which a contributor has specified that a particular content file (a contributor data file or native document) should not display in dynamic lists on the Web site.
Web Site Section: Specifies where a content file is stored on a Web site (unless a target section is explicitly specified in the original hyperlink).
Region Definition: Specifies the region definition that a region template or content file (contributor data file or native document) is associated with. This determines how the file displays on the site and what contributors are allowed to do. A region template and content file can be associated with only one region definition, but a region definition may have many region templates and content files associated with it.
Please note that some fields are automatically set as the file is created and checked into the content server. Also, not all metadata fields are used for all site assets, since they may not be relevant. For example, the Region Definition metadata field is not used for page template, since these are not associated with region definitions.
You can change the values of these fields on the content information page of a file, but be carefully when doing that, since this may affect the way the file is used on a site.