Date:Wed, 1 Sep 2004 16:20:46 -0500
Reply-To:Metadata Encoding and Transmission Standard
<[log in to unmask]>
Sender:Metadata Encoding and Transmission Standard
<[log in to unmask]>
From:"Riley, Jenn" <[log in to unmask]>
Subject:Re: More thoughts on <div> type
Comments:To: [log in to unmask]Content-Type:text/plain; charset="US-ASCII"
Hi all,
My thoughts on the need for something like a controlled vocabulary for
div/@type weren't that METS itself needed one, but that we needed one
for our specific implementation encoding digitized published books. I
interpret the interest we've seen in collaboratively developing a
vocabulary for this use is that other institutions have had this
internal need as well. If we develop a mutually agreed-upon vocabulary,
then we don't have to do it all individually, we can draw on the
collective expertise to determine what features of book-like objects are
important to be able to mark for special processing, and we'd increase
interoperability among our METS files for similar objects. Nobody would
be forced to use the vocabulary, it would just be a handy list to use
(or use as a starting point!) for local encoding guidelines. From the
responses I've gotten to my original query, it's clear that there are at
least beginnings of lists for this purpose in multiple places - a
collaboratively-developed list would simply allow us to reduce the
redunancy of effort for those who are interested.
Jenn
========================
Jenn Riley
Metadata Librarian
Digital Library Program
Indiana University - Bloomington
Main Library E170
(812) 856-5759
www.dlib.indiana.edu
> -----Original Message-----
> From: Metadata Encoding and Transmission Standard
> [mailto:[log in to unmask]] On Behalf Of Ruth Bogan
> Sent: Wednesday, September 01, 2004 4:00 PM
> To: [log in to unmask]
> Subject: [METS] More thoughts on <div> type
>
> I'm wondering if this is the best place for a controlled
> vocabulary. I understand why we might want to use <div> type
> as a trigger for a behavior, but for that couldn't you just
> use some generic designation, like 1-10 with locally defined
> meanings. I think developing a controlled vocabulary here
> imight be adding a layer of semantics to something that
> doesn't inherently need it.
>
> Ruth Bogan
>
> Ruth A. Bogan
> Head, Database and Catalog Portal Management Section
> Rutgers, the State University of New Jersey
> 47 Davidson Road, Busch Campus
> Piscataway, NJ 08854-5603
> Ph.: 732-445-5906
> Fax: 732-445-5888
> Email: [log in to unmask]
>
>
> > ----- Original Message -----
> > From: "Tim Au Yeung" <[log in to unmask]>
> > To: <[log in to unmask]>
> > Sent: Wednesday, September 01, 2004 3:52 PM
> > Subject: Re: [METS] list of <div> types in structMap
> >
> >
> > Hi Nancy,
> >
> > This sounds like a great idea. We're currently working on our book
> > system here. I'm not sure how much we can contribute but
> I'd certainly
> > be interested.
> >
> > Tim
> > ---------------------------------
> > Tim Au Yeung
> > Manager, Digital Object Repository Technologies Information
> Resources
> > University of Calgary
> >
> > -----Original Message-----
> > From: Metadata Encoding and Transmission Standard
> > [mailto:[log in to unmask]] On Behalf Of Nancy Hoebelheinrich
> > Sent: Wednesday, September 01, 2004 12:30 PM
> > To: [log in to unmask]
> > Subject: Re: [METS] list of <div> types in structMap
> >
> > Jenn:
> > While I don't believe I've seen anyone register a METS
> Profile which
> > includes a controlled vocabulary for the TYPE attribute to
> the <div>
> > as
> you
> > describe, I think you raise a very important point /
> opportunity for
> > the METS community. At the last(?) DLF meeting, there was a
> > significant
> amount
> > of interest in coming to agreement on just such a controlled
> > vocabulary
> from
> > a number of institutions, but to my knowledge, nothing yet has been
> > done about it. I know that there are a number of institutions /
> > organizations which have "their" own lists who could
> contribute them
> > possibly, such as Harvard, I believe -- those who are REALLY in the
> > know at Harvard could verify perhaps? and Stanford with a
> meager list
> > at the moment, but also CCS, the company which has the
> docWorks/METAe product / service has a very
> > comprehensive list which they might be willing to share. With what
> Indiana
> > also has as one of the starting points, perhaps a small group of
> interested
> > parties from the METS community could get together offline from the
> > METS list and draft / propose such a controlled vocabulary,
> > particularly for sequentially read, book-like objects which
> we could
> > then list on the METS site? Anyone interested in this relatively
> > minor, but important task? If so, please either respond
> via the METS
> > list, or contact me personally at [log in to unmask]
> > Nancy
> >
> > ****************************************************
> > Metadata Coordinator
> > Cataloging and Metadata Services Dept
> > 3rd Floor, Meyer Libr
> > Stanford Univ Librs/Acad Info Rsrcs
> > Stanford CA 94305-6004
> > phone: 650.725.6843 fax: 650.725.1120 [log in to unmask]
> >
> > -----Original Message-----
> > From: Metadata Encoding and Transmission Standard
> > [mailto:[log in to unmask]]On Behalf Of Riley, Jenn
> > Sent: Tuesday, August 31, 2004 11:00 AM
> > To: [log in to unmask]
> > Subject: [METS] list of <div> types in structMap
> >
> >
> > Hello all-
> >
> > Here at Indiana University we're working to develop a page-turning
> > application for digital objects (right now just digital images of
> > books, sheet music, etc. - anything that should be displayed in a
> > sequence) that runs off of METS files. We're starting with a set of
> > brittle books scanned by our Preservation department.
> >
> > These books have been previously available as PDF files,
> and bookmarks
> > were added to these files showing a single-level
> rudimentary strucutre.
> > The department that created these PDF files developed some
> guidelines
> > as to what features of the book should be labeled with bookmarks
> > (things like Chapter, Dedication, Frontispiece, Map, Plate,
> Preface,
> > Title Page). In practice these were used not so much as a
> controlled
> > vocabulary from which to choose labels, but as a guideline for what
> > features to mark. The acutal text used for the bookmarks
> varied widely.
> >
> > In translating this practice to a METS structMap, we're putting the
> > text formerly in a PDF bookmark into the structMap <div LABEL="">
> > atribute (e.g., <div LABEL="I. I am Born.">). This is what will
> > display to the user, so the basic functionality in the PDF files is
> > now repeated. But I think we can and probably should go a
> bit further
> > and use the <div TYPE=""> attribute as a means of recording strings
> > more meaningful to the page-turning applications than the LABEL
> > attribue strings. Although METS of course doesn't limit
> values of the
> > TYPE attribute to any particular list (and for good reason), I'm
> > thinking that I'd like to have a finite list of strings that we use
> > locally for this project in the <div TYPE=""> attribute, to
> allow us
> > to maintain consistency in METS docs and perhaps to allow the
> > page-turning application to do something intelligent with them
> > (generate lists of illustrations, etc.) TEI has a similar div/@type
> > mechanism, but it also allows any string to be used in the type
> > attribute. I could use our list developed locally for
> adding PDF bookmarks as a starting point, but it would
> definitely need work.
> > I'd be interested in hearing how others have approached this. Has
> > anyone developed a list of <div TYPE=""> attributes for book-like
> > objects (in a METS Profile or elsewhere) for use in a particular
> > project that they'd be willing to share?
> >
> > Thanks!
> >
> > Jenn
> >
> >
> > ========================
> > Jenn Riley
> > Metadata Librarian
> > Digital Library Program
> > Indiana University - Bloomington
> > Main Library E170
> > (812) 856-5759
> > www.dlib.indiana.edu
> >
>
