LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG Archives


PIG@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

PIG Home

PIG Home

PIG  January 2007

PIG January 2007

Subject:

Re: Revision of the PREMIS Data Dictionary - call for comments: significantProperties and preservationLevel

From:

Gerard Clifton <[log in to unmask]>

Reply-To:

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

Date:

Wed, 31 Jan 2007 17:14:46 +1100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (236 lines)

Thanks for these further comments. The Editorial Committee has not
considered making environment a separate entity, but I can raise it for
consideration.

Depending on your implementation, I can imagine that you could indeed
capture specific environment metadata once, as you suggest, and link to
it from the relevant objects. PREMIS doesn't specify how you should
store the metadata within your repository; it just describes what
metadata should be known and, through the schemas, how this metadata can
be expressed in a standard way for exchange or interoperability. 

So, you could store specific environment information (or any other
metadata) just once in your database in whatever form is applicable to
your implementation, link it to the relevant objects and only bring it
together with the rest of the object metadata to output to a PREMIS
schema when you need to. I don't believe there is a requirement to store
the metadata in a PREMIS document.

I expect that this could also apply to the proposed 'policy' entity, so
we would need to further consider if there are advantages to separating
it off.

Regards,
Gerard Clifton
Digital Preservation
National Library of Australia, Canberra ACT 2600 Australia
t: +61 2 6262 1381 | f: +61 2 6273 2545 | e: [log in to unmask]


-----Original Message-----
From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On Behalf Of
Steinke, Tobias
Sent: Friday, 26 January 2007 10:02 PM
To: [log in to unmask]
Subject: Re: [PIG] Revision of the PREMIS Data Dictionary - call for
comments: significantProperties and preservationLevel

If we talk about technical environments, this should be covered by an
advanced (inter)national file format registry. If these environment
information would be within in your archival system, you would have to
put it in every individual object anyhow in case of an exchange with
other archival systems.

You are right about the significantProperties being pretty subjective -
but subjective in context of the policy of an archiving institution! It
should be possible to separate this "subjective" information easily from
the essential object information in case of an exchange with another
archiving institution. E.g. the exact same document could be archived by
a library and by an archive. For the library significant properties may
be totally different and therefore the migration strategy could be
different - although it is the same object.

Best regards,
Tobias

--
Tobias Steinke
Deutsche Nationalbibliothek
Informationstechnik
Adickesallee 1
D-60322 Frankfurt am Main
Telefon: +49-69-1525-1762
Telefax: +49-69-1525-1799
mailto:[log in to unmask]
http://www.d-nb.de




