Skip to Content

CMS Overview

 

 

Permissions

Because of the sensitive nature of University and College communications, only authorized users can edit content in the CMS for any site. Before using the CMS, you will need to gain access through LSA Development, Marketing and Communications (LSA DMC); contact us at lsa.web.support@umich.edu.

Users are granted authorization only for the department/unit site(s) they will work within – there will be no access to content owned by other departments. Additional permissions for advanced roles within the department/unit editing team will need to be determined after discussion with department/unit leadership and LSA DMC.

Overview

The CMS is built on powerful databases that are quite cumbersome and technical to work with directly. To provide a more friendly and intuitive work-experience, Open Text provides two user interfaces to manage web content.

Once your authorization has been granted, you can edit your website through either of the two separate interfaces:

  • The Application Console (AppConsole) AppConsole
  • In Context Editing (ICE) https://edit.lsa.umich.edu /YOURSITE.

Pointing your browser to the URL of the AppConsole or clicking on the editing icon in your ICE site will produce a log-in screen. If you have been granted permission by LSA DMC to work with the CMS, simply enter your UMROOT (not Kerberos) username and password to gain access.

 


 

General Overview Site Tab Specifics Content Tab Specifics

General Overview

The AppConsole is a rarely-used file-structure based interface that allows users access to more advanced functions of the CMS. It is also referred to as “The Back End”. The AppConsole is accessible through the URL: https://edit.lsa.umich.edu/AppConsole.

It is features several tabs (images below each numbered list):
1. Home – page shown here; clicking on this tab returns you to this view
2. My Page – customizable user interface described elsewhere in the KnowledgeBase
3. Sites – hierarchical, folder-based CMS management of the structure of your site (i.e., the navigation and templates that make up your site) reviewed below
4. Content – hierarchical, folder-based CMS management of the content of your site covered below
5. People Admin – enables users with special permissions to create and manage people content items (additional training required)
6. Workbench – advanced administrative controls for managing internal data
7. Rich Media Asset Console –  Not recommended for use. Allows you to work with Rich Media (e.g., images and video)
8. Diagnostics – special messages appear here alerting you of any errors in the system
9. Actions Menu – a series of links that enable you to create content and other things, depending on your permissions
10. TaskInbox–partofaworkflow system that is not used
11. Logout – click here to sign out of the CMS; also applies to any ICE window you have open

back to top


Site Tab Specifics

The Sites tab of the AppConsole is used mainly by site adminitrators, but can also be used by editors to create and publish content.
1. Path – lets you know where you are at in the CMS folder structure; when clicked inside, displays folder (channel) hierarchy and enables quick navigation

First Four Icons
2. Green Plus – create a new content instance anywhere in the CMS or a new Channel (folder) in the Channel you are currently browsing
3. Delete – if content is selected, clicking this button will remove the association between the content and the channel in which it resides; does not apply to channels
4. Properties – this button brings up the editing/properties form of a selected content item

Like most other applications, if an icon is grayed-out, it is not useable. To make the icons active, try selecting a channel or piece of content.

5. Move – moves either the association of the selected content to the destination channel or moves the channel itself to a new location
6. Start Workflow – part of a workflow system that is not used
7. Workflows – part of a workflow system that is not used
8. Associate – the CMS requires that all published content be associated to a corresponding channel; clicking on this button opens the “Associate” dialogue box
9. Publish – opens a dialogue box which allows you to publish content in all selected channels to your live website
10. Unpublish– removes from the live site any selected content items or channels

11. Preview – opens up the selected content to preview in context
12. Clone – create an exact replica of the selected content
13. Approve – selected content will be made ready for publishing
14. Caching Summary–for CMSWeb support use only
15. Order – sets the order of channels and sub-channels in your website’s navigation (i.e. which items appear first, second, or third)
16. Friendly URL – DO NOT USE
17. Channel List – contains the contents of the channel into which you are looking

18. Up – Clicking on this arrow will move your browser up one level in the channel hierarchy, usually the previous channel you had open
19. Name – the name of the piece of content or Channel
20. Approval – indicates the approval status of the CMS entry
21. Publishing – indicates the publishing status of the entry
    - Unpublished – not on live site
     - Published – on live site
     - Stale – changes have been made to the entry that have not yet been published
