LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

PIG Home

PIG Home

PIG  August 2006

PIG August 2006

Subject:

Re: Premis questions from the KB

From:

Priscilla Caplan <[log in to unmask]>

Reply-To:

PREMIS Implementors Group Forum <[log in to unmask]>

Date:

Mon, 14 Aug 2006 11:29:00 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (121 lines)

This is Priscilla. I can answer some of these from my perpective but I
would be interested in hearing what others have to say.

Regarding #1, Premis definition of representation. You say "The DAIS
principle is 1 object = 1 AIP". I don't know what you mean by object in
this context. The PREMIS definitions of types of objects as files,
bitstreams or representations is meant to force us to be more specific
when we talk about objects. Say you were ingesting an ejournal article
that existed in two versions: 1) a single PDF file, 2) an SGML file, a
jpg image and 3 gifs. What would be in the AIP(s)?

REgarding #2, this is really interesting. You could do this in
Preservation level by "flattening" the values, so that each set of
characteristics to be preserved together would be assigned a
preservationLevel value. But we admitted that preservationLevel is
really a business rule and so ought to be out of scope for the PREMIS
data dictionary. I expect that many repositories will have much more
complicated rules than can be expressed in preservationLevel.

Regarding #3, creatingApplication. This is applicable to Files as well
as Representations, so it is fine if you only want to use it for Files.
  If I remember correctly, the reason this was made applicable to
Representations is because some applications output sets of files that
together constitute a representation. For example, Dreamweaver could be
considered the creatingApplication for a web page which itself consists
of several files, each of which have their own creatingApplication.
Flash might be another example (I don't know Flash well enough to say).

Regarding #4, use of an object. The use of most objects would be to
display or play them or otherwise render them to a user. But some
objects might be meant to be processed by program, for example an
executable file (computer code) is used by executing it, a SAS file is
used by the SAS statistical program, etc.

Regarding #5, linkingEventIdentifier. This is applicable to Files so if
you want to use it only for events that pertain to file (like virus
checking, format validation, etc.) that is fine.

Regarding #6, good idea. This might be an enhancement we could make for
the next edition.

p

Barbara Sierman wrote:
> Hello all,
>
> During the last months we at the KB in Holland studied the Premis Data
> Dictionary. In our e-Depot we use metadata, but when we started with the
> e-Depot the Premis Data Dictionary did not exist. So a comparison was
> made between the Premis data elements and our e-Depot system (DIAS from
> IBM). Our DIAS system will be upgraded to the next version so it is a
> good opportunity to study the data model . Most of the Premis elements
> will be relevant for us too. However some questions were left and I
> would like your opinion on the following:
>
> 1. Premis definition of Representation: a set of files, including
> structural metadata, needed for a complete and reasonable rendition of
> an Intellectual Entity.
> DIAS principle is 1 object = 1 AIP. If an object has a relation with
> other objects the relevant information in the bibliographical metadata
> will create the Intellectual Entity. So Representation Information will,
> as far as we know now, always concern one object.
>
> 2. Preservation Level:
> At this moment in our DIAS system all objects have the same preservation
> level, we do not make a distinction. This might change in the future. As
> a result of our study into migration we have some new thoughts and I
> would like to share them with you. We think that it will become
> important to register information about the 5 main characteristics of an
> object (content, context, structure, behaviour and appearance) and to
> add the preservation level of each of these characteristics. We have not
> decided whether we would like to do this on object level (hardly
> possible) but we think in terms of "class of objects "and "collections"
> with a certain set of characteristics that should be preserved, for
> example a collection of pfds where the text is more important than the
> illustrations opposite to a collection of pdfs where the font of the
> text is of no importance but the illustrations are.
> I must confess these are thoughts and we are still discussing it.
>
> 3. Representation: creatingApplication
> In my opinion this element belongs to the File section and not to the
> Representation section, as it is the Application that created the file,
> despite the representation of the file.
>
> 4. Representation and File; "use of an object"
> In both Representation and File the expression "use of an object"
> appears frequently, sometimes in connection with modifying the object by
> the end-user. To me it is not clear what is meant by "the use of an
> object". In our current situation we do not see any other use of the
> object than an end user who is allowed to see or read the object
> (perhaps download it but that is use outside our e-Depot). As curators
> of the e-Depot we also "use" objects, for migration and emulation for
> example. That is the only use we can think of. Did we miss a point here?
>
> 5. Representation: linkingEventIdentifier
> According to the explanation of this element, events like format
> validation and virus checking may be registred here. In our opinion this
> is not Representation information but File information.
>
> 6. One practical point: I numbered all the elements (1, 1.1, 1.1.1 etc),
> which make them easier to trace in the Dictionary.
>
> I look forward to your reactions and will thank you very much in
> advance.
>
> Kind regards,
>
>
> Barbara Sierman
> Digital Preservation Officer
>
> Koninklijke Bibliotheek
> PO Box 90407
> 2509 LK Den Haag, The Netherlands
>
> +31 70 3140109
> [log in to unmask]
>
> www.kb.nl
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2024
January 2024
December 2023
August 2023
July 2023
June 2023
March 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
May 2022
April 2022
January 2022
December 2021
October 2021
August 2021
July 2021
June 2021
April 2021
March 2021
January 2021
December 2020
September 2020
August 2020
July 2020
June 2020
April 2020
February 2020
December 2019
November 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager