Maybe the data dictionary section 4 page 4-4 to 4-5 answers your
question? In my opinion indeed a file should not contain other files. It
can contain bitstreams though. I think in PREMIS terms, the zip file
does not _contain_ files within it, rather it's a transformation of the
files being compressed.
On Mon, 2006-10-09 at 06:08, Georg Buechler wrote:
> We've just been discussing a similar question, so thank you Youn for
> bringing this up!
> We decided to use PREMIS to record metadata in a digital preservation
> project with state archives in Switzerland. I should point out that
> this is really a very basic, pilot project, and that we are not using
> METS, which may be the cause of some of the problems we encountered.
> Namely, we are archiving data from a database-driven application. We
> plan to combine several plain-text data files, information about the
> data model, and other files into a zip-file. So we have a
> representation (the AIP in the current form) consisting of one file
> (the zip-file) which itself consists a couple of other files - there
> clearly is a hierarchy of files that is difficult to model in PREMIS.
> Example 3 in the PREMIS Data Dictionary (p. 3-34 sqq.) gives a hint of
> how to achieve this, namely through the use of the "relationship"
> semantic unit. However, this looks more like a workaround to me, as I
> understand a file cannot contain other files. Is this understanding
> correct? Or am I missing the actual point here?
> Thanks for any kind of clarification.
> Coordination Agency for the Preservation of Electronic Files
> c/o Swiss Federal Archives
> Archivstrasse 24
> 3003 Berne
> T/ +41 31 322 82 18
> F/ +41 31 322 78 32
> E/ [log in to unmask]
> W/ http://kost-ceco.ch/
> > -----Ursprüngliche Nachricht-----
> > Von: PREMIS Implementors Group Forum [mailto:[log in to unmask]] Im
> > Auftrag von Youn Noh
> > Gesendet: Samstag, 7. Oktober 2006 00:07
> > An: [log in to unmask]
> > Betreff: Re: [PIG] Upcoming revision of the PREMIS Data
> > Dictionary - call for participation
> > For repositories that aren't using METS, I'm wondering if it
> > might not be a good idea to make it possible to represent
> > structural relationships in PREMIS hierarchically by revising
> > the schema for the object entity so that relationship can be
> > a child of relationship.
> > Thank you,
> > Youn
> > Youn Noh
> > Digital Resources Catalog Librarian
> > Catalog Department
> > Yale University Library
> > P.O. Box 208240
> > New Haven, CT 06520-8240