22. Type–denotes the type of content (e.g., article, image, event) described in Chapter 2.
23. Modified–when the entry was last changed
24. Modifier – uniqname of individual who last changed the entry
25. Created – when the entry was created
26. Creator – the uniqname of the individual who created the item

back to top


Content Tab Specific

The Content tab of the AppConsole bears a strong resemblance to the Sites tab; however, whereas the Sites tab shows you the hierarchy of channels in your site, the Content tab is more about organization and storage of your actual content. Much of the screen works the same way, but there are a few differences:
1. Green Plus – offers some additional selections for you to create Projects (folders in which to store and organize your content), content or static files
2. Resubmit – allows you to update static files (e.g., a .jpg image file, a Word document) with new files of the same name.

back to top

 


 

Heading 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin massa lacus, commodo et tincidunt vitae, sagittis eget nisi. Morbi tristique euismod blandit. te. 

Heading 2

In hac habitasse platea dictumst. Nam mi enim, sodales vitae rhoncus non, sodales in nibh. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. 

Heading 3

Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nam scelerisque, velit quis tincidunt gravida, turpis massa faucibus diam, ut dictum lectus mauris nec ligula.

Heading 4

Curabitur commodo libero eu neque consectetur volutpat. Mauris porta blandit augue a aliquet. Quisque aliquam nisl a sem sollicitudin euismod. Vivamus consectetur lacinia tempus. . 

Heading 5

In tristique quam sit amet nisi adipiscing condimentum. Mauris lacinia dui vel augue luctus nec sollicitudin nisl lacinia. Sed varius faucibus dolor, in pretium arcu pulvinar eu. 

Heading 6

Vivamus in velit ante. Aenean velit magna, volutpat id consequat sit amet, facilisis a nibh. Nullam imperdiet libero suscipit libero varius varius. Vestibulum id turpis mi. 

Permissions

Because of the sensitive nature of University and College communications, only authorized users can edit content in the CMS for any site. Before using the CMS, you will need to gain access through LSA Development, Marketing and Communications (LSA DMC); contact us at lsa.web.support@umich.edu.

Users are granted authorization only for the department/unit site(s) they will work within – there will be no access to content owned by other departments. Additional permissions for advanced roles within the department/unit editing team will need to be determined after discussion with department/unit leadership and LSA DMC.

Overview

The CMS is built on powerful databases that are quite cumbersome and technical to work with directly. To provide a more friendly and intuitive work-experience, Open Text provides two user interfaces to manage web content.

Once your authorization has been granted, you can edit your website through either of the two separate interfaces:

  • The Application Console (AppConsole) AppConsole
  • In Context Editing (ICE) https://edit.lsa.umich.edu /YOURSITE.

Pointing your browser to the URL of the AppConsole or clicking on the editing icon in your ICE site will produce a log-in screen. If you have been granted permission by LSA DMC to work with the CMS, simply enter your UMROOT (not Kerberos) username and password to gain access.

 


 

In Context Editing (ICE) is the graphic interface that allows you to see how the changes you are making to the CMS will look on the live site before you publish them. Most of the content editing is done through this interface with the editing icon (pencil).

It is most commonly called “Preview” or “ICE.” Your site will have its own URL similar to https://edit.lsa.umich.edu/YOURSITENAME.

Most pages will resemble some form of the template style represented here. The key to understanding how you can work on this page is in understanding what the icons do.

They're so small; let's magnify them a little bit so that we can see them a little bit.

Edit – brings up a content editing form or region configurator editing form
Remove – deletes the content item from the region configurator; content must be unpublished first and will not work as consistently as working through the region configurator itself
Publish – Updates your live website with your changes and will not work as consistently as working with the buttons a the bottom of each form
Unpublish - removes content or region configurator from your live site but leaves the content item on your ICE/preview site for editing or removal
Approve – readies the piece of content or region configurator for publishing and will not work as consistently as working with the buttons a the bottom of each form
Content or List Region – used to create content on dynamic pages or when creating a new region configurator on non-dynamic pages
Clear Region Config Cache – do not use unless instructed by LSA CMS Web support

 

