LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (May 2001, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 4 May 2001 17:20:50 +0100
Reply-To:     Peter Crawford <peter.crawford@DB.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Peter Crawford <peter.crawford@DB.COM>
Subject:      'Data Set History'
Comments: To: John.W@mediscience.co.uk
Content-type: text/plain; charset=iso-8859-1

Hi John Would hosting contents info /creation code/production history log in a catalog by (perhaps) the same name as the dataset meet the need of associated notes (nearly attached) ?

I go along in general with the need for attached documentation, but thought this meets the need with current sas system facilities and without overloading the data with metadata.

On my mvs platform the bound library provides a convenient "container" keeping documentation with data.

Regards Peter

Datum: 04/05/2001 16:07 An: SAS-L@listserv.uga.edu

Antwort an: John.W@mediscience.co.uk

Betreff: 'Data Set History' Nachrichtentext:

Hi folks,

In response to my recent post, I have received several private messages agreeing with me that the (very) old 'data set history' feature of PROC CONTENTS was probably nearly always 'less than useful' - which is probably why it was seemingly dropped a long time ago.

However, in response to those messages of agreement, I have suggested that, at least for me, far more useful/valuable would be the ability to somehow permanently attach 'notes' (which could include code) to a SAS dataset.

As things are, I sometimes 'emulate' that by story notes in a 'dummy' character variable - but that obviously has the potential to be very wasteful in terms of file size. Also, when archiving datasets, I often zip them together with files containing notes and/or code - but that is a little tedious. For me, it would be nice if those notes etc. could 'just be there' as part of the dataset.

If at least a few of you agree with me, I'll make this suggestion to SI.

Kind Regards

John

---------------------------------------------------------------- Dr John Whittington, Voice: +44 (0) 1296 730225 Mediscience Services Fax: +44 (0) 1296 738893 Twyford Manor, Twyford, E-mail: John.W@mediscience.co.uk Buckingham MK18 4EL, UK mediscience@compuserve.com ----------------------------------------------------------------

--

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


Back to: Top of message | Previous page | Main SAS-L page