Skip Headers
Oracle® Universal Content Management
10g Release 4 (10.1.4)
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next

Saving a Fragment in a Fragment Library

When you save a fragment that you've created with the Fragment Editor, you must choose a fragment library to store the fragment in. You can store the fragment in its own library, or you can store it, along with several others, in the same library. You are prompted for this the first time you save the fragment.

To save a fragment in a fragment library, perform these tasks:

  1. When finished making changes to a fragment (see Editing Fragments), click the Save icon (Figure) on the Designer toolbar (or click File then select Save).

    Save Icon

    Save Icon

    The Save Fragment dialog (see Save Fragment Dialog) is displayed.

  2. Click New to create a library for this fragment.

    Or, if you've already created a library, select it in the list and then click OK.

  3. On the Assign Info Form, enter the appropriate metadata for the library (Content ID, Type, Title, and so on) and then click Assign Info.

The library is created in the content server, and it displays in the Save Fragment dialog (preceded with the text "server:") the next time you open it.


Note:

The Save Fragment dialog displays only the first time you save a fragment. You're taken directly to the Assign Info Form with each subsequent save.

As you create and manage fragments, you may find it easier to group related fragments together in relatively small numbers (or in some cases put a single fragment in a library by itself) because fragments cannot be moved around, backed up, or distributed individually. They are handled and managed as fragment libraries (see Uploading and Downloading Fragment Libraries).

The default fragments that ship with Site Studio are stored in read-only fragment libraries, which is why you don't see them in the Save Fragment dialog (and also why you cannot edit the individual fragments).

You can make your own fragment libraries read-only to prevent others from accidentally overwriting or erasing a fragment (see Making a Fragment Library Read-Only).