Venue : AVON Foundation Comprehensive Breast Evaluation Center
Attendees : Prof. Bolker, Lesley Wojcik, Dr. Kopans, Mr. Richard, Suparna, Salini, Ashok and Shaila
Minutes:
We introduced ourselves to Lesley Wojcik and team at Avon Medical center.
The discussion was concentrated about learning the project requirements.
Each of us drew the rough sketch of the how a simple front end would look like.
Each of us presented a different idea.
We decided to come with a simple utility, which will simulate the search.
We decided to look/study for already available utility programs in Windows operating system.
Lesley agreed to show team their current data management system in the next meeting.
Comments:
The client’s ideas/suggestions are to some extent clear, to some extent confusing, and to some extent beyond the reach.
Currently the client has tremendous resources, which are not utilized, as it was difficult to search their existing resources.
The client has several users, where each user has a collection of resources. Each user has his/her mechanism for organizing his/her resources. There is no unified approach for organizing the resources for the users.
The meeting aimed at developing bridging structures that can link all the available resources, and to develop search engines with different search criteria that can crawl through all the resources, and get the relevant resources from the search.
The various resources the client has include electronic data, research paper publications, journals, films etc.
The client suggested that Term Synthesis and barcode approach has to be followed to organize and search the data. The search engine should be powered with various search criteria for e.g., search based on topic, last name of the author, budget number, chronology of the resources.
The search engine designed should search online resources (PubMed, MedLine etc), in addition to searching the client’s own resources.
The design of the project should be based on the levels of abstraction of data.
The client uses Paradox (DOS based database, which is ODBC and SQL compliant), Turbo Library e-journals to search the resources.
Options should be provided for saving some of the searches, and an automatic naming convention has to be provided for the saved searches.
The client suggested that granularity in the searches should not be provided as it may sometimes lead to the loss of valuable information.
The conclusion of this meeting was the client requires that the data should be indexed and should support both refined and generalized search. The client expects "Perspective Indexing of data with Retrospective searching of Data".