Excerpt |
---|
In the settings section of your Picturepark you will find status, which shows:
Nested values are flattened for better search performance which may affect Business Rule configuration or Advanced search queries. See Tagbox, Fieldset, and Relationship for details. |
Expand | ||
---|---|---|
| ||
Content and List ItemsYou can now reuse field IDs in Picturepark which previously was not possible on the same schema or on child schemas after the field had been deleted. In order to do so, you see a badge on Settings in the Main Menu which leads to the Status Page where you find the new index for Content and List Items. There you can trigger the update of Content and List Items. Picturepark now cleans up the data preventing the re-use of a field, but independent from the update of the schema. Therefore indexes are asynchronously updated once the editor deletes a Field that references other schemas or fields. The update on request might prevent deleting a ListItem because of a stale reference, but it makes the schema update a lot faster. The trigger point for this update is a manual start by the user after changing the schema configuration, indicated with a badge next to the settings menu. This way, the admin controls when Content and List Items shall be updated, instead of updating all items after every change. The significant advantage is to be able to perform multiple changes to multiple schemas without waiting for an update of all items after each change. However, the drawback is that some Items may contain obsolete information until the update is triggered:
The Status Page in the Settings in the Main Menu shows the state of Content and List Items: up-to-date, in progress, and outdated. For the outdated state, a button at the bottom "update" triggers the update. It is not required to do the update immediately after every edit to a schema, but the content authority should trigger an update after finishing the schema edits. Otherwise, the search may find Content Items by tags that are no longer available in their metadata profile. |
...