6. Synchronization
|
|
Synchronization procedure serves to share changes made to project structure and lookup list definitions in one (usually admins) project with other project database. It is useful especially when managing extensive research project, when there are many field teams working on different parts of a study area. In other words, synchronization ensures consistency of database structures of individual Field-Map projects. In addition, synchronization also enables to share data collected in the field, to assign/remove plots to be processed by individual research teams, to send files and text messages, etc. Synchronization is based on the existence of central (usually server) database, where database structure and collected data are stored. If the modification is made to this central database, it will become transferred to users databases during synchronization. Using synchronization is shortly linked with user accounts in Field-Map - generally admins and poweusers are allowed to manage server database, to assign individual plots to users or to download data. On the other hand, users only update structure of their databases by running synchronization, alternatively they send collected data to server repository. Synchronization procedures are defined in so called Synchro Journal. It stores commands concerning changes of project database or lookup list structures, adding/removing plots for individual users or sending files and messages. The majority of operations managing Synchro Journal is available only for admins and powerusers. Almost all kinds of changes made to Field-Map project are shared with other users via synchronization procedure. However, voice memos and photography are not synchronized. |