Create offline copy, local replica.

[grandfso]

Hi,
I was trying to find answer to my question however, I didn't manage to. Alfresco seems to be very good solution for my client. My only concern is, will Alfresco allow my clients, to create a local replicas of the database. So they can view items they have access to when being offline? Or at least, does Alfresco support any methods of exporting of documents and records? What would you recommend?

Thanks, Radek

[zaizi]

Your users can access documents within Alfresco repository as a shared network drive by using Alfresco's CIFS functionality.

If they are on Windows you can use Briefcase or Sync Center to make local copies of the network folder for offline viewing and editing. When they connect back to the network they will be sync'd with Alfresco.

[grandfso]

Zaizi,
First I'd like to say thanks for your prompt reply. The solution you've suggested appears to be what I've been looking for. Only one concern. I'm looking at having a repo not only for documents, but also records. Will those also get exported and synchronized as a files for example?

thanks, Radek

[zaizi]

What do you mean by records?

[grandfso]

Hi,
If I create for example new html content, I'd consider this as a record. 

thanks, Radek

[zaizi]

Html content will appear as an html file and thus can be synchronized like any other file.

[grandfso]

zaizi, thanks for your help. This answers my question perfectly. I appreciate it

[jooray]

Does this work well?

Is it possible to somehow also do locking with briefcase, so if I check out something for changes, it's locked on the server?

[stevereiner]

FlexSpaces+AIR has some support for offlining ("tools/make available offline", "tools/offline upload" menus). May add support for offline metadata view/edit (including locked state) stored in AIR's built-in SQLite db while offline in the future.

http://forums.alfresco.com/en/viewtopic.php?f=32&t=14382

Steve

[chrisdav]

It will be good when it works again, just beware the bug https://issues.alfresco.com/jira/browse/ETHREEOH-1247 . This means versioning and metadata get deleted when you synchronise. Instead of creating a new version it deletes the node and creates a new one. So you have lost your old versions and any metadata.

I have yet to find a version of 2.* that it works on, although I have not gone right back to 2.0.

Should be getting fixed in 3.1 sp2.