Search  
 

Please login to post into the forums. Remember - keep your posts friendly. 

Note: Identic Pty Ltd reserves the right to remove any material it considers inappropriate or offensive. Please report any undesirable posts or behaviour to support@lucidcentral.org.

If you have any direct support requests such as reactivation requests please use the help desk.

  
 

Login

    
 
HomeHomeLucid3 Discussi...Lucid3 Discussi...Building and us...Building and us...BEST practice for large projects with multiple people using LucidBEST practice for large projects with multiple people using Lucid
Previous
 
Next
New Post
8/22/2019 8:47 AM
 
Hello. I am working on a large project and we will have up to six people entering data into Lucid Builder from multiple computers. I was wondering what the are the best practices for managing this and are there tools to merge different versions of a key that are being worked on at the same time by different users. 
Thanks in advance.
 
New Post
8/22/2019 4:19 PM
 
Hi Gallaher,

Thanks for posting your question to the forum. We've found the best way to deal with multiple users working on the same key is to first come up with an agreed feature list (at least a core list). This makes merging data from each of the key authors much easier.

So to summarise a suggested process:
  1. Create a new key.
  2. Enter the standardised features and states.
  3. Either enter the list of taxa (entities) you are dealing with and divide up the scoring between the authors through agreement. (e.g. Author 1 scores entities 1-10; Author 2 scores entities 11-20 etc) and give each author a separate copy of the key to start the scoring process. Or alternatively, divide the entities into separate copies of the key that goes to each author. (i.e. Author 1 key - contains the standard feature list + 1-10 entities; Author 2 key - contains the standard feature list + 11-20 entities).
  4. Merging the data. Once each author has completed scoring their set of taxa against the features these keys can then be merged into a "master" key.  That is create a new key and use the in-built Lucid Builder import options to import the other keys. The thing to remember with the key data import is the key being imported will potentially overwrite key data in the opened key where they intersect depending on score values.

    For example if the currently opened key contains the following:

    (Entity) Eucalyptus baileyana  - (Feature)Adult Leaves: (State) alternate ----> Scored as Present

    The key being imported contains:

    (Entity) Eucalyptus baileyana  - (Feature)Adult Leaves: (State) alternate ----> Scored as Absent

    Then the open key score for Eucalyptus baileyana  - (Feature)Adult Leaves: (State) alternate would stay as Present. Due to the score order dominance as indicated in help (see below for the link).

    The chance of unintended overwriting of key data is eliminated (or at least greatly reduced) if the key data is separated as described above. 

If there were any differences in the features between the open key and the key being imported, the non-matching features would be imported, along with any scoring that maybe applied to them. The same applies to the entities. Media attachments can also be merged.

Some more information about import merging can be found in the Builder help here. Let me know if you need any additional information or clarification on this.

Cheers,

Matt.
 
Previous
 
Next
HomeHomeLucid3 Discussi...Lucid3 Discussi...Building and us...Building and us...BEST practice for large projects with multiple people using LucidBEST practice for large projects with multiple people using Lucid


  
Copyright 2019. All rights reserved. Identic Pty
Terms Of Use  Privacy Statement