Paligo provides metadata about the various types of content you have in your instance, including publications, topics, and admonitions. This metadata can be useful when you want to find out more about a component, such as a topic, and its relationship with other content in the database. For example, you can open a topic and use the metadata to find out which publications it appears in.
There are several ways to display Paligo metadata, depending on whether you want metadata for a component, publication, or folder:
-
Select a component, such as a topic or informal topic, in the Content Manager to display it in the main editor. The editor has a Metadata side panel.
-
Select the dotted menu ( ... ) for a component, such as a topic, in the Content Manager. Next, select Edit and then Open structure. The structure view has a Metadata section.
-
Select a publication in the Content Manager to open its structure view. The structure view has a Metadata section.
-
Select the dotted menu ( ... ) for a folder and then select Metadata.
For information on the possible metadata properties and values, see Paligo Metadata Properties . Note that you will only see metadata entries that are relevant to the type of content you have selected.
The Paligo metadata has many properties, and they vary depending on what type of content you are viewing. You will only see metadata properties that are relevant.
The possible entries are described in the sections below.
Universally Unique Identifier. This is a 128-bit number that Paligo uses to identify components both internally and externally.
This is the kind of component you are viewing. The main types of component are:
-
Publication
Publications have article as their root element.
-
Component
This is a general term for many types of component, including topics and informal topics.
The root element varies, depending on the type of component. For example, a topic has section as its root element and an informal topic has sidebar as its root element.
-
Admonition
This covers the various types of admonition, including note, caution, and warning.
The root element for an admonition shows the type of admonition, for example, note.
-
Fork
The component is a reused component, such as a reused topic.
The root element for a reused component varies depending on the type of reused content. For example, a reused topic will have fork as its type and section as its root element.
-
Folder
The component is a folder. It does not have a root element.
The Subtype shows that the component has a further level of categorization, such as:
-
Appendix
-
Topic
-
Cover
-
Informal topic
-
Itemizedlist
-
Simplelist
-
Step.
Your Paligo may have additional subtypes, especially if your instance has a customization.
The name of the parent component (shown when you are looking at the metadata for a reused component, so the Type is fork).
This shows any cross-references made from this component to other components. For example, it could show a cross-reference from one topic to another topic.
This shows any cross-references from other components to this component. For example, it could show a cross-reference from another topic to the currently selected topic.
This shows any publications that also use the origin of the selected fork.
The source branch of the selected component (only shown if the component is a branch).
The source branch is the branch from which the current component was created.
The branches of the selected component. These are branches made from the selected component.
The user that creates a folder or component is the "owner" by default. Only owners and administrators can control the permissions for a folder or component.
But it is possible to change the owner to another user, if needed. To find out more, see Change Component Owner.
The user that created the folder or component.
The Creator is the same as the Owner by default. But it may be different if someone has changed the Owner metadata (see Change Component Owner).
The folder that contains the currently selected content.
You can change the location to a different folder if required.
Comments
0 comments
Article is closed for comments.