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 will have Subfolders which holds the files. Subfolder might sometimes also have another Folder inside. Main folder name will be a name (meaning text value) and Subfolder will be no. Inside each Main there could be thousands of Subfolders.
Hierarchy will be like,
/okm:root/Main1/1022593032/Files & a Folder
/okm:root/Main1/1022593033/Files & a Folder
..
..
..
/okm:root/Main1/1022601308/Files & a Folder
/okm:root/Main2/1022593074/Files & a Folder
/okm:root/Main2/1022593075/Files & a Folder
..
..
..
/okm:root/Main2/1025601308/Files & a Folder
Is this the right way to organize folders and files or is there any other better? Because I read in a thread that having 1000s of child nodes will have performance issues. In our case Main folder is going to have 1000s of folders.
How is Categories, Metadata, Thesaurus, Templates, etc., going to affect? Do we have to work on any of these other than uploading folders and files in Taxonomy?
Attaching couple of screenshots for better understanding.
We will have 1000s of accounts under each portfolio and each account will have 1 to 20 documents. Is it better to have taxonomy structure like this (above mentioned) or,
Here we have all files in same folder prefixing name of folders for each file.
For us it is more important that the performance is good while we do search or other operations using REST API.
Thanks in advance!
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 will have Subfolders which holds the files. Subfolder might sometimes also have another Folder inside. Main folder name will be a name (meaning text value) and Subfolder will be no. Inside each Main there could be thousands of Subfolders.
Hierarchy will be like,
/okm:root/Main1/1022593032/Files & a Folder
/okm:root/Main1/1022593033/Files & a Folder
..
..
..
/okm:root/Main1/1022601308/Files & a Folder
/okm:root/Main2/1022593074/Files & a Folder
/okm:root/Main2/1022593075/Files & a Folder
..
..
..
/okm:root/Main2/1025601308/Files & a Folder
Is this the right way to organize folders and files or is there any other better? Because I read in a thread that having 1000s of child nodes will have performance issues. In our case Main folder is going to have 1000s of folders.
How is Categories, Metadata, Thesaurus, Templates, etc., going to affect? Do we have to work on any of these other than uploading folders and files in Taxonomy?
Attaching couple of screenshots for better understanding.
We will have 1000s of accounts under each portfolio and each account will have 1 to 20 documents. Is it better to have taxonomy structure like this (above mentioned) or,
Here we have all files in same folder prefixing name of folders for each file.
For us it is more important that the performance is good while we do search or other operations using REST API.
Thanks in advance!
Production Configuration: OpenKM Community 6.3.8 | Windows Server 2016 | Intel (R) Xeon (R) CPU E5-2670 2.60GHz | RAM: 140GB | 16 Core | MySQL 5.7.14 | Virtualized