Maintenance

Introduction:

You have to think about your process with CHILI to organise the files.

The files structure is depending of the process used. 

With an example, I will try to explain you the philosophy to organise correctly your documents in CHILI in relation with your portal. 

For example: 

You can imagine you have a webtoprint portal with test files before order, ordered files and archived files. 

CHILI documents: 

You don't want to keep all the tests files because the user has created a test file to know the possibilities with your portal.

Every tests files are placed somewhere on the CHILI server.

If the end user has created a test file, you have to move it via the webservice on a specific "Temp folder" if the user is not going to the next step "order".

The temp folder will be clean after X days/weeks…

If the user has decided to order the file, the file will be moved to a specific folder (for e. g. : ordered files) 

IMPORTANT REMARK : You will have to delete the folders/the files via the webservices or manually in CHILI but never via the File system. 

Assets: 

When the assets are imported in CHILI, an unique file id is created to identify the asset.

If you import the asset in a document, there's a relation between the document and the asset done by the file ID.

When you are going to delete the asset, the unique file ID doesn't exist anymore.

So you have to take care if the asset is used in another document before delete the file, because the relation will be lost.