Because this is a hosted program, there are relatively few requirements:

  • Browser – Internet Explorer 7 or later; Mozilla Firefox 3 or later, Safari 3 or later
  • Additional Software – the latest version of Java, which should already be on most LSAIT-maintained machines. If not, Java is available as a free download at http://www.java.com

Suggested Guidelines

  • Hardware: Machines maintained by LSAIT and are on scheduled maintenance or replacement schedules
  • Software:
    • Latest versions of Firefox or Safari browsers
    • Adobe Acrobat Pro for the production of .pdf
    • Google Apps

 

In Context Editing (ICE) is the graphic interface that allows you to see how the changes you are making to the CMS will look on the live site before you publish them. Most of the content editing is done through this interface with the editing icon (pencil).

It is most commonly called “Preview” or “ICE.” Your site will have its own URL similar to https://edit.lsa.umich.edu/YOURSITENAME.

Most pages will resemble some form of the template style represented here. The key to understanding how you can work on this page is in understanding what the icons do.

They're so small; let's magnify them a little bit so that we can see them a little bit.

Edit – brings up a content editing form or region configurator editing form
Remove – deletes the content item from the region configurator; content must be unpublished first and will not work as consistently as working through the region configurator itself
Publish – Updates your live website with your changes and will not work as consistently as working with the buttons a the bottom of each form
Unpublish - removes content or region configurator from your live site but leaves the content item on your ICE/preview site for editing or removal
Approve – readies the piece of content or region configurator for publishing and will not work as consistently as working with the buttons a the bottom of each form
Content or List Region – used to create content on dynamic pages or when creating a new region configurator on non-dynamic pages
Clear Region Config Cache – do not use unless instructed by LSA CMS Web support

 

AppConsole: see Application Console

Application Console: file-structure based interface that allows users access to more advanced functions of the CMS. It is also called “AppConsole.”

Cascading Style Sheet: A style sheet used for web pages to enforce a common look and feel without encoding raw HTML in every static file.

Channel: a means of organizing and deploying content that is displayed to users on sites. Each site has, at a minimum, a single “Home” channel which can have several subchannels.

CMS: see Content Management Services or Content Management Suite, depending on context
Content Item: a database-driven piece of content based on a Content Type Definition (CTD). Also known as an instance.

Content Management Services: a powerful solution for creating and managing content. It makes it easy deliver a consistent message through public-facing web sites. It allows content to be created once and published in multiple places to multiple audiences. It is scalable; as the number of sites and the quantity of content grows, the number of content contributors can scale with it.

Content Management Suite (CMS): the entire installed Open Text Content
Management product suite.

Content Type: a template for content entry; it defines the attributes for each type of content, based on the underlying database tables.

CSS: see Cascading Style Sheet 

Development, Marketing, & Communications: Department within LSA that provides strategic, integrated services for all College fundraising, marketing, and both postal and web communications.

DMC: see Development, Marketing, & Communications

GIF: see Graphics Interchange Format Graphics Interchange Format: a graphics format pioneered by CompuServe that has a maximum of 256 colors, interlacing, and transparency (one color can be defined as transparent, allowing the background color to be visible); one of the most common graphics formats on the World Wide Web (WWW).

HTML: see HyperText Markup Language

HTTP: see HyperText Transfer Protocol

HTTPS: see HyperText Transfer Protocol Secure

HyperText Markup Language: the underlying base language for the world wide web (WWW).

HyperText Transfer Protocol: protocol used for requesting and serving web pages.

HyperText Transfer Protocol Secure: Protocol used for requesting and serving web pages securely.

Instance: see Content Item.

Job: a collection of assets (regardless of  type) bundled together for publishing.

ICE: see In Context Editing

In Context Editing: visual interface that allows the user to see how the changes made to the CMS will look on the live site. Most of the content editing is done through this interface. It is most commonly called “Preview” or “ICE” 

