Overview

Library Experience provides an efficient way to store, manage, and access documents and other files within and across applications in a collaborative work environment.

Note: This software product may perform additional functionality not described within this guide. However, the licenses of this software product you have purchased do not permit use of any such additional functionality. To use any extended functionality, an additional fee must be paid.

ENOVIA Live Collaboration users can access certain details about ENOVIA objects, however, all library-related data is only available to library members through the Library Experience license.

Specific features and functions supported by Library Experience include:

• Object and Text Search. Search on standard object attributes and define advanced queries. Perform basic text searches on checked-in files. Perform full-text searches with optional full-text search engines.
• Document Versioning. Whenever a file is checked in, Library Experience creates a new version object to hold that file so you can access prior versions.
• Folders. Access all folder contents (libraries, classes, parts, and documents) you own or use.
• Electronic Signature. Authorized users can sign or approve documents and other files that would normally require a handwritten signature.
• Subscription to Object Events. Subscribe to object events and receive electronic notification when those events (revise, release, promote, delete, modify) occur for the object.
• Batch Printing. Print document files without opening them in the native application using any printers connected to the network print server. Batch printing requires AdLib.

  ENOVIA products support AdLib version 4.

• PDF Rendering. Integrate with optional rendering application to generate PDF versions of native document files. PDF rendering requires Adlib.

Libraries mirror the development process in your company. A library is the top level of your hierarchy. For example, suppose that your company manufactures connectors that share architecture, components, and so on, however, each connector has a different application. You can create a part library called Connectors to categorize all these objects. Within this part library, you can create part families for different types of connectors, such as Analog and Digital. You can create as many sub-families as you need to categorize all your connectors.

The container objects within libraries are called classes. Classes categorize the objects in a library hierarchy. Within document libraries, the classes are document families. Within part libraries, the classes are part families. Within general libraries, the classes are general classes.

Classified items are the actual objects being managed, for example, CAD drawing files, specification documentation, or other files.

These libraries are intended to manage documents and have a fixed hierarchical structure. A default document library organizes documents (such as CAD drawings) into a fixed hierarchy. This library includes the following classes of objects:

Libraries and document families are container objects used to organize information. Only documents contain files. You can also put your files into unstructured private or public folders for easy access. See Working with Folders for details on using folders.

These libraries are intended to manage parts (for example, manufactured items or design code) and have a flexible hierarchical structure.

Parts are the products developed in the manufacturing process. A part library organizes these objects into classes called part families. The hierarchy within a part library is flexible and can be customized. Your business administrator defines both the levels of classes in the hierarchy and the policy that governs the objects managed in the hierarchy.

For example, an automobile manufacturer might use a part library to organize the parts for the new Zenith line of SUVs. Under the Zenith part library, you might have part families called Rear Wheel Assembly, Front Wheel Assembly and so on. Under the front and rear wheel assembly families, you might have further subclasses called Front Tire, Front Brake Assembly, and so on. You can create as many levels of a part library hierarchy as required to describe your manufacturing process.

See Working with Parts for details on working with part libraries.

These libraries can be customized to fit the needs of your organization and have a flexible hierarchical structure.

A general library is defined by your business administrator to meet the needs of your organization. It includes custom classes and a custom policy for the objects managed in the library.

For example, suppose that your company designs microchips. You could create a custom library called Semiconductor IP that contains objects of the class IP Library. Within that library, you could create Analog and Digital class objects to manage objects in still lower levels of your design hierarchy.

See Working with General Classes for details on working with General Libraries.

The tasks you can perform in Library Experience depend on the role you are assigned. For example, if you have the Librarian role, you can create, modify, and delete objects. If you have the Library User role, you can search for and view objects.

Your role in Library Experience determines what actions you are allowed to perform. Your role is part of your profile in the database. The following roles are provided as defaults:

You should read the Application Exchange Framework User's Guide (or review the AEF Help) for details on how the user interface works, and tools such as filters, printer-friendly pages, sorting, structure navigator, export, charting, and more.

You should also read the Common Components User's Guide for help using the document features that Library Experience takes advantage of.