> Regarding the non-roman data in your MODS records, I wonder if
> <extension> is merely a storage place for that data, or if it is used in
> a functional way for indexing or display in your systems?
We are using <extension> as a storage place, but you can see how we
display the non-roman data contained in it here:
We use MODS as a way of holding the data for display and export
(into a variety of formats via XSL Transformations.) Indexing is
> The MARC $6
> feature permits a field-specific ability to toggle roman and non-roman
> data in a user display -- would a similar feature in MODS be useful for
> you (and other MODS implementors)?
I'm not sure we would use such a facility -- even though the MARC21
records we create the MODS record from have the $6 data.
> Joe Altimus
> Metadata Librarian
> Arizona State University Libraries
> On Wed, Aug 12, 2009 at 1:59 AM, Ashley Sanders
> <[log in to unmask] <mailto:[log in to unmask]>> wrote:
> 1) What type of data are you currently putting in the top-level
> <extension> element?
> We use the <extension> element for local holdings info and for non-roman
> data. If a MARC record contains 880 fields, then we create a second
> <mods> element using the 880s and stick it in <extension>. You can
> see an example here:
> 2) Do you have specific cases in which it would be helpful to
> you to have <extension> inside a specific MODS element rather
> than at the top level to convey additional semantics?
> 3) Have you made changes to the MODS schema locally to allow for
> additional elements not in the MODS schema?
> Ashley Sanders [log in to unmask]
> <mailto:[log in to unmask]>
> Copac http://copac.ac.uk A Mimas service funded by JISC
Ashley Sanders [log in to unmask]
Copac http://copac.ac.uk A Mimas service funded by JISC