Which element is NOT a part of version control in Relativity Web Processing?

In the context of version control within Relativity Web Processing, the primary focus is on managing and tracking different versions of processing profiles and changes made over time. The ability to track changes over time allows users to see how a given profile or setting has evolved, which is crucial for auditing and reverting to previous configurations if necessary.

Maintaining a history of job parameters aids in understanding how specific data was processed and enables accountability and repeatability in processing workflows. Ensuring all data changes are recorded is essential for maintaining an accurate record of activities, which aligns with compliance and efficiency in data handling.

Creating duplicates of processing profiles, on the other hand, does not constitute a core part of version control. While it can be a useful feature in certain workflows, creating duplicates does not inherently track changes or provide a historical record of modifications. Instead, it merely replicates an existing version without the tracking features essential to effective version control practices. Thus, this element does not align with the fundamental objectives of version control in Relativity Web Processing.