Question

I need to manage attachments on my Spring web application and I thought to use an open source repository. My app it’s a job approval system using Java EE / SPRING 3 Framework and postgress DB to allow user to tracks the job, right through every step of the approval process. It is a fully managed, collaborative system that operates from a central server and is accessed by a standard internet browser.

I’ve a little bit of experience in Alfresco and I’m using it to store data into the repository and I’ve a doubt about the data organization into the repository. Have I to take care about the organization the data or just upload files into the repository when needed? For instance, I could create a new folder on repository for every request, is it a correct or no?

any suggestion will be really helpful!

thanks in advance, Andrea

Answer 1

There’s no extensive guideline on the repository structure. It really depends on the content you store and its lifecycle. There are countless concerns that might affect your design, for instance:

• you need to configure rules to handle only some content items -> more folders needed

• you need to configure a behavior to act on some of the content items (e.g. cmis:document to ws:asset in the Web QuickStart)

• you store a gazillion content items -> you must use a balanced tree of folders to keep performance

• you need to configure permissions on subsets of the content items -> easier to configure a folder and let documents inherit