> -----Original Message-----
> From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On 
> Behalf Of Susan Thomas
> Sent: Friday, January 26, 2007 10:43 AM
> To: [log in to unmask]
> Subject: Re: [PIG] Revision of the PREMIS Data Dictionary - 
> call for comments: significantProperties and preservationLevel
> 
> Hi,
> 
> I think "significantProperties" should remain with the object 
> - it can 
> be pretty subjective and closely related to the object. I 
> would favour 
> option 5 with the addition of the wrapper semantic unit of 
> "preservationPolicy", as Tobias suggests.
> 
> There is, however, a group of semantic units which I would 
> like to see 
> presented as an entity: environment. We are working on using 
> PREMIS for 
> preserving personal digital archives of notable individuals. 
> Oftentimes 
> we can record details of the environment(s) used by the 
> creator in the 
> production of their archive (because we have access to their 
> computers); 
> we would love to be able to create this information once and 
> link to it 
> from the objects derived from that environment, rather than 
> add the same 
> information to each object. Did the editorial committee 
> discuss this as 
> a possibility at any stage?
> 
> Best,
> 
> Susan
> 
> Gerard Clifton wrote:
> > Thanks for raising this, Tobias.
> >
> > In coming up with the current options, the Editorial 
> Committee did discuss
> > whether to create a separate entity for policies or 
> business rules, which
> > would include preservationLevel and significantProperties, 
> but initially
> > decided that a simple option could be to keep these 
> semantic units as
> > 'attributes' of individual objects, rather than link to a 
> separate entity.
> > However, we are also interested to hear others' views on this.
> >
> > Also, what other kinds of semantic units might fit under 'policy'?
> >
> > Regards
> > Gerard Clifton
> > Digital Preservation 
> > National Library of Australia, Canberra ACT 2600 Australia
> > t: +61 2 6262 1381 e: [log in to unmask]
> >
> >
> > On Thu, 25 Jan 2007 16:55:10 +0100, Steinke, Tobias 
> <[log in to unmask]> wrote:
> >
> >   
> >> Although I like the structured solution of option 5, there 
> should be a
> >> semantic unit "preservationPolicy" for this. The 
> preservation level and
> >> the significant properties are heavily related to the policy of the
> >> archiving institution (the agent) and to the associated rights.
> >> Therefore "preservationPolicy" or shorter "Policy" (it's all about
> >> preservation...) could even be an own type of entity in 
> PREMIS. Maybe we
> >> should consider to think about other policy-related issues 
> before making
> >> a decision.
> >>
> >> Best regards,
> >> Tobias Steinke
> >>
> >> -- 
> >> Tobias Steinke
> >> Deutsche Nationalbibliothek
> >> Informationstechnik
> >> Adickesallee 1
> >> D-60322 Frankfurt am Main
> >> Telefon: +49-69-1525-1762
> >> Telefax: +49-69-1525-1799
> >> mailto:[log in to unmask]
> >> http://www.d-nb.de
> >>
> >>
> >>
> >>     
> >>> -----Original Message-----
> >>> From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On 
> >>> Behalf Of Ruth Duerr
> >>> Sent: Tuesday, January 23, 2007 7:14 PM
> >>> To: [log in to unmask]
> >>> Subject: Re: [PIG] Revision of the PREMIS Data Dictionary - 
> >>> call for comments: significantProperties and preservationLevel
> >>>
> >>> Of the options presented on the wiki, I think Option 5 would 
> >>> suit the  
> >>> needs of the scientific data archive best....
> >>>
> >>> On Jan 22, 2007, at 12:37 AM, Gerard Clifton wrote:
> >>>
> >>>       
> >>>> The PREMIS Editorial Committee has begun revision of the 
> PREMIS Data
> >>>> Dictionary for Preservation Metadata and its related XML 
> schemas  
> >>>> and is
> >>>> seeking feedback from the digital preservation community.
> >>>>
> >>>> Comments and discussion are invited on proposed changes to the  
> >>>> semantic
> >>>> units 'significantProperties' and 'preservationLevel'. 
> Notes on a  
> >>>> number of
> >>>> issues and suggested options for these semantic units are 
> >>>>         
> >>> available  
> >>>       
> >>>> on the
> >>>> PREMIS Implementors' Group wiki at:
> >>>> http://pigpen.lib.uchicago.edu:8888/pigpen/11
> >>>>
> >>>> Please send comments and suggestions to the PIG-list for 
> further  
> >>>> discussion.
> >>>> The initial period for comment will end on Friday, 
> February 2, 2007.
> >>>>
> >>>> The full list of proposed changes will soon be made 
> available via  
> >>>> the wiki
> >>>> (see PREMIS Revisions at: http://pigpen.lib.uchicago.edu:8888/ 
> >>>> pigpen/8).
> >>>> Other topics for discussion will follow in due course.
> >>>>
> >>>> With thanks,
> >>>>
> >>>> The PREMIS Editorial Committee
> >>>>         
> >
> >   
> 
> 
> -- 
> Susan Thomas
> Project Manager
> Paradigm & Cairo
> Oxford University Library Services
> Osney One Building
> Osney Mead
> OXFORD OX2 0EW
> 
> Web : http://www.paradigm.ac.uk
>       http://cairo.paradigm.ac.uk	
> Telephone : +44 (0) 1865 283821
> 

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 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