Changes between Version 62 and Version 63 of S3/S3XML


Ignore:
Timestamp:
10/06/11 06:55:11 (10 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3/S3XML

    v62 v63  
    346346||'''modified_on'''||datetime**||date and time when the record was last updated||''no, default: request date/time''!** !***||
    347347||'''created_by'''||string||username (email-address) of the user who created the record||''no''||
    348 ||'''modified_by'''||string||username (email-address) of the user who last updated the record||''no''||
     348||'''modified_by'''||string||username (email-address) of the user who last updated the record!**!***||''no''||
     349||'''owned_by_user'''||string||username (email-address) of the user who owns the record!**!***||''no''||
     350||'''owned_by_role'''||string||name of the user group who collectively own the record||''no''||
    349351||'''mci'''||integer||master-copy-index****||''no, default: 2''!*** !**!**||
    350352
     
    353355- (!***) the last update date/time and mci are required in synchronization
    354356- (!**!**) the master copy index specifies how often a record has been copied across sites, see below
     357- (!**!***) record ownership will be retained if the record owners can be matched against existing users/user groups
    355358
    356359The {{{uuid}}} will be stored in the database together with the record. If {{{uuid}}} is present and matches an existing record in the database, then this record will be updated. If there's no match or no {{{uuid}}} specified in the {{{resource}}} element, then the importer will create a new record in the database (and automatically generate a {{{uuid}}} if required).