File Type Settings

Property	Description
Layers
Add	Here you see the Layers that can be added to the selected File Type. This way you can prevent multimedia layers being added to images.
Reorder	You can reorder the Layers, which has currently no impact in Picturepark.

It is not possible to add fields to File Types, but you can update settings of available fields.

General Settings for all Schemas

Common Settings for all Schemas
Property	Description
Settings
Name (translated)	By clicking on the Edit button, you can change the display name of the schema as well as add any translations for any Metadata languages you have available in your Picturepark. The ID of a schema is always singular. When creating a List "Events" ensure that the ID is "Event" or name the list singular too. This is important for any type of integration.
Schema ID	All technical references to the schema and its fields refer to the ID. You cannot update the ID which you set on creation. Picturepark automatically capitalizes the first character of the schemas ID. Numbers are not allowed as ID-property of any schema. The ID of a schema is always singular. When creating a List "Events" ensure that the ID is "Event" or name the list singular too. This is important for any type of integration.
Description (translated)	Here you should enter succinct information to help you, editors, and other admins understand the schemas use. You can also add information for any Metadata languages you have available in your Picturepark.
Content item protection	Enable admins to: prevent assignment (e.g. assign a Layer to Content Items) prevent update (e.g. changing layer settings) prevent deletion This setting is used for Picturepark system layers and system lists (all checkboxes set to true), not editable in Picturepark.
Fields
Add field	Clicking on Add will allow you to add a new field. You cannot add fields to system schemas.
	For tagbox fields on layers you can define the default values for tagbox. Those values are automatically assigned when the layer is assigned and you create a new tag from within the layer. Define “Active employee” as default value for the tagbox “Person” on the Layer “Corporate Information”. Assign Layer “Corporate Information” Find Tagbox “Person” Create a new person for the tagbox See the fields (information) you need to create a new person “Active employee” is prefilled.
Reorder	If you click on this button you can drag and drop reorder the fields in the schema. This will change the display order of the fields in the schema after you have added them to the content.
Edit and delete	You see any fields of the schema listed here. On mouse-over, you find the options to edit or remove. To give you an overview of the most important settings, you see what field type each field has here as well as boosting and whether search and index are on. For tagbox fields, you also see the connected List and can go directly to this List by clicking on the link and then the open icon.
Display Pattern
Update Display Pattern	Here you can change the Display Pattern for the schema, which triggers a Status Update.
Activity
Created	Statistic on creation date, creation time, and creator.
Modified	Statistic on modification date, modification time, and modifier.
Owner
Transfer	You can see who the owner of the List is here, and if you have the corresponding permissions, you can also transfer the ownership to another user. An owner has full control of his or her List regardless of other permissions applied.
Permissions
Add	You can add Permission Sets to the schema.
Remove all	You can remove all Permission Sets from the schema at once.
View and unassign	On mouse-over, you can view the assigned Permission Set or unassign it from the schema, check the result for un-assigning in the advanced view by disabling it first.
Show advanced	A matrix is showing the active permission listed by action per user role. You see if user roles can view, manage items, or manage the schema (settings). If you switch off the Permission Set, you test out how Permission Set removals change the permission. This switch is just for checking; it does not disable the Permission Set.
View for all	Per default, the schema is visible to all users i.e., All users can view, but only the owner can manage. You can however also change this so that only certain users can see/edit the List by adding permission sets here. If "View for all" is inactive and no Permission Sets are applied, then only the owner can view and manage this List.