Thank you all. Currently, I'm going with a utility that is a front to Tortoise and automates the update, lock, edit, and commit steps. I'll keep your ideas for reference.
Thanks.
Jerry L. Johns
478.394.1541
jerrylanejohns_at_gmail.com
> On Oct 14, 2014, at 10:19 AM, Ryan Hathaway <rghathaway_at_starkcountyohio.gov> wrote:
>
> Hi Jerry,
>
> Based on the info which you've shared, if I were tasked with such a problem to solve, I would consider implementing and installing a Windows Scheduled Task on each user's PC which runs a custom .bat, vbscript, or powershell batch/script file on a schedule. The script would wrap some error condition handling (file in use, network errors etc.) around some calls to the built in apache svn command line tools (these are installed as part of the TortoiseSVN installation) which would apply update/commit/etc. actions, or at least capture the list of commits & updates which would be needed to bring the repository and working copies up-to-date, then save the list into a database, log file, or rss feed, and/or send email notifications, depending on your requirements analysis.
>
> 3rd party tools as Simon mentioned are of course also another option.
>
> Best of luck!
>
>
>
>
>
> Thank you,
>
> -Ryan
>
>
> Ryan Hathaway
> Programmer Analyst
>
> Office of Alan Harold, Auditor
> Stark County Ohio
> 110 Central Plaza S
> Canton, OH 44702
>
> 330-451-1414
>
>
> ***Please note: My email address has changed to rghathaway_at_starkcountyohio.gov ***
>
> >>> Simon Large <simon.tortoisesvn_at_gmail.com> 10/11/14 4:09 AM >>>
> Subversion is a revision control tool, not a document sharing tool, and as such it requires a certain discipline to use it. The user decides when to commit changes and adds comments to describe those changes, and the user decides when to update their working copy with changes from others. These things cannot be automated. For plain text files subversion will merge changes when a file is changed both locally and remotely; it cannot do that with binary formats such as Office documents. Even when the files are mergeable it requires communication between users to make sure they are not working on the same parts of the same files.
>
> For document sharing by non-technical users there are better solutions. I know nothing about One Drive, but Google Docs works well. All changes are saved automatically and if two users are editing the same doc they can each see the other's changes happening.
>
> Horses for courses as they say.
>
> Simon
>
>> On 11 October 2014 02:44, Jerry Johns <jerrylanejohns_at_gmail.com> wrote:
>> My company is thinking about using an alternative to SVN for MS Office document management.
>>
>>
>>
>> The biggest complaint is that non-technical people forget to check for repository updates or don’t commit after making changes to local files and this affects other people using those documents.
>>
>>
>>
>> I want to keep SVN instead of going with something like One Drive for Business, etc.
>>
>>
>>
>> Are there tools or options that would extend the functionality of Commit Monitor, for example, so that it keeps the local copy in sync?
>>
>>
>>
>> Thanks.
>>
>> Jerry
>>
>
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3089893
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-10-14 17:25:14 CEST