Working with libraries

Before creating Web content, you must create a set of libraries to store your Web content items in. You also define the role that users and groups will have when working with different item types in libraries.

• Web content library architectures
  Multiple Web content libraries can be used when creating Web content.
• Creating Web content libraries
  You create Web Content libraries in the WebSphere Portal Express administration portlet.
• Deleting a Web content library
  When a Web content library is no longer required, you can delete the library.
• Disabling a Web content library
  When a Web content library is no longer required, you can disable the library. This prevents the library from being accessed from an authoring portlet, preventing users from updating any items stored in the library. Any items referenced from this library will still be rendered in Web content.
• Using item type roles within a library
  You define the role of a user or group for each item type used within a library. The roles determine the default library access of a user or group, as well as defining different access to individual tasks and views within the authoring portlet.
• Defining roles within a library
  You define item type roles within the Portal Content section of the IBM^® WebSphere^® Portal Express administration portlet.
• Library access control example
  This example shows how item type roles can be used to grant different groups specific access to different features in the authoring portlet.
• Library version management
  You can restore a set of items within a library that either have the same label or were versioned at, or before, a specified date and time.
• Web content library management APIs
  You can perform various Web content library functions using the Web content API.