A Jain version of the story says that six blind men were asked to determine what an elephant looked like by feeling different parts of the elephant's body. The blind man who feels a leg says the elephant is like a pillar; the one who feels the tail says the elephant is like a rope; the one who feels the trunk says the elephant is like a tree branch; the one who feels the ear says the elephant is like a hand fan; the one who feels the belly says the elephant is like a wall; and the one who feels the tusk says the elephant is like a solid pipe. A wise man explains to them: &quot;All of you are right. The reason every one of you is telling it differently is because each one of you touched the different part of the elephant. So, actually the elephant has all the features you mentioned.&quot;
Modelling relations, hierarchical or otherwise, is difficult in ESE.
The Rhine portal has no inherent ability to display objects as part of relations, sequences, or hierararchies. Series are “simulated” by creative ESE-mapping.
Hierarchical relations can be modelled in EDM with subordinate objects able to be sequenced
Part of relations
Is there a need for clearer rules, guidelines or best practices for how to map to EDM and preserve relations and hierarchies?
Not really for me to decide. Anyone in the audience?
Hierarchical objects in a search result. The sub-objects should not be individually displayed in search results but their metadata indexed and searchable.
Hierarchical object view 1
Hierarchical object view 2. Should there be a max limit to the number of sub-objects related to a mother object?
Hierarchical object search and display is a priority feature for the Danube release of Europeana Paintings by Arthur Rackham. Not found in Europeana. Will be followed by smaller releases in tighter intervals
Hierarchical objects in Europeana David Haskiya Product Developer Meeting on hierarchical objects, September 16 2010
A lot of things are best understood in context Photo by Pawyilee