Skip to main content

Synchronize a container with a master container

Project description

Introduction
============
collective.contentsync addresses the case where many folders must be synchronized with one master folder template.

For example, your system has many clients who need to upload files into a directory structure. Your template may look like this:

Template
- Accreditation files
- Financial statements 2008
- Financial statements 2009
- Staff profiles

Every client must also have this structure since content is going to be uploaded into that structure. Suppose you have 1000 clients and now you add "Financial statements 2010" to your template. This new folder must be pushed to every single client. This process would be time-consuming by hand, hence the existence of collective.contentsync.

Rules of synchronization
========================
The terms "source" and "destination" are used. The rules are dependent on an item providing information as to whether it was created by a synchronization or a user.

1. New items in the source tree are copied to the corresponding location in the destination tree. If an item already exists at this location in the destination tree it is preserved.
2. Items which appear in the destination tree but not the source tree are deleted if and only if they were created during a synchronization and do not contain any items that were created by a user.
3. Items which appear in the destination tree and which were created during a synchronization are renamed if the corresponding source item is renamed. The rename is limited to title and does not include the id.

User interface
==============
The user is presented with a progress bar and a detailed log. This provides
constant feedback and prevents timeouts.

Usage
=====
Append /@@collective.contentsync.form to the URL of the item you wish to synchronize, or simply run the collective.contentsync profile in portal_setup. Running the profile will add a Synchronize tab to every folderish item in your site.

collective.contentsync has not been tested with a pure Zope application but should "just work" since it has no Plone dependencies.

Changelog
=========

1.01
----

* If an object in the source tree is renamed it is renamed in the target on a
* sync

* More progress outputs

1.0
----------------

* Initial release

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

collective.contentsync-1.01.tar.gz (10.2 kB view details)

Uploaded Source

Built Distribution

collective.contentsync-1.01-py2.4.egg (27.3 kB view details)

Uploaded Source

File details

Details for the file collective.contentsync-1.01.tar.gz.

File metadata

File hashes

Hashes for collective.contentsync-1.01.tar.gz
Algorithm Hash digest
SHA256 48342ab77006365be86146182d25404d4d2e39c54fc07965f184047c3c443743
MD5 7a5139886ab07265ef896adaebae0afc
BLAKE2b-256 2e7cf40cb94d64d8424b792b297e21de9622cf319fcda6ced8869ec8b2f6b692

See more details on using hashes here.

File details

Details for the file collective.contentsync-1.01-py2.4.egg.

File metadata

File hashes

Hashes for collective.contentsync-1.01-py2.4.egg
Algorithm Hash digest
SHA256 459fe471e4db894b96fc884173a433d76be45985063e0f75102d750aab874f2b
MD5 b606bec290af2710fcf98e303b789c28
BLAKE2b-256 19039f61874fa5e2f86a0fc818b6da00d70ebb7b442c5617315a1d4557de99ff

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page