Dear colleagues from PREMIS,
as you perhaps know we have started to implement a long term archiving system based on the DIAS-solution of IBM/KB Netherlands for cooperative and distributed approaches. "KOPAL - Co-operative development of a long-term digital information archive" is a German implementation project for a digital archive according to the OAIS reference model [http://nestor.sub.uni-goettingen.de/allg/detail.php?show=657&lang=en]. Together with IBM, the SUB Göttingen and the GWDG (also Göttingen) we have defined a generic data-model to organize a valuable object description and we are now on the way to enhance the existing data-holding structure. Our activities are based on LMER (Long-term preservation metadata for electronic resources, http://www.ddb.de/standards/lmer/ ) which is based on the model by National Library of New Zealand (NLNZ).
With this background the initiative of PREMIS in the context of DCMI is very important for us and I am looking forward to having more and concrete contacts to your activities - as a step forward to implementation of running solutions.
Because the deadline for feedback is coming soon, I want to submit some pre-release comments on PREMIS final report and data dictionary by Tobias Steinke and Hans Liegmann, who both belong to the KOPAL project staff:
Tobias Steinke ([log in to unmask]) writes:
As you may already know, KOPAL will implement
- The Final Report gives a very interesting view of the discussion within the Working Group. Maybe you should explain more in detail your very generically concept of an object. The view of an object by LMER and NLNZ as a logical unit is more straight forward, but I see the advantages of having a unique concept for what you call representations and files on one hand and something like an intellectual entity on the other hand. Maybe your key concept of an object will become clearer by different examples.
- In the introduction you say the group preferred to use the term "semantic unit" rather than "metadata element". I think it's a bit difficult to think only in semantic units. The metadata elements in an exchange format (for SIP and DIP) should be usable for other purposes than the metadata within the data management (representation as data model). E.g. in a DIP I want to see the history of all migrations leading to this package and to get references to the former incarnations. Within the data management you only need to associate the last event. In case of an access you are able to rebuild the history for the DIP.
- I think the semantic unit storageMedium is not relevant as preservation data. The long-term preservation of files should be independent of the current storage medium. You should seperate data about binary data (files, bitstreams, filestreams) and physical entities.
- For me one of the key elements is format and I like your units dealing with this. As format registries are very important for the use of preservation metadata in general you should explain and stress this concept more in detail.
Hans Liegmann ([log in to unmask]) writes:
- I appreciate very much the results of the PREMIS working group. As a generic model of semantic units, the data dictionary has to be tested and evaluated now pilot implementations. KOPAL will be one of these implementations and should look very close at compatibility issues in the near future.
- I agree to Tobias Steinke that "storageMedium" is not relevant as preservation metadata. Inside attributes of the OAIS entity "Archival Storage" should be hidden from the outside world.
- It would be helpful to have the graphical representation of the PREMIS data model more elaborated. The entity "objects" should be displayed in a structure together with its subtypes file, bitstream and representation.
Best regards
Reinhard Altenhöner
Reinhard Altenhöner
Die Deutsche Bibliothek
Overall Project Manager KOPAL
Head IT-department
Adickesallee 1
D-60322 Frankfurt am Main
Telefon: +49-69-1525-1700
Telefax: +49-69-1525-1799
mailto:[log in to unmask]
http://www.ddb.de
>-----Ursprüngliche Nachricht-----
>Von: DCMI Preservation Working Group
>[mailto:[log in to unmask]] Im Auftrag von Rebecca
>S. Guenther
>Gesendet: Donnerstag, 17. Februar 2005 23:20
>An: [log in to unmask]
>Betreff: Reminder: PREMIS final report and data dictionary
>
>
>This is a reminder that comments are due on the PREMIS work
>next week. Original date was Feb. 21, but we will extend that
>until Fri. Feb. 25.
>
>There is now a section on the PREMIS final report page that
>lists the changes that we know are needed in the final report
>and data dictionary.
>
>Thank you for your input.
>
>Rebecca ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>^^ Rebecca S. Guenther ^^
>^^ Senior Networking and Standards Specialist ^^
>^^ Network Development and MARC Standards Office ^^
>^^ 1st and Independence Ave. SE ^^
>^^ Library of Congress ^^
>^^ Washington, DC 20540-4402 ^^
>^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
>^^ [log in to unmask] ^^
>^^ ^^
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>---------- Forwarded message ----------
>Date: Tue, 1 Feb 2005 17:27:37 -0500 (EST)
>From: Rebecca S. Guenther <[log in to unmask]>
>Subject: PREMIS final report and data dictionary
>
>We are pleased to announce the initial completion of the
>PREMIS final report and data dictionary. These documents are
>for review by the PREMIS Working Group, Advisory Commitee, and
>other invited experts before a more general world-wide review.
>The documents still require final editing and formatting.
>There are 3 documents:
>
>1. PREMIS Final Report
>This narrative gives a summary of the activities of the PREMIS
>working group and is an introduction to the PREMIS data
>dictionary. It explains many of the decisions that the Core
>elements subgroup made when developing the data dictionary,
>details the data model used, and defines terminology. It
>should be read prior to reviewing the data dictionary.
>
>2. PREMIS Data Dictionary
>This document is a complete specification of data elements
>(called "semantic units") that make up this core preservation
>metadata element set. It includes element names, definitions,
>applicability, repeatability, obligation, examples,
>creation/maintenance notes, and usage notes. The data
>dictionary is organized by type of entity, as explained in the
>data model.
>
>3. Examples
>There will be selected full examples for various types of
>digital objects. This section is not yet completed, but will
>be shortly. We will announce the availability of the examples
>in a separate message.
>
>To access the documents go to:
>http://premis.lib.uchicago.edu:8888/premis
>This site is
>password protected.
>Login: premis
>Password: promise
>Then click on Review Draft of PREMIS Final Report
>
>How to send comments
>Comments may be sent to this list (premis-all or DC
>preservation). If you prefer, you may send personally to
>Rebecca Guenther ([log in to unmask]) and Priscilla Caplan ([log in to unmask]).
>
>Deadline
>Please send all comments within 3 weeks, by Feb. 21.
>
>Thank you all for your participation.
>
|
