Icons indicate the type and status of objects in the repository.
| Icon | Object Type or Status | Description |
|---|---|---|
 |
Annotation Definition | An annotation definition allows you to attach comments or other information to objects in the repository. Annotations are typically used for reviewer comments. |
 |
DITA Bookmap | A bookmap is a specialization of a DITA Map. A bookmap allows you to add a frontmatter, backmatter, and other attributes to enable the content to be presented in the form of a book. |
 |
Cabinet | A cabinet contains all other repository objects except other cabinets and administrative objects. Cabinets are created by administrators. Cabinets can have access controls applied to them so that only certain users or groups can alter the cabinet properties, contents, and other characteristics. Cabinets are defined specifying a language and locale. |
 |
Custom Attribute | Custom attributes allow user-defined information to be attached to or removed from objects in the repository. Custom attribute definitions define the characteristics of the user-defined information. |
 |
DTD | A Document Type Definition (DTD) contains element definitions. Administrators specify the element definitions that are used as locking unit boundaries for checking out elements in structured documents. DITA structured documents rely on DITA-specific DTDs. |
 |
DITA Map | A DITA Map lets you organize topics that you want to build into an output web or PDF. It manages all the navigation for DITA, which allows authors to organize and manage navigation from a single structure. |
 |
Edition | An edition is a read-only copy of a structured document containing all the elements and files within or associated with that structured document at a specific date and time. You can reuse objects from an edition. |
 |
Element | An element is contained within a structured document. An element must have a corresponding element definition in the DTD that is associated with the structured document. |
 |
Element in different locking unit | In the Navigation view, an element will appear using this icon if the parent element does not reside within the same locking unit of the same document. |
 |
Element in different document | In the Navigation view, an element will appear using this icon if the parent element does not reside within the same document. |
 |
Element Definition | An element definition is contained within a DTD. Element definitions specify the elements allowed in the structured document that is associated with the DTD. Element definitions cannot be deleted directly from the repository. You can only delete them by editing and importing the DTD. |
 |
Event Queue | An event queue stores a list of event objects. Event queues receive events when interesting repository updates occur. Daemon processes, located typically on servers, can be activated to perform batch processing on incoming events arriving in an event queue. Astoria event queues can handle various tasks, such as publishing. Event queues are created only by administrators. |
 |
External File Placeholder | External file placeholder objects allow you to store an entity, such as a graphic or URL in your file system and access that entity through the repository as though it were stored there. Using external file placeholders saves space in the repository and allows you to maintain your current method of labeling, tracking, and working with graphics and other entities. |
 |
File | A file is an unstructured data type, such as a graphic, spreadsheet, or chart. When available, the icon of the file type is utilized. The icon that is displayed for your file depends upon which type of file you are viewing. |
 |
File Version | A file version is a copy of a file as it existed at a specific point in time. You supply a version name and description when you check in the file. The name defaults to the previous name and increments it by one. For example, if the original version name is Import, the first time you check in the file, the name is changed to Import.1. The second time you check in that object, the name is Import.2, and so on. |
 |
Folder | A folder is contained within a cabinet. A folder can contain repository objects including a structured document, DTD, file, and other folders. |
| Group | A group is a collection of users or other groups that is used to identify users authorized to perform particular actions. The icons shown are for the Administrators group, the Application Administrators group, and all other groups, respectively. | |
 |
Products cabinet | Top level flavored cabinet-like administrative object in the Navigation view. Contains all repository objects that are used by the Release Management feature. |
 |
Product Group folder | An optional flavored folder in the Products cabinet that contains a collection of products establishing a hierarchy. Can contain Product folders and other Product Group folders. |
 |
Product folder | Contains the assets for deliverables and supporting material, organized chronologically into release objects. |
 |
Reference | A reference contains the "address" of another repository object. The icon is that of the object to which the reference refers, with an arrow modifier in the lower right corner that is common to all references. When a user creates a shortcut, the reference appears in that user's My Shortcuts view. |
 |
Release object | A cabinet-like object in a Product folder that contains assets for a product deliverable at a specific point in time. Assets are organized into one or more cabinets within the release object, depending on their location in the baseline cabinets. |
 |
Role | A role enables flexibility and simplicity in assigning access controls. It is also used in workflow configuration. A role groups multiple capabilities into a single object that can be attached to an object and be associated with users and groups. |
 |
Search | A search is an action you can perform in the repository. You specify criteria for the search to find the objects you need. You can save that set of criteria as a repository object for reuse. Parameters can also be defined so that when the search is executed, you are prompted to specify values for the search invocation. |
| Shortcut | A shortcut is a reference residing in a special user folder. Each user has their own shortcuts folder to hold personal references. The My Shortcuts view lists the user's shortcuts. To display the referenced object, click the shortcut to open it in the Details view. The object within the shortcut can be viewed, edited, and otherwise treated as the original. Deleting a shortcut does not delete the associated repository object. If the shortcut outlives the object to which it referred, the shortcut will display with a red X. |
|
 |
Structured Document | A structured document contains an XML document instance. |
 |
Trigger | A trigger allows you to create an action that happens when a specific event in the repository occurs. Triggers generally cause events to be queued in an event queue of the same name, and the events are subsequently processed by an Astoria server. |
 |
User | A user identifies a particular person. That person has the right to access or modify the repository or particular objects in the repository according to the permissions they are granted. A user can be a member of one or more groups. |