Joint Photographic Experts Group: a group of photographic exports who, finding the Graphics Interchange Format (GIF) format too limiting for true quality static video, developed their own. The format provides for thousands of colors but no interlacing or transparency

JPG: see Joint Photographic Experts Group 

Literature, Science, and the Arts: the largest college at the University of Michigan

LSA: see Literature, Science, and the Arts

LSA Information Technology: the parent organization for the Research Systems Group (RSG) and the System Services Team (SST).

LSAIT: see LSA Information Technology

Portable Document Format: a standard document format, developed by Adobe Systems, portable across multiple computer platforms

PDF: see Portable Document Format

Preview: see In Context Editing

Project: a logical structure or container used to organize content items; projects can contain content items, static files, and subprojects. At a minimum the project file structure should reflect the Sites or Channel folder structure

Rich Media Services: CMS component that provides the technology to allow media editors to manage multiple formats and sizes of web assets such as images, video metadata, podcasts and Flash/RIA

RMS: see Rich Media Services

Role: a collection of capabilities assigned to groups of users

Sites: vehicle for delivering content to the users; sites contain channels, content items, and static files

Source Path: the location of the static file

SQL: see Structured Query Language

Static File: a document, such as a GIF, HTML, JPG, PDF, Word .doc, XML, or other file, under CMS control and stored in the file system

Structured Query Language: an industry-standard language for performing queries against a database.

Subchannel: A channel within another, parent channel. See channel. 

Subproject: A project within another, parent project. See project.

Uniform Resource Locator: the address of a specific Web site or file on the Internet. It cannot have spaces or certain other characters and uses forward slashes to denote different directories.

Uniqname: the unique textual identifier for a user’s account information in the computing resources at the University of Michigan.

URL: see Uniform Resource Locator

General Overview Site Tab Specifics Content Tab Specifics

General Overview

The AppConsole is a rarely-used file-structure based interface that allows users access to more advanced functions of the CMS. It is also referred to as “The Back End”. The AppConsole is accessible through the URL: https://edit.lsa.umich.edu/AppConsole.

It is features several tabs (images below each numbered list):
1. Home – page shown here; clicking on this tab returns you to this view
2. My Page – customizable user interface described elsewhere in the KnowledgeBase
3. Sites – hierarchical, folder-based CMS management of the structure of your site (i.e., the navigation and templates that make up your site) reviewed below
4. Content – hierarchical, folder-based CMS management of the content of your site covered below
5. People Admin – enables users with special permissions to create and manage people content items (additional training required)
6. Workbench – advanced administrative controls for managing internal data
7. Rich Media Asset Console –  Not recommended for use. Allows you to work with Rich Media (e.g., images and video)
8. Diagnostics – special messages appear here alerting you of any errors in the system
9. Actions Menu – a series of links that enable you to create content and other things, depending on your permissions
10. TaskInbox–partofaworkflow system that is not used
11. Logout – click here to sign out of the CMS; also applies to any ICE window you have open

back to top


Site Tab Specifics

The Sites tab of the AppConsole is used mainly by site adminitrators, but can also be used by editors to create and publish content.
1. Path – lets you know where you are at in the CMS folder structure; when clicked inside, displays folder (channel) hierarchy and enables quick navigation

First Four Icons
2. Green Plus – create a new content instance anywhere in the CMS or a new Channel (folder) in the Channel you are currently browsing
3. Delete – if content is selected, clicking this button will remove the association between the content and the channel in which it resides; does not apply to channels
4. Properties – this button brings up the editing/properties form of a selected content item

Like most other applications, if an icon is grayed-out, it is not useable. To make the icons active, try selecting a channel or piece of content.

5. Move – moves either the association of the selected content to the destination channel or moves the channel itself to a new location
6. Start Workflow – part of a workflow system that is not used
7. Workflows – part of a workflow system that is not used
8. Associate – the CMS requires that all published content be associated to a corresponding channel; clicking on this button opens the “Associate” dialogue box
9. Publish – opens a dialogue box which allows you to publish content in all selected channels to your live website
10. Unpublish– removes from the live site any selected content items or channels

