Version 2.3.0

Support for Reusing Digest Already Written to Custom Metadata

When Use Existing Value if Present is checked, the code that normally would generate the customized digest for an item during the item set creation, will look to see if the item already has a value stored in the specified custom metadata field. If the item has a custom metadata field with the same name (as specified for setting Digest Custom Metadata Field) the script will further check:

• Is the value of the field non null?
• Is the value a String?
• Is the value not empty or only whitespace character?

If the value passes all of these checks, then the existing value will be used rather than generating the value from the profile.

Care should be taken when using this setting! The script has no way to know if the digest value present in the field was generated by this script or using the same metadata profile! It is very possible to run the script one time with profile A on some items and then run the script again later with profile B (or even modified profile A) and some of those same items and incompatible digests could be used!

Version 2.2.0

Added ability to record digests used to create item set

Version 2.1.0

Small changes towards improved performance / resource usage

Version 2.0.0

Initital GitHub Commit

Note: GitHub version starts at v2.0.0 since this script is a rewrite of an older script with similar functionality.