Search

Hi,

Thanks for the suggestion. Can you please explain a little more about setting metadata and automation for our purpose?

Thanks!

There will be 100 companies approximately, 100 portfolios (approx) containing 1000s of accounts and each account contains around 1 to 50 documents. Companies will own accounts, for example PortfolioA will have 1000 accounts, Company1 own 300 accounts, Company2 own 400 accounts and Company3 own remai...

Yes, you are right. Portfolios are going to have thousands of consumer accounts, different companies are going to own those accounts (will be handled with permissions). For example, PortfolioA will have Account1 (like 1022593032), Account2, Account3,..., Accountn. CompanyA owns Account1 and Account2...

Hi, Thanks for your input. We might have 10K nodes per parent (we will consider segmenting it in different folders like you suggested though), but API call is going to search for only 1 node (or at the very max may be a few more nodes) in a parent at a time. The usual use-case is going to be like, /...

Hi, Thanks for the reply. You say the performance of the UI will be a problem if we have lots of nodes per parent. We will be doing API calls, we will not be using OpenKM directly so UI being slow isn't a big concern for us. We might have 10,000 nodes (folder) under each parent (folder), will the pe...

Appreciate anybody's help .

Hi, We have been using OpenKM for some time now, but still a newbie when best practices are taken into account. We are going to have about 15 million documents. Gone through other threads regarding this topic and have a basic idea of hierarchy that will help us. We have a list of Main folders that w...