Sheesh... serves me right for not reading ALL my mail before replying to
ANY of it... here's a quick comment to complement my previous posting in
reply to the inheritance issue...
In the granularity report, you(s) suggest:
Apart from the relation tag the "child" may get full metadata itself
or it may derive its metadata from the
"parent" document. The decision is made by the information provider.
SURFnet SE will derive the
metadata from the "parent" document, unless the "child" has its own
metadata. In other words:
metadata of the "child" document will overrule those in the "parent"
document. This applies exclusively to
the complete set of metadata: either the metadata will be derived
from the "child", if the "child' has no
metadata (apart from the relation-element which is necessary to
identify the "parent"), the other
metadata will be derived from the "parent." It won't be possible to
derive some of the metadata from the
"child" and add only the lacking elements from the "parent"
This is okay, as long as the entity assigning the metadata is thorough.
Treating each and every document as a separate entity requiring its own
complete metadata is the best way to go, rather than approaching the meta
data tagging with the attitude "oh... the parent says this, so I don't need
to say it again here...".
In the granularity report, you(s) suggest:
There are various options to use the information in the relation tag
to manipulate query results:
Perhaps another method (in addition to/complementary to/instead of the
three you've listed) is to "rank" the documents based on the search
criteria. Then pick the entity (parent, child, grandchild document) that
*best* matches the search criteria. You might return, for example, a record
looking like:
Rank 2 (63%) - "Section 2.2 - Application for Membership" - (summary of
document here) - text/html - 1504 bytes - part of document "Constitution of
OrganisationName"
There the "part of document" link has been calculated by following the
"IsPartOf" to a leaf node. My theory being that any properly constructed
document should be thoroughly linked internally (eg: Prev | Up | Next ).
The pick out the DC.Title of the top parent document and stick it in using
something like... sprintf( "Part of document %s.\n", $Top_Parent_Title);
Regards,
Alex Satrapa
Marianne Peereboom wrote:
> ...Recenly a report has been made available on the DONOR website about
> the
> granularity issue. This report contains a proposal to use
> DC.Relation.IsPartOf to specify
> parent/child relationships between (parts of) documents.
>
> The report is available at
> http://www.konbib.nl/donor/index-en.html
> (under reports)
> The URL of the document itself is:
> http://www.konbib.nl/donor/rapporten/granularity.html
|