Datasets:
srobertsphd
/
mit-labnetwork

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
2.97k
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
From diadiuk at MIT.EDU Tue Aug 24 10:49:53 2010
From: diadiuk at MIT.EDU (Vicky Diadiuk)
Date: Tue, 24 Aug 2010 10:49:53 -0400
Subject: [labnetwork] how-to retain knowledge
In-Reply-To: <4758C49779F144758A40C4EC1A476021@computer692435>
References: <4758C49779F144758A40C4EC1A476021@computer692435>
Message-ID: <F56109CA-1E94-485F-A058-B7157D746CA7@mit.edu>
Hi,
This is a perennial question that we've tried unsuccessfully to
approach really formally (we started a process library database,
searchable by material, process, etc) & the problem is that the person
inputting the data doesn't benefit from it, so it doesn't work well.
We haven't completely given up, & we have a Wiki site into which users
can upload their processes - some do.... some actually look at it once
in a while.
What we are doing, that sort of works, is maintain electronic
versions of each process that gets submitted for approval & we are
insisting on fairly descriptive titles.
The cumulative memory of the Process Technology Committe & the
fabstaff is the most useful tool, though.
Vicky
On Aug 23, 2010, at 11:21 PM, Vijay wrote:
> Matthieu,
> I can share my experience of getting process recipes
> documented
> from students who use our laboratory for their research work (Centre
> of
> excellence in Nanoelectronics, IISc, Bangalore) in following manner--
>
> 1. A brief format of the reports that each researchers needs to submit
> after completion of research work (or part of it) is given to them at
> the time of their initiating the work.
>
> 2. Report is colleted from them after research is completed and their
> next usage of lab may not be approved if they have not submitted the
> report in appropriate format.
>
> 3. New processes or recipes shared by the user student is documented
> as
> an internal report authored by the researcher and co-authored by the
> lab
> staff if essential role played by them. This gives the researchers
> sense
> of ownership of the work and also co-author gets his due credit. This
> document is not shared publicly until the researcher so desires.
> However, it is available for sharing amongst the Lab members on
> request
> basis.
>
> (This process is followed with researchers approaching our lab under
> Indian Nanoelectronics Users Program--INUP)
>
> Regards,
>
> VIjay
>
> -----Original Message-----
> From: labnetwork-bounces at mtl.mit.edu
> [mailto:labnetwork-bounces at mtl.mit.edu] On Behalf Of Schroeder,
> Jeremy L
> Sent: Monday, August 23, 2010 9:37 PM
> To: 'Matthieu Nannini, Dr.'; labnetwork at mtl.mit.edu
> Subject: Re: [labnetwork] how-to retain knowledge
>
> Matthieu,
>
> I don't have the answer, but I can briefly comment on the first
> question
> (i.e. retaining knowledge from fab members).
>
> We have discussed this issue at Purdue's Birck Nanotechnology Center
> and
> we thought about developing an online knowledge database. However, the
> key is getting members to actually write down their know-how since
> people are often not interested in doing additional work that does not
> clearly benefit them. Not only that, even if members write down their
> information, it has to be written in a clearly understood format and
> someone else should check the information to ensure that it is
> accurate.
>
> In order to get this to work, I think you need a staff member partly
> devoted to the project. The staff member can ask students for specific
> information and then create standard-format documents from this
> information.
>
> Jeremy
>
> -----Original Message-----
> From: labnetwork-bounces at mtl.mit.edu
> [mailto:labnetwork-bounces at mtl.mit.edu] On Behalf Of Matthieu Nannini,
> Dr.
> Sent: Monday, August 23, 2010 10:08 AM
> To: labnetwork at mtl.mit.edu
> Subject: [labnetwork] how-to retain knowledge
>