Page History

dataIndex=(value|target) Required if ALL attrs identified by attrId-param are of type xGraphic or externalCrossReference

Basically, there There are the following use cases for this type of requests:each with set of request params involved:

1. Value of some certain single attribute needs to be updated
   1. It's an attribute of a type that can be non-unique
   Single-update
   1. Non-unique attribute at it's level (e.g. of type xGraphic, externalCrossReference, crossReference and figure)
      1. xGraphic, externalCrossReference
         1. attrId
         2. dataIndex
         3. value
      2. crossReference
         1. attrId
         2. target
         3. termLang
         4. mainLang
      3. figure
         1. attrId
         2. figure
   2. Unique attribute It's an attribute of a type that should be unique at it's level (all other attribute types), mean other than mentioned in point 1.a)
      1. It's a picklist attribute
      2. Picklist attributes (e.g. of type processStatus, administrativeStatus, termType, grammaticalGender and others)
         1. attrId
         2. value
      3. Plaintext attributes It's a plaintext attribute (e.g. of type definition, source, context, geographicalUsage, subjectField and others)
         1. attrId
         2. value
2. Multiple attrs can be affected
   
   1. Batch-update draft attributes (but attributes will be remain drafts) - request params are same as described in point 1. Such usage is involved when user updates any attributes within batch-edit window.
   2. Batch-confirm draft attributes, so attributes won't be drafts anymore. Such usage is involved when user presses Save-button in batch-edit window
      1. attrId/attrId
      2. dropId
      3. draft0/draft0
    Batch-update
   1. Non-unique attribute at it's level.
   2. Unique attribute at it's level