thanks for your quick answer.
Jerome McDonough schrieb:
> While METS doesn't *insist* that you encode structure
> within the structural map down to the page level of an
> item, equally it doesn't forbid it.
I see - well, but somehow this is just another kind of work-around. In
the area of metadata storage METS is following a real good concept in
separating Descriptive from Administrative Metadata.
I think, METS should follow the same principles regarding the structure
of a work.
A printed work has always two separate strucutres: A logical structure
(book, chapters, articles) and a physical structure (pages or even
page-areas , columns etc...). You have two different kind of structures
(as you also have two different kinds of metadata) - therefore it would
be a much buetter solution to store them separatly.
< A structmap with
> levels like
> <div type='book'>
> <div type='chapter'>
> <div type='page'>
This example works quite well for simple structures as you will find in
some books. But unfortunately you'll get many, many exeptions: A page
may belong to one OR MORE logical structures (e.g. a chapter ending on a
page; the next one begins on the same page).
In newspapers you'll often find articles beginning on page 1 and have a
their continuation on page three.
Following your suggestion, we would get something like (in the case a
chapter ends on the same page where the next chapter starts):
<div type="book" id="0001">
<div type="chapter" id="0002">
<div type="page" id="0003"/>
<div type="page" id="0004"/>
<div type="page" id="0005"/>
<div type="chapter" id="0006">
<div type="page" id="0005"/>
<div type="page" id="0007"/>
This is a very bad soluton, because
a) if the id-attribute is a real (XML-)ID, we can't use it twice to
identify the same page ( page with id=0005 in the example)
b) we have to store information redundantly (e.g. pointing from "both"
div type="page" id="0005" to the same metadata section....
I would suggest to have two structMap sections: One for logical and one
for physical structure. When I understood the METS-schema correctly, I
may have several structMap-sections and may even use the type-attribute
witht he values "PHYSICAL" and "LOGICAL".
The question is: How may I point from one div in one structMap section
to another div (in the physical structMap section)?
> Once you have a page level element within the structural map,
> you can address the points you raise,
Yes.... So it was a good hint, to point me to the structMap-section. As
you see, there are several possibilites to store page numbers :-)
Maybe you should add a appropriate chapter to the METS-introduction to
describe the recommended way how single pages may be stored in METS.
> which I interpret as
> follows: 1. a need to indicate a machine-processable page order
> (basically an integer for each page as well as a human-readable
> page order (page xii, etc.); and
> 2. a need to associate metadata
> with a page element regardless of whether there is actual a file
> or files for that page element. Both of these are possible
> within METS as it stands.
> pages and page iii holds a dedication, you might have a div as follows:
> <div ORDER='7' ORDERLABEL='iii' LABEL='Dedication'>.
This is even better than storing this information as metadata. :-)
> Finally, I should note that just because you have a <div>
> within a structural map doesn't mean you *have* to have a
> corresponding file.
That's necessary, yes. Otherwise I would not be able to store pages but
just have files on chapter level etc...
Markus Enders, GDZ