JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for RECORDS-MANAGEMENT-UK Archives


RECORDS-MANAGEMENT-UK Archives

RECORDS-MANAGEMENT-UK Archives


RECORDS-MANAGEMENT-UK@JISCMAIL.AC.UK


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

RECORDS-MANAGEMENT-UK Home

RECORDS-MANAGEMENT-UK Home

RECORDS-MANAGEMENT-UK  July 2006

RECORDS-MANAGEMENT-UK July 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Originals and Copies (was RE: Back Ups)

From:

David Aspinall <[log in to unmask]>

Reply-To:

David Aspinall <[log in to unmask]>

Date:

Wed, 5 Jul 2006 08:49:38 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (125 lines)

I can see where both Marc and Larry are coming from and one could argue both
are right:

-	It is true that by the time information gets placed on a media it
has already resided in some temporary memory e.g. RAM. So one could argue
that when it is placed on, say, disc, it is not original.
-	But the first place the user or operating system "selects" as the
destination would be part of some dedicated storage - be that disc, tape,
memory stick or something else. So one could argue that everything else was
transient and that this is the first/original copy.
-	I think that bit is academic but there does tend to be a difference
in ownership/responsibility when looking at the structured and unstructured
data.
-	The situation with structured systems is pretty simple to define -
ICT takes a back-up (either complete or incremental) of the database. The
ICT team takes responsibility for maintaining a service.
-	With unstructured data, it is more normal to take back-ups (either
complete or incremental) either the whole or part of a structure (e.g.
"Shared Docs on the X: drive). With these kind of back-ups the ICT people
usually leave the user to determine which is "the master". They are simply
providing a service related to a specific logical area. Responsibility and
ownership of the contents are usually left with the users.

David Aspinall
Senior Records Management Consultant
Tribal Education & Technology
The Charnwood Building
Holywell Park
Ashby Road
Loughborough LE31 3GS
 
T  01509 268292
F  01509 232748
E  [log in to unmask]
 
M 07785 234322
www.tribalgroup.co.uk
 
This email and any attachments (together the "contents") are for the
confidential use of the named recipient(s) only. They may be subject to
legal professional privilege.  They are intended solely for the person or
organisation to whom this email is addressed and if you are not the intended
recipient, you must not copy, distribute, disclose or take any action in
reliance on the contents. If you have received this e-mail in error, please
delete the contents from your computer system and notify the sender as soon
as possible. Any opinions expressed in the contents are those of the
individual and not necessarily of the company. Whilst the contents have been
scanned for the presence of computer viruses, we do not guarantee that they
are virus-free and we accept no liability for any damage or loss resulting
from a virus or any malicious program. It is the recipient's responsibility
to ensure that the onward transmission, opening or use of the contents will
not adversely affect their systems or data or otherwise incur liability in
law.
 
____________________________________________


-----Original Message-----
From: The UK Records Management mailing list
[mailto:[log in to unmask]] On Behalf Of Fresko, Marc
Sent: 04 July 2006 23:47
To: [log in to unmask]
Subject: Originals and Copies (was RE: Back Ups)

Larry, also with great respect for your huge experience in records
management:

If (for example) you open on your PC an electronic document that is held
on a server, you are not opening the stream of bits that is on the
server.  Rather, your computers are copying the bit stream from the
server to your PC and opening that copy.  If you then apply metadata (or
whatever) to declare it a "record", then save it back to the server, you
are likely to be saving a fresh copy to the server (details admittedly
dependent on configuration).  So the "record" on you copy is then a copy
of a copy of the document that started out on the server.  And that,
almost inevitably, was not the original bit stream anyway.  This is only
one example from several instances of copying that will take place
during the existence of the record.  All this is miles away from the way
that paper records are created and how they exist.

The concepts you cite are all absolutely fine in the non-electronic
world, but they do not make sense with electronic documents and records.
In most cases that matter, you cannot sensibly identify an electronic
original, and you cannot produce an electronic original in any
meaningful way.  The best you can do (and what you must do) is to ensure
that all copies of a record are accompanied by appropriate controls so
that you can attest successfully that they represent a true record of
the content of the long-lost original.

Marc Fresko



-----Original Message-----
From: The UK Records Management mailing list
[mailto:[log in to unmask]] On Behalf Of Larry Medina
Sent: 04 July 2006 23:27
To: [log in to unmask]
Subject: Re: Back Ups

On Jul 3, 2006, at 7:54 AM, Susan Mansfield wrote:

> As a result of the good practice mobilisation work records management 
> has been doing our ICT department is reviewing its back up 
> arrangements.
> I'd
> appreciate hearing how other organisations handle backing up 
> information to inform the decisions we are faced with making.

First, I must respectfully disagree that there is no "original" 
electronic document, and that that "all are copies" once stored.

Your policy and procedure should declare which original is handled and
declared as the master (or source or original) record.  It's typically
that which is generated by the department, originator or organization
responsible for the business function or purpose the "document" 
supports.  And your practices should indicate how that "record copy" is
authenticated and protected as a record, which would include how it is
stored, scheduled and managed.

<snip>

Larry Medina
Danville, CA

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 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
November 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
September 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
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager