Repository administrators can create asset types, which
include the asset type name and description. When creating an asset
type, repository administrators should consider who uses the asset,
in what context the asset is used, what artifacts the asset must include,
what other assets are related and how, and what descriptive information
users need to find and use the asset efficiently. Administrators can
define other levels of constraints such as those on artifacts, categories,
or attributes.
Before you begin
To create an asset type, you must be a repository administrator.
If you are a community administrator, to create an asset type for
your community, see
Creating community asset types.
About this task
Users
and administrators use asset types for many purposes, including the
following:
- To align with the internal structure of an organization.
- To allow users to filter a search by asset type.
- To place a constraint on an asset. For example, you can require
that an asset have a specific file type as an artifact or be related
to another asset in a certain way.
- To automatically assign categories to the asset based on the content
of XML artifacts.
- To create rules that allow XML artifacts to be indexed and found
by keyword searches.
- To view metrics of the number of assets that exist by type in
the repository.
- To trigger a custom review process that is assigned to specific
asset types in a community.
- To assign community roles to apply to assets of a specific type.
When creating an asset type, consider
the following questions:
- Who will use the asset?
- How will the asset be used?
- What artifacts must the asset include?
- What descriptive information must the asset include?
- What information will users need to find and use the asset?
- What assets are related to the asset, and what are the relationships?
- Will the asset artifacts include XML content? If yes, do you want
to automatically assign categories based on that XML content?
To create an asset type
that is similar to that of an existing asset type, click Duplicate.
This action duplicates the existing asset type and then you can modify
the existing name and details of the asset type by clicking the asset
type name and editing the details.
Important: Asset types
in the repository are displayed alphabetically. When you create asset
types that correspond to a particular business need or department,
name similar asset types with the same prefixes so that users can
find the asset types in the list easily. For example, for service
asset types you can create the following asset type names:
- Service
- Service Design
- Service Model
- Service Implementation
- Service Test
- Service Test Results
These steps must be performed by a user with administration
permissions.
Procedure
- Log in to the web application.
- Click Administration.
- In the Repository Administration sidebar, click Asset
Types.
- Click New Asset Type.
- Describe the asset type:
- In the Name field, type a name.
- In the Description field, type
a meaningful description. When a user is submitting
a new asset using the Submit an Asset wizard, this description displays
when the user selects this asset type and clicks the help icon for
the Type field on the Describe page.
- Optional: Select the communities to contain
this asset type. If the asset type is not restricted to certain communities,
the asset type is available to all communities in the repository.
- Click the Scoping tab.
- To limit the communities that can hold this asset type,
in the Communities Scoping section select Restrict to selected
communities, and then select one or more communities.
- Optional: Define
the available category schema for the asset type. You can allow either
all or a limited selection of the categories that are available in
the repository.
- Click the Scoping tab.
- To allow all categories to be applied to the asset,
in the Category Scoping section select Use all category
schema.
- To allow only a subsection of category schemas, select Use
only the selected category schemas, and then select one
or more category schemas.
- Optional: Define
an artifact constraint by specifying a quantifiable range of required
artifacts that conform to an extension, format, or label.
- Click the Constraints tab.
- In the Artifact Constraints section, click New
Artifact Constraint.
- Select the range of artifacts to be required, choose
the restriction type, and then type a value for the type of artifact
to require. For example, if creating an asset with
an asset type named "Presentation," you can specify that the asset
contain at least one artifact with a file extension of .ppt. Format
is the context for the file, for example a presentation or a process
model. File extension is the type of file, for example .txt, .xml,
or .ppt. Format is defined automatically based on the MIME type of
the file.
- Optional: Define relationship constraints.
- Click the Constraints tab.
- In the Relationship Constraints section, click New
Relationship Constraint.
- Specify a quantifiable range, and then choose the asset
type that must conform to the relationship that you choose.
- If you want to limit assets of this type to use only
the relationship constraints defined here, select Allow
only these relationships. When users
submit or modify assets of this type, they are not able to select
any other relationships.
- Optional: Add asset
attributes to allow users to enter additional information or choose
predefined values about the asset. These attributes are arranged into
two columns that are visible on the general details page for an asset.
Attributes that are moved into the Hidden Attributes section are not
visible on the general details page for the asset.
- Click the Constraints tab.
- Add attribute constraints to each section. The
sections are divided into Column 1, Column 2, and Hidden Attributes.
You can organize the attributes into two columns to group the attributes
in the general details page for an asset. Attributes contained in
the Hidden Attributes section are not visible in the general details
page for assets. To add an attribute constraint:
- Hover the cursor over the section name and click the Insert icon.
- Click Add Attribute Constraints.
- Enter a name in the filter and select the attribute, or hold down
the CTRL key to select multiple attributes, and click Add
and Close.
- Choose attribute constraints to require.
- Hover the cursor over the attribute name and click the Edit icon.
If the Edit icon does not appear, the attribute is already required
and cannot be edited.
- Select the Attribute is required check
box.
- Click OK.
- Create groups within each section.
- Hover the cursor over each section and click the Insert icon.
- Click Add Attribute Group.
- Enter a name for the group and click Add and Close.
- Reorder the attributes into a logical order and groupings
for asset users. To move an attribute to a different section
or group, click and hold the attribute, move the cursor to the desired
location, and release the attribute.
- Optional: Define
an XPATH expression and rule that automatically applies categories
to an asset based on the content of XML artifacts that you upload
to the asset.
- Click the Automatic Categorization tab.
- Click New XML Artifact Categorization.
- To populate the Namespace Mappings section and test
your XPATH expression, upload a sample XML document by browsing your
local file system for a sample document and click Upload
Sample. If you upload multiple documents, only
the most recent can be used. The sample file can be reused for multiple
assets until you log out.
- To add artifact file types that contain XML content,
click Add File Type, type a file extension,
and click OK.
- Click Add Namespace Mapping,
and then type the prefix and URI of the XML namespaces. If you uploaded
a file in the Sample XML File section, you can click Add
from Sample to retrieve all namespace information from
it. You can edit or delete any mappings from the list. The
default namespace is listed with the prefix "default." You can edit
this mapping to use the actual element name, or use "default" in place
of the element name in your XPATH expression.
- To select one or more categories to apply automatically
to assets of this type if they contain artifacts that match the XPATH
expression you provide, click Add Category and
select one or more categories from the Select Categorizations window. Click Delete to remove a category.
- In the XPATH Expression field,
type an XPATH expression to use to search XML documents. For
example: /wsdl:definitions/@targetNameSpace
- To evaluate the XPATH expression against your sample
XML file, click Test Sample. You
can view the results of the evaluation.
- In the Contains field, type the
value that you want the XPATH expression to match. For
example: example.com
When submitting this asset type, if the results from the
XPATH expression match the value of the Contains field,
the categories you specified are applied to the asset.
- Optional: Define
how the content of XML artifacts indexes and displays in search results.
- Click the Search Index Rules tab.
- Click New Rule.
- Select XML Artifact Rule and
click OK. The XML Indexing
Rule page opens.
- In the Name field, type a name
for the rule.
- In the Description field, type
a meaningful description for the rule.
- In the File extensions field,
type a list of file extensions to index. Separate multiple extensions
by space, For example: wsdl xml dita xsd
- To define XML elements to index, in the Rule Configuration
section, click Add Element.
- In the Element field, type the
XML element that you want to index. Select Index all attributes if
you want to also index the content of all of the attributes for the
element.
- Click OK.
- Optional: To define one or more specific
element attributes to index, click Add attribute,
type an attribute name, and then click OK. Repeat
for all attributes that you want to index.
- Click OK. The Asset Type page
reopens. Click the rule name to edit it, or click Delete to
remove it.
- Click OK to save the asset type.
What to do next
To locate an existing asset type to modify, enter the name
of the asset type in the Filter field for quick identification in
long lists.