[385] in magellan
Spatial Data Services Bi-Weekly Report
daemon@ATHENA.MIT.EDU (Daniel Sheehan)
Wed Feb 2 21:23:17 2000
Message-Id: <200002030223.VAA16514@melbourne-city-street.MIT.EDU>
Date: Wed, 02 Feb 2000 21:21:14 -0500
To: magellan@mit.edu
From: Daniel Sheehan <dsheehan@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Project Name: Spatial Data Services
Project Leader: Daniel Sheehan
Report Date Feb. 2, 2000
Submitted by: Daniel Sheehan
URL: http://web.mit.edu/gis/www/spatial-data/
Accomplishments past period:
- Found a metadata to MARC (library) format converter.
- Discusses Libraries' interest in spatial data and GIS services.
- Developed understanding of Oracle/SDE and decided to schedule time to
work on Oracle and SDE before developing a delivery plan.
Goals for the coming period:
- Develop relationship with "metadata->MARC" format developers. Possibly
participate as Alpha testers.
- Develop a better facility with the spatial software.
- Include Anne Salemme on the Oracle/SDE (Spatial Database Engine)
technical side of the team as well as the network side. Anne is interested
in Oracle and is currently enrolled in a class. She expresses string
interest in dealing with SDE.
- Continue to find other institutions with spatial data or GIS services and
discover how they store and retrieve data.
Issues:
- We need to determine that the software can sucessfully do before we try
to develop a delivery plan. This should take approximately one month. The
team would like to continue working and meeting while we develop expertise
with the software.
Key learnings:
- What is a "Discovery Process" ? I intintially thought of suspending the
process while team member Tom Grayson and I developed expertise with the
software. Team members would like to continue though some will work at a
slower pace while we learn to deal with SDE. In addition, Anne Salemme
volunteered to take an active part in working with the SDE software. A
couple of lesson: the process may take longer than expected and some
diversions (getting a better understanding of the problem and seeing new
aspects of the problem) should be anticipated and are part of the process.
Finally, team members helped to define a way to slow down the process while
keeping the team together.
Team dynamics:
- We have an interested and enthusiatic team.
Additional comments:
- None
Cheers,
Daniel
-----------------------
Daniel Sheehan
Spatial Data Specialist
Academic Computing / Information Systems
x2-1475
dsheehan@mit.edu
