Hi,
I've been looking into this area as we are writing our own METS
crosswalk file to incldue all the metadata our partner wants, and this
includes a structMap.
It does seem that some way of specifying the order of files is
necessary, but I'm not sure that expecting files to be named in
lexicographical order is the way to go - page01 coming before page02 is
fine for a scanned document but less easy for a longer born digital work
(such as a thesis) divided into chapters and related sections. Clearly
intro will then come after chapter01, chapter02 etc and appendixA will
come immediately after the abstract (!), unless you get the submitter to
rename the files.
It seems a simpler approach (from the user's point of view) to ask for
files to be specified in order, preferably also allowing the order to be
changed on editing the submission. No idea how complicated this is to
implement, but one possible approach is to have the ordering of the
files specified in the database. I imagine that the table that maps
bitstreams to item could add an order number.
The trouble is, of course, that this implies that all bitstreams are at
the same level of subdivision of the item, so it fails to manage items
where, say, illustrations are linked files, whose parent is a chapter.
This suggests that each bitstream is mapped to a parent, which is the
item if the bitstream is a top level subdivision or the bitstream(s?) if
it is a subivision or subsidiary part of a bitstream. For example,
chapter 1 of item 1 has item 1 as its parent, order place 1 (assume no
introduction!) and illustration 1 has chapter 1 as its parent, also
order place 1 while illustration 2 also has chapter 1 as its parent but
order place 2. This would map quite well to a METS structMap, where an
item can be subdivided to arbitrary depth. One further difficulty is
that the same item might have several places in the ordering. A web page
linked to from several other parts of the site springs to mind, but an
illustration might possibly appear (and so be linked with) several
chapters. Of course web sites are a different proposition in that there
need be no sequential ordering at all, they are navigated by following
links in any available order. Maybe an order place of zero could be used
to indicate such cases?
For what its worth our more detailed METS assumes a single layer of
subdivision of an item (e.g. into chapters or pages) and doesn't do
anything so rash as specify the order of the divs in the structMap. We'd
like to take this further but as the database doesn't support it we
can't.
Hope this verbosity is of interest,
Jon
http://ads.osdn.com/?ad_idv37&alloc_id 865&op=ick