Defining content folders

Do the following to define content folders:

Go to RiSE > Page Builder > Manage content.
Select the root folder in which you want to create the new content folder.
Do one of the following:
- Go to New > Website Content Folder to create a new content folder.
- Select an existing content folder and click Edit to modify the existing content folder.

Note: You can also select an existing content folder and go to Organize > Delete to delete the content folder.

Define the following on the content folder, as necessary:
- Properties
- Workflow management
- Current tags
- Access settings

In most cases, content folders are automatically published when you click Save. However, if you define an existing content folder that contains any content records with a Working status, or if you edit a folder that contains no content records, the content folder is not automatically published. You must subsequently click Publish from the toolbar to create an active Published version. You can choose to publish the child content records at the same time, if desired.

Copying or moving content folders to another content folder

You can move content folders into different content folders by dragging and dropping them into a different folder. You can also move content folders by selecting the content folder and then using the toolbar commands Organize > Cut and Organize > Paste.

Note: You cannot drag and drop system folders or folders that have nested system documents.

Note: Content cannot be dragged from the left panel to the right panel (or within the right panel) of the Manage content section.

When you move or copy a content folder into a new content folder, you must republish the moved content folder to ensure that any content inside the folder that was moved is made visible on all iMIS content management websites associated with the new parent content folder. This also ensures the moved content folder is removed from all websites that were associated with the old parent content folder.

When you move or copy a content folder that is workflow-enabled, the content folder's assigned content authority group and content owner remains unchanged.

Tags inherited from ancestors in the content folder hierarchy are recalculated based on the content folder's new position in the hierarchy. Although the new inherited tags are visible immediately within Page Builder, you must republish all descendants of the content folder to ensure that website searches for these tags will find the folder's descendant content records.

Reverting to an earlier version of a content folder

Whenever you save or publish a content folder, the previous version of the content folder is saved as an Archived version. Do the following to revert to an older archived version:

Go to RiSE > Page Builder > Manage content.
Select a content folder.
Click Versions.
Select an archived version and click Revert and then OK.

The version you selected is turned into a new Working version at the top of the list. When you close this window, the version you selected is the version seen in the content folder hierarchy. As with any Working content folder, you can publish this version when you are ready to make it an active Published version.

Restoring or purging deleted content folders

A content folder that has been deleted is moved to the Recycle Bin at the bottom of the content folder hierarchy.

Permanently purging specific content folders

Do the following to permanently purge specific content folders:

Go to RiSE > Page Builder > Manage content > Recycle Bin.
Select the content folders you want to permanently purge in the Recycle Bin. Press Ctrl as you select content folders to select more than one folder.
Go to Organize > Purge.

Permanently purging all items in the Recycle Bin

Do the following to permanently purge all items in the Recycle Bin:

Go to RiSE > Page Builder > Manage content.
Select the Recycle Bin.
Go to Organize > Empty the Recycle Bin.

Restoring a deleted content folder

Do the following to restore a deleted content folder:

Go to RiSE > Page Builder > Manage content > Recycle Bin.
Select the deleted content folder.
Click Versions.
In the Document versions window, select the desired Recycled version.
Click Revert and then OK. The content folder is moved to its original location in the content folder hierarchy and its status is changed to Working. You must republish the content folder to create an active Published version again.

Troubleshooting

You must have one or both of the following content authority group permissions in at least one content authority group to which you belong:
- To create new content folders, you must have Folder Creator content authority group permissions. Folder creators can create new content folders, as well as edit or delete existing content folders.
- To modify the properties of a content folder, you must have Folder Editor content authority group permissions.
To create new content folders, you must have both Read and Edit Document system permissions on each content folder in which you want to create new content folders.
To edit existing content folders, you must have both Read and Edit Document system permissions on each content folder you want to edit.
To delete existing content folders, you must have Delete Document system permissions on each content folder you want to delete.

The Document system permissions from the parent content folder are copied into each newly created content folder, but can later be modified.

You must have Select Document system permissions on each content folder to which you assign tags.
To be the content owner of a content folder, you must have Content Editor content authority group permissions in the content authority group that is assigned to the content folder.

