Short answer
Design systems for cultural heritage data to support many-to-many relationships and explicitly model uncertainty, rather than forcing one-to-one mappings.
- Field
- User-Centred Design
- Source
- Journal of Documentation (2026)
- Method
- Case Study
- Evidence
- Moderate effect
Direct, one-to-one mapping of entities is insufficient for reconciling diverse cultural heritage records due to inherent ambiguities, incomplete data, and varying cataloguing traditions. This user-centred design research insight is drawn from a 2026 study published in Journal of Documentation. Using Case study, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Design systems for cultural heritage data to support many-to-many relationships and explicitly model uncertainty, rather than forcing one-to-one mappings.
Entity reconciliation in cultural heritage requires flexible, many-to-many modelling to accommodate inherent data ambiguity.
Direct, one-to-one mapping of entities is insufficient for reconciling diverse cultural heritage records due to inherent ambiguities, incomplete data, and varying cataloguing traditions.
Journal of Documentation · 2026
Key Findings
- 01Entity reconciliation is rarely a one-to-one operation.
- 02Ambiguities, incomplete data, shifting attributions, and varying practices significantly shape reconciliation outcomes.
- 03Observed strategies include creating anonymous/collective entities, using umbrella terms, adding uncertainty qualifiers, and acknowledging unresolvable ambiguity.
Application
Design takeaway
Design systems for cultural heritage data to support many-to-many relationships and explicitly model uncertainty, rather than forcing one-to-one mappings.
How to apply
When designing a database for historical documents, allow for multiple authors, multiple subjects, and multiple locations to be associated with a single document.
Project actions
- 01Consider how your design will handle situations where a single input relates to multiple outputs, or vice versa.
- 02Think about how to visually represent uncertainty or multiple connections in your user interface.
Method & Evidence
Variables
Strengths & Limitations
Strengths
- +Focuses on a real-world, complex problem in digital humanities.
- +Provides practical strategies observed in practice.
Limitations
The complexity of implementing a true many-to-many database structure can be a significant technical challenge for a design project.
Reliability & validity
The study's validity is strengthened by its focus on real-world case studies within specific institutional contexts. Reliability could be enhanced by a larger, more diverse sample of institutions and data types.
Think critically
How might the 'many-to-many' nature of entity reconciliation impact the user experience and the perceived trustworthiness of the information presented?
Design Principles
"Embrace ambiguity: Design systems that can represent and manage uncertainty and complex relationships, rather than assuming perfect, singular data."
This research highlights a critical usability challenge in digital humanities and cultural heritage informatics. Designers of databases, archival systems, and research platforms must move beyond simplistic data models to accommodate the complex, often non-linear relationships found in real-world historical data.
What This Means for Your Design
When you're trying to link up information from different places, like photos and art descriptions, it's not always a simple one-to-one match. Sometimes one photo can relate to many artworks, or one artwork can have many photos. You need to design your system to handle these 'many-to-many' connections and show when information isn't perfectly clear.
How to use in your project
- 1.Reference this study when discussing the challenges of data modelling or user interface design for complex datasets.
- 2.Use the findings to justify the need for flexible relationship types in your proposed design solution.
Add to My Project
Quick Cite
Paragraph starter
This design project acknowledges the inherent complexities in data reconciliation, drawing upon research that highlights the inadequacy of one-to-one mapping for heterogeneous records (Daquino, Mambelli, & Kozlov, 2026). The findings suggest that systems must be designed to accommodate many-to-many relationships and explicitly model uncertainty to effectively manage ambiguous or incomplete data, a principle that will guide the development of the proposed solution.
Source
Journal of Documentation
Many-to-many. Usability challenges of entity reconciliation in art history and photographic studies
journal · 2026
View sourceQuestions About This Research
- What does the research say about entity reconciliation in cultural heritage requires flexible, many-to-many modelling to accommodate inherent data ambiguity?
- Design systems for cultural heritage data to support many-to-many relationships and explicitly model uncertainty, rather than forcing one-to-one mappings. Evidence: Journal of Documentation (2026).
- Why does "Entity reconciliation in cultural heritage requires flexible, many-to-many modelling to accommodate inherent data ambiguity." matter for design?
- This research highlights a critical usability challenge in digital humanities and cultural heritage informatics. Designers of databases, archival systems, and research platforms must move beyond simplistic data models to accommodate the complex, often non-linear relationships found in real-world historical data.
- How can designers apply this research?
- Design systems for cultural heritage data to support many-to-many relationships and explicitly model uncertainty, rather than forcing one-to-one mappings.
- What were the main findings?
- Entity reconciliation is rarely a one-to-one operation.. Ambiguities, incomplete data, shifting attributions, and varying practices significantly shape reconciliation outcomes.. Observed strategies include creating anonymous/collective entities, using umbrella terms, adding uncertainty qualifiers, and acknowledging unresolvable ambiguity.
- What research method was used?
- Case Study.
- How strong is the evidence?
- Evidence strength is rated Moderate effect, based on a 2026 journal from Journal of Documentation.
- What should I do differently in my next project?
- When designing a database for historical documents, allow for multiple authors, multiple subjects, and multiple locations to be associated with a single document.
- What are the limitations?
- The study focuses on art historical photo archives, and findings may not directly translate to all types of cultural heritage data.