Article: An article is a specific type of DCR. In the templatedata section of IW, files are organized into article, index, home etc.  To find an article already on the site, click on the article link.

Author, Editor, Administrator and Master:  All four of these terms refer to access levels within IW, not the role that the person has within the website.  For example, a website editor may only need author access for the tasks they have in Interwoven.  The higher the access level, the more things there are that can break so most IW users have either author or editor access.  When logging in to IW, be sure to set the access level correctly. 

Branch: A branch is a group of related sites controlled by the same master in IW.  For example, all of TruthMedia’s site are in one branch.  You can see the different branches in the file tree on the left side of the screen in IW.

DCR: Data content record, sometimes also referred to as a “new form”.  A DCR is the basic form that holds all of the content you want on your page.  Text, images, forms, videos etc are all entered into a DCR.  The DCR does not dictate how the page will look, it controls what will be on the page.

Deploy: This action sends files to the server so that they can be viewed outside of a specific workarea.

Deploy live: Sends the files to the live site.  They can now be viewed by the public.

Deploy on demand:  Older version of deploying, sometimes still used to deploy single pages.

Deploy to dev:  This action sends afile to the development server. (Most people refer to this in its shortened version, dev.) This means that files are viewable outside of a specific workarea, but are not live on the public site.  Each website has a corresponding dev site.  For example http://www.womentodaymagazine.com is the live site and http://dev.womentodaymagazine.com is the dev site.

Dev site:  Short for development site.  This is a version of the site that is not available to the public, but can be accessed by the entire team. 

Edition:  An edition is one copy of every file in the staging area of one site at a given time.  Each month when the new issues go up, an edition is published.  Editions are used for deployment.  They can also be used as a “roll back button”.  If a mistake has been made on a page and there is a recent version saved in an edition, then it is easy to revert back to the older version.  A new edition is not automatically deployed when it is created, it simply puts all of the files together in one place ready to be deployed.

File tree:  A listing of files and folders that shows where each file is and how it relates to the others.

Import:  Import is the action of bringing a file into IW.  It is most often used in relation to images.  An image on a person's hard drive that is to go on a website must be imported into IW first.  The import button is located in the file menu.  Note: After an image has been imported, it needs to be submitted to staging right away.  Images are not automatically submitted with the DCR.

Index:  An index is a special kind of DCR.  Instead of holding primarily a single article, indexes are formatted to hold links of multiple articles along with images, taglines etc.  An index page is still referred to as an index DCR and functions the same way as a DCR.  A home page is just a special kind of index. 

Interwoven: Interwoven is the name of the company that builds TeamSite, Workflow and other content management products.  Technically, this program is used most often in TeamSite, but most refer to it as Interwoven or IW.

Interwoven is down: This means that there is trouble accessing the server that Interwoven sits on.  It does not mean that data has been lost, it is just that no one is able to log in to the system to make changes until the server becomes available.

Locks, locked and unlocked: Any time a file is openned in a workarea, IW will put a lock on it so that no one else can work on the file while it is open.  When the file is open there is a key icon next to the file name in the workarea. Anyone else who looks at the filename will see a padlock icon.  If there is an article with a lock beside it and you want to work in it, you must contact the person working on the file to see if they can unlock it for you.  Note: when you submit a file to staging, the lock is automatically released.  If you do not submit the file, you must unlock it manually.  The unlock button is in the Actions menu.

Log in:  Each time you want to access IW, you must log in.  Follow the link to the log in page and enter your username and password and check to make sure that you access level is correctly selected.  If you try to log in with an access level below your usual level, some functionality will be lost.  If you try to log in with a higher access level, the log in will fail.  If you cannot log in, or if you log in and buttons are missing in your workarea, check your access level before calling for help.

NLTR: This refers to a specific branch used to create newsletters.

Permissions:  Permission control who has access to what in IW. Permissions affect both the access level and the ability to deploy.  If you would like to request a change in permission access, all requests must go through an IW master (Sheldon for TruthMedia).  Note: Permissions changes have far reaching effects, not all permission requests will be granted.

Preview:  Clicking on preview in a DCR allows a person to see what the page will look like in a browser.  The URL at the top of the screen is extremely long and complicated – that is because preview is only a temporary page.  Never try to use a preview URL as a link.  Links within a DCR will not function in preview mode.  To check a link, deploy the page to the dev site.  Preview can be used to see how an image or table is displaying, or to check colours or functionality.  When finished with the preview, close the window to return to the working DCR.

Publish:  See edition

Staging or Staging Area: In IW, the staging area is a separate section where completed DCRs are stored.  When working on a file, keep it in the workarea.  When the file is ready to go online, submit it to the staging area so it can be deployed.  Editions are also published out of the staging area

Submit or Submit direct:  This action sends the file to the staging area and releases the lock.  Once a file been submitted it is ready to be deployed.  (Technically there are exception to this, but this is the general rule.)

URL:  This stands for universal resource locator, this is the address of a web page.  Usually in the form of http://www.sitename.com/folder/articlename.html

Version or versioning (and submitting a version to staging):  TeamSite provides "versioning" at two levels. When an edition is published, a "snapshot" of the Staging area is made. This gives a version of the site. When a file is submitted to the Staging Area, the updated file does not not replace the old file in the TeamSite database, but is kept along side of it. Submitting files to Staging gives us individual file versioning. By correctly submitting files and publishing editions, we are able to track the history of a file or a website and if necessary, retrieve previous versions of them.

Workarea:  Each website has several workareas that hold versions of the files in the site.  Most IW users will work in the same workarea at all times.  Files in your workarea can be edited, changed, or added without affecting the live site.  All file work is done in a workarea, and then submitted to staging when complete.  The workarea gives you a place to store files that are not ready to go live yet.