Hello Thomas,

It is also my understanding that only <part> pertains to the guest (say, article) record, whereas all the rest can be pulled in from the host (say, periodical) record, as you assume. I think this is what <http://www.loc.gov/standards/mods/userguide/part.html> says.

We treat it like this: <https://github.com/eXist-db/tamboti/blob/master/modules/mods-common.xql#L2211>.

Best,

Jens

On Oct 21, 2013, at 3:25 PM, Thomas Scheffler <[log in to unmask]> wrote:

> Hi,
> 
> I am working on a repository that uses MODS not only as export or import
> format but also for internal storage.
> For performance reasons I want to keep data of parent objects redundant
> in child objects inside relatedItem[@type='host']. So whenever a parent
> objects metadata changes all children would be automatically updated.
> 
> So much for the theory. In practice however I need to flag each
> information if it was inherited or not at child level, e.g. an article
> was published inside a specific volume. Knowing this I can safely remove
> the old parent metadata and replace it by a new copy, if the parent was
> updated.
> 
> My question is: Can I always assume that child-level metadata (like page
> and volume numbers) inside <relatedItem> is always in <part> elements
> and all other elements are indeed inherited from the parent object?
> Maybe there are cases which I do not overlook at the moment.
> 
> kind regards,
> 
> Thomas Scheffler
> -- 
> Thomas Scheffler
> Friedrich-Schiller-Universität Jena
> Thüringer Universitäts- und Landesbibliothek
> Bibliotheksplatz 2
> 07743 Jena
> Phone: ++49 3641 940027
> FAX:   ++49 3641 940022