11. Preview – opens up the selected content to preview in context
12. Clone – create an exact replica of the selected content
13. Approve – selected content will be made ready for publishing
14. Caching Summary–for CMSWeb support use only
15. Order – sets the order of channels and sub-channels in your website’s navigation (i.e. which items appear first, second, or third)
16. Friendly URL – DO NOT USE
17. Channel List – contains the contents of the channel into which you are looking

18. Up – Clicking on this arrow will move your browser up one level in the channel hierarchy, usually the previous channel you had open
19. Name – the name of the piece of content or Channel
20. Approval – indicates the approval status of the CMS entry
21. Publishing – indicates the publishing status of the entry
    - Unpublished – not on live site
     - Published – on live site
     - Stale – changes have been made to the entry that have not yet been published
22. Type–denotes the type of content (e.g., article, image, event) described in Chapter 2.
23. Modified–when the entry was last changed
24. Modifier – uniqname of individual who last changed the entry
25. Created – when the entry was created
26. Creator – the uniqname of the individual who created the item

back to top


Content Tab Specific

The Content tab of the AppConsole bears a strong resemblance to the Sites tab; however, whereas the Sites tab shows you the hierarchy of channels in your site, the Content tab is more about organization and storage of your actual content. Much of the screen works the same way, but there are a few differences:
1. Green Plus – offers some additional selections for you to create Projects (folders in which to store and organize your content), content or static files
2. Resubmit – allows you to update static files (e.g., a .jpg image file, a Word document) with new files of the same name.

back to top

Ephox Edit Live! Editing Toolbar

This toolbar appears in article, news, event, people, and publication content types.  Most of the functionality of this toolbar is universally familiar to individuals using word-processing programs, but there are a few extra utilities that work specifically with the CMS (VCM hyperlink, VCM image link and "window view").  

CMS sites have their own Heading styles, which are located in the drop down menu located on the far left of the toolbar. This document shows sample heading sizes and styles that you may choose from for your site.

Warnings

The toolbar is a miniature program that needs permission to run inside your browser. Whenever the toolbar appears, which is in most content types in the CMS, it will need to load. You need to grant your browser permission to always “trust” the toolbar by checking the box inside the message when it pops up and then select the "Run" button (see image below).

Menus and Toolbars

Moreso than brochures or bilboards, websites are a platform on which you can convey a dynamic message to your audience in many different ways. Knowing a little bit about each type of content may help you decide which is most appropriate to use in a particular situation.

Ephox Edit Live! Editing Toolbar

This toolbar appears in article, news, event, people, and publication content types.  Most of the functionality of this toolbar is universally familiar to individuals using word-processing programs, but there are a few extra utilities that work specifically with the CMS (VCM hyperlink, VCM image link and "window view").  

CMS sites have their own Heading styles, which are located in the drop down menu located on the far left of the toolbar. This document shows sample heading sizes and styles that you may choose from for your site.

Warnings

The toolbar is a miniature program that needs permission to run inside your browser. Whenever the toolbar appears, which is in most content types in the CMS, it will need to load. You need to grant your browser permission to always “trust” the toolbar by checking the box inside the message when it pops up and then select the "Run" button (see image below).

Menus and Toolbars

Floatee Menu Box
The Floatee Menu Box is comprised of several administrative actions and three key things you need to know:

1. Page Options – when hovered over with the mouse, activates the Page Options menu. 

2. Clear Management Cache – causes the CMS to look in the database and retrieve the most recent information; if you make a change and don’t see it, clicking on this is your best bet

3. Editing-On – lets you know that you are in editing mode; clicking on it will turn the editing icons off and allow you to see what your site would looks like on the live servers.

Because this is a hosted program, there are relatively few requirements:

  • Browser – Internet Explorer 7 or later; Mozilla Firefox 3 or later, Safari 3 or later
  • Additional Software – the latest version of Java, which should already be on most LSAIT-maintained machines. If not, Java is available as a free download at http://www.java.com

Suggested Guidelines

  • Hardware: Machines maintained by LSAIT and are on scheduled maintenance or replacement schedules
  • Software:
    • Latest versions of Firefox or Safari browsers
    • Adobe Acrobat Pro for the production of .pdf
    • Google Apps

 

