On Thu, Sep 06, 2012 at 04:58:16PM +0000, Berry, Irene (CIV) wrote:
>   1.  Computer code: Has anyone successfully added .tgz or gripped tar ball 
> format for computer code?  I don't see that format on the table of supported 
> formats, but I wondered if anyone has archived computer code successfully.  
> That is the format that has been proposed to me.

The categories are suggestions only.  "Supported" means supported by
*your organization*, as in:  you undertake to ensure that the
bitstream will still be accessible as format fashions change.  You
should review the lists of support levels and alter as needed.  DSpace
just stores and serves up the bits.

Here, "supported format" means we're confident that we can recover the
content from the packaging and rewrite it in some suitable new format,
should the old format fall into disuse.  That generally means it's an
open, published format and we wouldn't be afraid to spend a reasonable
amount of time building a converter for it, if we had to, or that
open-source tools which can read it are known to be available.  "Known
format" means we think it should be usable over the long term but we
make no promises.  The other category (I forget the name) means "we'll
store it for you, but we make no statements about whether it may be
usable tomorrow."

IIRC the categories and their members were carried over from what the
MIT Libraries felt they could reasonably do to maintain repository
content.  Every site ought to think deeply about these lists and make
adjustments for local conditions as needed.

(Come to think of it, we probably ought to ship the format registry
content as optional material and let people install it manually, to
encourage local examination of the lists.)

.tgz is an interesting case because it's a container format.  That
means that you have currency issues with both the .tgz and the stuff
packed inside.  .tgz ought to be "supported" here because 'tar' and
'gzip' are both well-known and published, and tools could be recreated
from scratch without too much trouble if we really had to.  Program
code (however packaged) has a currency which is distinct from that.
For example, Common Bliss programmers are becoming somewhat rare(r),
so it might be infeasible to make that code run 100 years from now.
(That also points out that you want to be very thoughtful about what
you mean by "supported".)

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Asking whether markets are efficient is like asking whether people are smart.

Attachment: pgpSU7bgCus6f.pgp
Description: PGP signature

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to