Create a Schema
Each schema type has some schema-specific settings and also requires different follow-up tasks. Please check each schema type for details.
Press + (Create)
Choose the desired type: Fieldset and relation, Layer, List, Virtual
Provide a name (choose plural, e.g., products)
Validate the ID (choose singular, e.g., product)
Provide a description (optional).
Search a Schema
In the list layout for all schema types, you see all schemas in a tree-like hierarchy. This allows admins to scan the Picturepark data model in one go easily. Another main benefit is the schema-wide search. Admins can search for a schema and get results from all possible schema types.
Import a Schema
You can import schemas from another Picturepark of the same version. It is not allowed for the schema to have the same ID, so You must change this.
Lists linked to other lists must all have unique ideas. Picturepark will otherwise link to an existing list.
Update a Schema
Open Schema Type
Search for Schema
Click on Schema
Available Settings (cogwheel icon)
Update & Save
Limitation: File Types are system fields. As such, we have limited what can be changed here so that the system works as expected. You can, however, make the following changes:
Field Settings: Include in Search, Filters, and Analyzers, e.g., make XMP core fields searchable
You can make the original file creation date (EXIF) searchable to create a filter for the file creation date.
You can make DPI searchable to add a width/height filter to the sidebar or calculate orientations (if not available for all files).
Export a Schema
You can export schemas for use in another Picturepark of the same product version.
Open the desired Schema Type.
Select your schema and then export. Click on the icon in the toolbar or export from context menu.
By default, the export contains all schemas. De-select any referenced schemas that you would like to exclude from your export.
For lists, you can choose not to Export list items. You only export the fields and settings without any items.
Please be patient. There is no indication that your schema is exporting - you will need to wait for your computer dialog to save. The export can take more than a few minutes for complex schemas.
If you are exporting Lists and Layers that have child lists, please select any child lists or layers that you would like to exclude while exporting.
Delete a Schema
Select the desired schema.
Choose to delete (trash bin icon) from the context menu or the toolbar in the browser or detail view.
Confirm your desire to delete.
Schemas in use or with references (assigned items) cannot be deleted. You must clean up the references first (e.g. remove from Tagbox, remove from items)
Picturepark has so-called System Schemas that are required for the Picturepark to function correctly.
All users can view the information therein if you use them in Lists or Layers.
System schemas display "SYSTEM" in the UI.
You cannot create a system schema, delete the schema, or delete any fields.
Examples in Lists are country, language, and region, which show the "System"-flag in the top right corner.
Manipulating System Schemas
You can change the following in a system schema:
Indexing (filters, search, boost factors, text fields, filter, and simple search analyzers)
Name and translation
You can also add layers for file types.
You can add a calculated value for a field; however, we don't recommend doing this.
create a system schema
delete a system schema
add list items
apply permission set to these schemas.
Schema Hierarchies (Parent and Child)
In a parent/child setup, the children get the fields from their parents and can have their fields too, e.g., parent “controlled vocabulary” with a field: term; child “keywords.” Picturepark displays the children in a tree-like hierarchy, so you know which schemas belong together.
You cannot remove a field on the parent from a child schema.
You can only reorder the fields that are on the child directly. You cannot reorder inherited fields. The parent fields are at the top, and below are the child fields.
You can break inheritance for tagboxes but not for other fields, so your tagbox can be required on the parent and not on the child. Other fields like a title or date field are required on parent and child.
Schema Circular References
Circular references, also known as cyclic dependencies, make it possible to refer from one record to another and vice-versa.
Connecting lists: Cities and Regions
The city of Aarau is in the Region of Aargau. The capital of Aargau is Aarau.
Connecting lists: Product and Market
Product A is available in markets D, A, and CH. In Market CH, the best-selling product is A.
Connecting lists: Employee and Department
The employee Megan Manager works in the department Marketing. The supervisor of the department Marketing is Megan Manager.
An employee with the Department. & The Department with a Supervisor.
You have a person and department entity. The person is a member of a single department (simplified). The Department has a supervisor who is one of the Employee members.
Blueprints for Schemas (schema.org)
A good source for schema examples is the website of schema.org, an open-source community founded and supported by Google and Microsoft that maintains and promotes schemas for structured data on the Internet, on web pages, webshops, and many more.
Examples from schema.org, which you can use as a blueprint mainly for Lists in Picturepark: