...
Even though the architecture is flexible i.e. at the time of setup implementors can specify the content hierarchy of the data, the default content hierarchy has been setup assuming three levels i.e document category, document type and document forma as shown in the diagram below;
| 1 - Denotes the 1st level of content hierarchy under the root node which represents document categories. Here its is "Work"
2 - Denotes the 2nd level which represents the document types such as "Bibliographic" and "Instance"
3 - Denotes the 3rd level which represents the document formats such as "MARC" and "Dublin-core" for Bibliographic records and "OLEML" (OLE defined) for Instance records. |
| L1 - This denotes level 1 - Denotes the content hierarchy under the MARC node
2 - Denotes a 2nd level of MARC nodes
3 - Denotes the nodes that will hold the actual MARC records where you can have up to 1K nodes.
L2 - This denotes level 2 where you can have up to 1k nodes.
L3 - This denotes level 3 where you can have up to 1K nodes.
|
| Info |
|---|
| title | Total number of records at L1 |
|---|
|
Jackrabbit recommends small number of nodes per parent node for efficiency.
The total number of nodes (i.e. resulting number of files) that can be accommodated at L1 is 100M with possibility of being able to add more) |
|