[Koha] Biblio records as book set "container" records - hierarchical groupings

[Hans Henderson]

OK, to continue back on-list with this last bit:

> Another way to handle it, with analytics, would be to have brief 
but complete records for all the 'elements' of the set, and a 
'master' record that listed (say in a 505 and with 700s) all the 
elements that make up the set.

So a "dummy" Biblio record that doesn't point to a specific resource, 
but provides links to all the various other "real" Biblios that are 
related. Would these be actual "links" in the www sense, so a user 
could click to pull up the Biblio listing, e.g. make a reservation 
and then navigate back to the parent record, click to open the next 
Biblio they wanted to reserve, etc?

If the display just provided a text listing showing what related 
resources were available, then they'd have to launch a separate 
search for each one, bit of a PITA. . .

The big question remains (addressed to whoever can answer, not Steven 
specifically - will coding these relationships in the MARC records 
prior to import help Koha tie the various Biblioitem records together 
to their common "master" Biblios? Is there any field content 
"matching" going on during the import?

Or will they just all come in as separate Biblios?

And if the latter, is there a way to tie them together after the 
import?

Thanks in advance. . .

Hans