Heading 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin massa lacus, commodo et tincidunt vitae, sagittis eget nisi. Morbi tristique euismod blandit. te. 

Heading 2

In hac habitasse platea dictumst. Nam mi enim, sodales vitae rhoncus non, sodales in nibh. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. 

Heading 3

Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nam scelerisque, velit quis tincidunt gravida, turpis massa faucibus diam, ut dictum lectus mauris nec ligula.

Heading 4

Curabitur commodo libero eu neque consectetur volutpat. Mauris porta blandit augue a aliquet. Quisque aliquam nisl a sem sollicitudin euismod. Vivamus consectetur lacinia tempus. . 

Heading 5

In tristique quam sit amet nisi adipiscing condimentum. Mauris lacinia dui vel augue luctus nec sollicitudin nisl lacinia. Sed varius faucibus dolor, in pretium arcu pulvinar eu. 

Heading 6

Vivamus in velit ante. Aenean velit magna, volutpat id consequat sit amet, facilisis a nibh. Nullam imperdiet libero suscipit libero varius varius. Vestibulum id turpis mi. 

Moreso than brochures or bilboards, websites are a platform on which you can convey a dynamic message to your audience in many different ways. Knowing a little bit about each type of content may help you decide which is most appropriate to use in a particular situation.

Permissions

Because of the sensitive nature of University and College communications, only authorized users can edit content in the CMS for any site. Before using the CMS, you will need to gain access through LSA Development, Marketing and Communications (LSA DMC); contact us at lsa.web.support@umich.edu.

Users are granted authorization only for the department/unit site(s) they will work within – there will be no access to content owned by other departments. Additional permissions for advanced roles within the department/unit editing team will need to be determined after discussion with department/unit leadership and LSA DMC.

Overview

The CMS is built on powerful databases that are quite cumbersome and technical to work with directly. To provide a more friendly and intuitive work-experience, Open Text provides two user interfaces to manage web content.

Once your authorization has been granted, you can edit your website through either of the two separate interfaces:

  • The Application Console (AppConsole) AppConsole
  • In Context Editing (ICE) https://edit.lsa.umich.edu /YOURSITE.

Pointing your browser to the URL of the AppConsole or clicking on the editing icon in your ICE site will produce a log-in screen. If you have been granted permission by LSA DMC to work with the CMS, simply enter your UMROOT (not Kerberos) username and password to gain access.

Because this is a hosted program, there are relatively few requirements:

  • Browser – Internet Explorer 7 or later; Mozilla Firefox 3 or later, Safari 3 or later
  • Additional Software – the latest version of Java, which should already be on most LSAIT-maintained machines. If not, Java is available as a free download at http://www.java.com

Suggested Guidelines

  • Hardware: Machines maintained by LSAIT and are on scheduled maintenance or replacement schedules
  • Software:
    • Latest versions of Firefox or Safari browsers
    • Adobe Acrobat Pro for the production of .pdf
    • Google Apps

 

Ephox Edit Live! Editing Toolbar

This toolbar appears in article, news, event, people, and publication content types.  Most of the functionality of this toolbar is universally familiar to individuals using word-processing programs, but there are a few extra utilities that work specifically with the CMS (VCM hyperlink, VCM image link and "window view").  

CMS sites have their own Heading styles, which are located in the drop down menu located on the far left of the toolbar. This document shows sample heading sizes and styles that you may choose from for your site.

Warnings

The toolbar is a miniature program that needs permission to run inside your browser. Whenever the toolbar appears, which is in most content types in the CMS, it will need to load. You need to grant your browser permission to always “trust” the toolbar by checking the box inside the message when it pops up and then select the "Run" button (see image below).

Menus and Toolbars

Floatee Menu Box
The Floatee Menu Box is comprised of several administrative actions and three key things you need to know:

1. Page Options – when hovered over with the mouse, activates the Page Options menu. 

2. Clear Management Cache – causes the CMS to look in the database and retrieve the most recent information; if you make a change and don’t see it, clicking on this is your best bet

