Using Laserfiche and IBM FileNet as examples
When working with enterprise content management (ECM) systems like Laserfiche or IBM FileNet, it’s very common to notice something that looks confusing at first:
You create one folder… but you see two “entries”:
One related to the folder itself One related to the template (metadata / class / document type)
This is not a bug — it is by design, and it reflects how ECM systems separate structure from information.
1. The Core Concept: Structure vs Metadata
ECM systems manage two different things:
1. Folder / Document (Structure)
This is:
The physical or logical container Where content lives The hierarchy (parent / child folders)
2. Template / Class (Metadata Layer)
This defines:
Fields (Name, ID, Status, Date…) Rules and validation Business meaning
👉 So when you create a folder:
One entry = the folder object One entry = the metadata definition attached to it
2. How It Works in Laserfiche
In Laserfiche:
A folder is created in the repository A template is assigned to that folder
What you may see:
Folder name in the repository Template fields panel (metadata)
Sometimes, especially in workflows or searches, it feels like two entries because:
The system tracks entry ID (folder) And template data (metadata record)
👉 Example:
You create:
“Loan_12345” folder
Entry 1 → Folder (Loan_12345) Entry 2 → Template data (Loan Template fields like CustomerName, Amount, Status)
3. How It Works in IBM FileNet
In IBM FileNet, this separation is even more explicit:
Folder object → stored as a container Class (Document Class / Folder Class) → defines metadata
Additionally:
Metadata is stored in database tables The folder is an object with properties
👉 So internally:
One record = object (folder) Another representation = properties (class-based metadata)
This can appear as two entries in:
Queries API responses Search results
4. Why Systems Are Designed This Way
1. Flexibility
You can:
Change templates without moving folders Apply different metadata to similar structures
2. Scalability
Metadata is indexed separately:
Faster search Better reporting
3. Governance
Clear separation allows:
Audit trails Versioning Security at multiple levels
5. Common Situations Where You Notice “Two Entries”
You may observe this behavior when:
Running search queries Using workflow tokens (Entry ID vs Field values) Viewing results in integrations / APIs Designing reports
👉 Example:
A query returns:
EntryID (folder) Field values (template)
It looks like duplication — but it’s actually two layers of the same object.
6. Important Insight for Architects
This is where many engineers get confused.
They think:
“Why do I have duplicates?”
But the correct understanding is:
“I have one object with two dimensions: structure and metadata.”
Final Thought
In ECM systems like Laserfiche and IBM FileNet:
The folder is the container The template is the meaning
Seeing “two entries” is simply the system showing you both.
And once you understand this, you start thinking like an architect:
Separate structure from meaning — and your system becomes clean, scalable, and powerful.