Note: The iCore content folder and all of its descendant content folders and content records are protected for use by iMIS. The default Document system permissions for these content folders and content records permit editing only by members of the SysAdmin role.

Concepts

Review the following concepts related to content folders.

Content folders

Children content records and content folders inherit the tags from their parent content folder (and therefore also the tags from all ancestor content folders), but no other attributes are inherited. However, some attributes are initially copied from the parent folder at the time of creation:

The specific Access settings from the parent folder are copied to new content records and content folders at the time of creation, which you can subsequently change as needed.
The Authority Group value from the parent folder is copied to new content folders at the time of creation, which you can subsequently change as needed.
The Owner of this content value from the parent folder is copied to new content folders at the time of creation, which you can subsequently change as needed.

Note: For content folders that have a content authority group (CAG) assigned to them, the Owner of this content value is not copied to new content records that are created inside of it. Instead, content records automatically have this value set to specify the first person who created the content record, which you can subsequently change as needed.

The Content is considered expired n days after last published value is copied to new content records and content folders at the time of creation, which you can subsequently change as needed.

Note: A content record does not have a content owner automatically assigned if it was created by a person who is a member of the SysAdmin role but who does not have Content Editor content authority group permissions in at least one content authority group.

Content layouts and content item zones

A content layout is a predefined set of content item zones within a content record. Each content item zone can contain one or more content items, and you can drag and drop content items among the zones to rearrange the position in which content is displayed in a rendered content record.

Content owners

A content owner is related to the content authority group (CAG) that is assigned to a content folder and its children content records. Content owners are specified on the Workflow management tab of the content folder or content record definition.

Only members of the content authority group assigned to a content folder who also have Content Editor permissions within that content authority group are available to be manually assigned as the content owner for the content folder or for content records within that content folder.

When you create a new content folder, it copies the currently designated content owner for the parent content folder. However, when you create a new content record, a different process is followed:

If the person who created the content record is a person with Content Editor content authority group permissions in at least one content authority group, they are automatically assigned as the content owner for the content record. You can subsequently change this value to any person from the parent folder's content authority group who has Content Editor content authority group permissions.
If the person who created the content folder does not have Content Editor content authority group permissions in any content authority group (for example, a person who is a member of the SysAdmin role) then no content owner is assigned.

The Owner of this content field serves a different function for content records and content folders:

For content records, the content owner:
- Receives email notification of pending expiration for the content record.
- Is assigned content change requests for the content record in the Content change requests assigned to you section of their iMIS content management Task list.
For content folders, the content owner specifies which member of the assigned content authority group should replace the designated content owner of any child content records if the current owner assigned to a content record becomes ineligible for any reason.

Content records, content items, and content types

A content record is an iMIS definition object, stored in the Document system, which specifies all the information needed to render a web page from an iMIS content management website. Instead of hand-coding the contents of a web page for your website, you define some basic properties and tags for the content record, choose a content layout, add various content items to the content item zones in the layout, and then define the properties for each content item. After the content record has been published to an .aspx file on the website, it is available for viewing by web browsers as a complete web page.

A content item is a web widget in the ASP.NET environment:

Choose from different types of content items to insert in the various content item zones in the content layout.
Configure each content item to populate that instance of it with the desired content.

You can easily rearrange the rendered page contents by dragging a content item to a different location within the content item zones. A standard set of system-defined content items are available in iMIS, but staff or consultants who are experienced in ASP.NET development can also easily add new content items for use when authoring content.

The standard content items supplied with iMIS content management (listed in the Content gallery) all have a corresponding content type, which tells iMIS how to create the corresponding content item within the system, how to edit the content item, how to display the content item, how to publish the content item, and so on.
New complex content items that you add to your iMIS environment are also listed in the Content gallery and must also have corresponding content types.
A special ASI-supplied ContentWebUserControl content type is used as a generic default content type for all simple content items, or for ad-hoc web user controls that have been manually added to a content record.
To see the Communities Content g
allery, you must have a COMMUNITIES license.