3. Editing-On – lets you know that you are in editing mode; clicking on it will turn the editing icons off and allow you to see what your site would looks like on the live servers.

AppConsole: see Application Console

Application Console: file-structure based interface that allows users access to more advanced functions of the CMS. It is also called “AppConsole.”

Cascading Style Sheet: A style sheet used for web pages to enforce a common look and feel without encoding raw HTML in every static file.

Channel: a means of organizing and deploying content that is displayed to users on sites. Each site has, at a minimum, a single “Home” channel which can have several subchannels.

CMS: see Content Management Services or Content Management Suite, depending on context
Content Item: a database-driven piece of content based on a Content Type Definition (CTD). Also known as an instance.

Content Management Services: a powerful solution for creating and managing content. It makes it easy deliver a consistent message through public-facing web sites. It allows content to be created once and published in multiple places to multiple audiences. It is scalable; as the number of sites and the quantity of content grows, the number of content contributors can scale with it.

Content Management Suite (CMS): the entire installed Open Text Content
Management product suite.

Content Type: a template for content entry; it defines the attributes for each type of content, based on the underlying database tables.

CSS: see Cascading Style Sheet 

Development, Marketing, & Communications: Department within LSA that provides strategic, integrated services for all College fundraising, marketing, and both postal and web communications.

DMC: see Development, Marketing, & Communications

GIF: see Graphics Interchange Format Graphics Interchange Format: a graphics format pioneered by CompuServe that has a maximum of 256 colors, interlacing, and transparency (one color can be defined as transparent, allowing the background color to be visible); one of the most common graphics formats on the World Wide Web (WWW).

HTML: see HyperText Markup Language

HTTP: see HyperText Transfer Protocol

HTTPS: see HyperText Transfer Protocol Secure

HyperText Markup Language: the underlying base language for the world wide web (WWW).

HyperText Transfer Protocol: protocol used for requesting and serving web pages.

HyperText Transfer Protocol Secure: Protocol used for requesting and serving web pages securely.

Instance: see Content Item.

Job: a collection of assets (regardless of  type) bundled together for publishing.

ICE: see In Context Editing

In Context Editing: visual interface that allows the user to see how the changes made to the CMS will look on the live site. Most of the content editing is done through this interface. It is most commonly called “Preview” or “ICE” 

Joint Photographic Experts Group: a group of photographic exports who, finding the Graphics Interchange Format (GIF) format too limiting for true quality static video, developed their own. The format provides for thousands of colors but no interlacing or transparency

JPG: see Joint Photographic Experts Group 

Literature, Science, and the Arts: the largest college at the University of Michigan

LSA: see Literature, Science, and the Arts

LSA Information Technology: the parent organization for the Research Systems Group (RSG) and the System Services Team (SST).

LSAIT: see LSA Information Technology

Portable Document Format: a standard document format, developed by Adobe Systems, portable across multiple computer platforms

PDF: see Portable Document Format

Preview: see In Context Editing

Project: a logical structure or container used to organize content items; projects can contain content items, static files, and subprojects. At a minimum the project file structure should reflect the Sites or Channel folder structure

Rich Media Services: CMS component that provides the technology to allow media editors to manage multiple formats and sizes of web assets such as images, video metadata, podcasts and Flash/RIA

RMS: see Rich Media Services

Role: a collection of capabilities assigned to groups of users

Sites: vehicle for delivering content to the users; sites contain channels, content items, and static files

Source Path: the location of the static file

SQL: see Structured Query Language

Static File: a document, such as a GIF, HTML, JPG, PDF, Word .doc, XML, or other file, under CMS control and stored in the file system

Structured Query Language: an industry-standard language for performing queries against a database.

Subchannel: A channel within another, parent channel. See channel. 

Subproject: A project within another, parent project. See project.

Uniform Resource Locator: the address of a specific Web site or file on the Internet. It cannot have spaces or certain other characters and uses forward slashes to denote different directories.

Uniqname: the unique textual identifier for a user’s account information in the computing resources at the University of Michigan.

URL: see Uniform Resource Locator