Gregers Larsen 9/2/2013

Like

1886 Views

Hello LEAP crew, thanks for a useful modelling tool!

In our organisation, multiple will use and program in the same LEAP project ("Area"). Therefore we use SVN on our local server, but I think this question applies to user of Dropbox etc. as well.

Will only singular files change in accordance to the place where I work? By this I mean, if I change a number in the Key Assumptions, will it ruin the work for my colleague working in Demand\Transport for instance? Or will LEAP only change the files that has something to do with my exact data change?

Thanks,
Gregers

Charlie Heaps 9/3/2013
 

Like

1885 Views

Hi,

I'm not sure I understand your question exactly but here are a few tips:

1. You need to treat LEAP as a single-user system (just like Word or Excel). Currently, you cannot safely have two people simultaneously editing a LEAP area. We are considering adding some features to allow you to have a repository of LEAP areas from which you can check out areas to be edited and then check them back in again, but this is not supported at present.

2. If you want to have different people working on different sectors then I recommend using Excel as the place where you do the data entry and then use the Analysis: Import and Analysis: Export options as the way of moving data back and forth to LEAP.

I hope this helps?

Best,

Charlie

Gregers Larsen 9/24/2013
 

Like

1825 Views

It is clearly not the preferred option. Importing and exporting to Excel can cause errors between people and is not, in my opinion, so well defined in the manual.

I have looked into the data structure of my LEAP project and can see the challenges as multiuser systems. For now, I am working on it on my own, but I am specifying very harshly to my colleagues the need for regular updating ad committing.

I think this is something you should maybe consider, as LEAP projects quickly can become big enough for team exercises. And with further uses of services like Dropbox, Box, SkyDrive and SVN there is a acute risk of version errors.

Thanks,

Gregers