Creating a New Library
A Windchill library provides the context under which you can store and provide access to business information. For example, all documents owned by a department can be stored in a department library. Libraries can also hold objects that are not related to a single product. For example, parts that are related to more than one product could be stored in a common parts library (such as a Commodity Parts or Engineered Parts library), from which you allow multiple product teams access to those parts.
Your Windchill solution provides a set of library templates that can be used when you create a library. These templates set the initial rules that are enforced within the library. For details on what is set in a library template, see Working With Context Templates. For more information on how to create additional library templates, see Using Current Library Settings as a Template.
After you have created a library, you can use the business administration utilities to modify the rules for the library. For additional information, see the Products and Libraries reference topics.
 |
Users who are members of the Library Creators group can create libraries. Additionally, organization administrators can create libraries. They do not have to be a member of the Library Creators group. Site administrators can also create libraries but only if they are a member of the organization that is hosting the organization container associated with the library being created. By default, the site administrator is not a member of the organization.
|
Site and organization administrators can add members to the Library Creators group from Organizations 
> table. The new library icon 
appears on the Libraries table only if you have the necessary permissions for creating libraries.
> table. The new library icon appears on the Libraries table only if you have the necessary permissions for creating libraries.To create a new library, use the following procedure:
1. Click the new library icon on in the Libraries table.
on in the Libraries table.The New Library window opens.
2. Select the type of library you are creating from the Type drop-down list.
Multiple types are listed if your site has created subtypes of the wt.inf.library.WTLibrary type; otherwise, only Library is listed. (If organization identifiers, such as a CAGE code or DUNS number, are enabled at your site, the organization identifier is displayed as a read-only attribute. For additional information, see the Products and Libraries reference topics.)
3. To use a shared team as the context team for the library, enter a team name in the Shared Team field by clicking Find to locate the shared team. To remove a shared team name from this field, click Clear.
This field is not required, meaning that you can leave it blank and select team members after you create the library. If you do select a shared team, you can only select one. This group of members can comprise the entire library team, or additional team members can be added, as long as the shared team you select is set up to allow it and as long as you have selected the Allow roles and/or members to be added locally in this context checkbox.
| | This field appears only when shared teams are defined for the organization. For general information about shared teams and the use of shared teams in a library, see Teams. |
If you have selected a shared team, select the Allow roles and/or members to be added locally in this context checkbox to be able to add more team roles and members to the library team. You can select this checkbox only if the shared team has been set up to allow for this.
4. In the Name text field, enter the name of the library being created.
| | The library name must be a unique library name within the current organization context, and cannot contain the following special characters: /, \, :, *, ?, <, >, |, ", or ,. |
5. From the Template drop-down list, select the template that you want to use.
| | If you chose to use a shared team and the template you selected includes a reference to a shared team, then the shared team you chose to use overrides the shared team specified in the template. All of the shared team roles and members (if any) from the shared team referenced in the template are overwritten by the roles and members of the shared team you selected in the Shared Team field. |
For a description of the out-of-the-box library templates, see the Products and Libraries reference topics. For information about creating a template, see Using Current Library Settings as a Template. For general information about templates, see Working With Context Templates.
6. In the Description text field, enter a description of the library. The description can have a maximum of 4000 characters.
7. Determine whether you want the library to be a private library from which only selected team members will have access or a public library where all users may have access.
| | If a shared team has been selected for the library, then this field is disabled. |
To limit the access, select Yes for the Private Access attribute. If you select Yes, then access is restricted to use only the access control policies that are defined within the library context being created; any public access policy rules written at the organization level are not inherited by the library. By selecting Yes, the default domain for the library is moved from the organization PDM domain to the organization Private domain. For more information on the implications of moving domains, see Context and Domain Hierarchy Overview.
If you select No, then the library is accessible based on the access control policies that are defined for the library context and those inherited access control policies defined in the parent context.
8. Click OK to create the library and close the window.