Storing dead properties as custom metadata

Content Platform Tenant Management Help

Version
9.7.x
File Size
4269 KB
Audience
anonymous
Part Number
MK-95HCPH002-19

HCP can be configured to store WebDAV dead properties as custom metadata for an object. When HCP is configured this way, you use the PROPPATCH and PROPFIND methods to store and retrieve dead properties just as you do for live properties.

This is the only way HCP can store dead properties. If a namespace is not configured to store dead properties as custom metadata and you try to store dead properties, HCP returns an HTTP 404 (Not Found) error code.

To have a namespace configured to store dead properties as custom metadata file, contact your tenant administrator.

As with custom metadata accessed using WebDAV, dead properties are stored in the default annotation. This annotation is represented by the custom-metadata.xml file

Using the PROPPATCH method, you can change individual dead properties in the default annotation. You do not need to replace the entire annotation as you do when you use it for custom metadata.

You can use the default annotation to store either custom metadata or dead properties, but not both:

  • If, after using the annotation for custom metadata, you try to store dead properties, HCP returns an HTTP 409 (Conflict) error code. In this case, you need to delete the existing annotation before you can store dead properties for the object.
  • If, after storing dead properties, you replace the annotation content with new custom metadata, the dead properties you stored are lost.